Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
DeeZed
Starting Member
1 Post |
Posted - 2011-01-28 : 04:39:43
|
Hi, I'm hoping someone can help me. I have a SQL2005 SP3 + patch (so 9.0.4053) distributor which is also the subscriber. 5 different servers replicate through and to this server without issues. However 1 server (same version, both 64 bit) causes errors everytime either the publisher or distributor/subscriber are restarted. The log reader agents for all publications from that server error, the dist agent retries, only errors I can see are "The process could not execute 'sp_MSpub_adjust_identity' on servername. Status: 0, code: 21, text: 'Encryption not supported on the client.'.". These errors can last for anything up to about 5 hours. Then suddenly, with no intervention, all agents start working and the whole thing catches up. I'm at my wits end with this, as I can't find anything helpful on it! I have tried restarting the agents with a new profile with ReadBatchSize set to 1 and a loginTimeout of 150, but this doesn't help. All ideas gratefully received! |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-01-28 : 07:38:01
|
If you restart the distributor, then of course you're going to get errors.Not 5 hours worth though, unless it's down for nearly that long. How are you determining this? Are you sure that the error condition is lasting that long? Are you checking the agent statuses? Don't use replication monitor for this.What do you see in the SQL Server logs and application event logs?What do you see in distribution..msrepl_errors?Finally, why and how often are you restarting the distributor? |
|
|
|
|
|
|
|