replication problem

what's rcsp_resolver does becuase the replication failed ((timeout expired))
please help meSounds like a custom conflict resolution procedure to me - not sure where you would access these - probably in the publication properties somewhere.
GW

replication log reader failed

Hi all,
Sql server 7.0
I have replication jobs which replicates the data from one
server to another.
one of our server was down for some duration of time and
the replication job log reader has failed it gives the
error msg log reader agent: "the process could not
execute 'sp_repldone/sp_replcount".
pls help me in solving this problem.
TIA
Haseeb,
I thought these issues had been sorted in SP>=2. If you don't have it
installed it's worth putting on. Either way, you could try increasing the
Query timeout (default: 300 seconds) on the logreader by editing the
QueryTimeout option as this is I think the issue.
HTH,
Paul Ibison
|||I also had this problem and setting the QueryTimeout did not help. I tried everything in every posting I could find and nothing worked. I ended up deleting all my publications to reset the Log Reader Agent, then re-setup the publications and subscriptio
ns. Once the Log Reader was recreated, everything worked fine again.
"Paul Ibison" wrote:

> Haseeb,
> I thought these issues had been sorted in SP>=2. If you don't have it
> installed it's worth putting on. Either way, you could try increasing the
> Query timeout (default: 300 seconds) on the logreader by editing the
> QueryTimeout option as this is I think the issue.
> HTH,
> Paul Ibison
>
>

replication job failure

Our SQl Server 2000 was rebooted recently but when I check the management
section then jobs replication its registered as failed yet when checking the
history it is still executing step 2.
Yet when I check in the replication monitor in the distribution agents
replication is as normal do you know how I can get rid of the fail status if
it is still processing transaction replication that has been running for 3
days on step 2?
thanks for any help
Sammy
Sammy,
you could try stopping and restarting the job, then refresh.
Rgds,
Paul Ibison
|||Thanks Paul it worked
"Paul Ibison" wrote:

> Sammy,
> you could try stopping and restarting the job, then refresh.
> Rgds,
> Paul Ibison
>
>

Replication Job Failed. Unable to determine the owner

A former employee at my organization created a replication job to back up our database. The developer has since left and his windows account was deleted. I'm now receiving this error:

SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-05 15:40:00 - Message: The job failed. Unable to determine if the owner (username) of job Replication agents checkup has server access (reason: Could not obtain information about Windows NT group/user 'username', error code 0x534. [SQLSTATE 42000] (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error 3621)).

How can I fix this? I looked under the Replication folder but didn't see anything.

In Object Explorer, look at the job in SQL Server Agent to see who owns it, and verify the account is valid.

|||That's for the help. I changed the owner but am now getting this error:

SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-07 01:00:00 - Message: The job failed. The Job was invoked by Schedule 175 (Replication agent schedule.). The last step to run was step 1 (Run agent.).

When I executed the maintenance plan manually it worked, but it doesn't seem to work on the schedule. I've never created a maintenance plans so I'm going to look up some more information to see if I can figure out what is going to wrong.

Replication Job Failed. Unable to determine the owner

A former employee at my organization created a replication job to back up our database. The developer has since left and his windows account was deleted. I'm now receiving this error:

SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-05 15:40:00 - Message: The job failed. Unable to determine if the owner (username) of job Replication agents checkup has server access (reason: Could not obtain information about Windows NT group/user 'username', error code 0x534. [SQLSTATE 42000] (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error 3621)).

How can I fix this? I looked under the Replication folder but didn't see anything.

In Object Explorer, look at the job in SQL Server Agent to see who owns it, and verify the account is valid.

|||That's for the help. I changed the owner but am now getting this error:

SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-07 01:00:00 - Message: The job failed. The Job was invoked by Schedule 175 (Replication agent schedule.). The last step to run was step 1 (Run agent.).

When I executed the maintenance plan manually it worked, but it doesn't seem to work on the schedule. I've never created a maintenance plans so I'm going to look up some more information to see if I can figure out what is going to wrong.

Replication issues with failed logins

I just applied instcat.sql to my SQL Srvr 2k sp4. At first it broke my replication with some cursor errors. Applying the latest instcat.sql fixed the problem, however one of the distribution agents would not start (i'm not sure if instcat had anything to do with it) giving me a "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. The process could not connect to distributor 'DistributorName'. The step failed." error.

Any suggestions would be greatly appreciated!

Thanks!

For those who experience similar problems: I simply ran distribution agent at Distributor. That fixed the issue.