October 3, 2009 at 1:22 am
We have upgrade the SQL server from 2000 to 2005. After upgrade the replication is not working with the following symptoms:
1. Subscription status always show 'Not running, performance critical'.
2. When I try to re-sychronize with option "Start Synchronziing" , error is encounter as below :
Replication montior could not start the job '..................'
Additional informtion :
SQL server Agent error : request to run job STX-T01-STL_NEwCC
(from User sa) refused because the job is already running from a request by User sa. (Microsoft SQL Server , Error: 22022)
Anyone could kindly help ?
Or any idea to further troubleshoot this issue ?
Thanks and best regards,
October 5, 2009 at 12:32 am
I have seen this a ton. I actually created a a report in reporting services to identify these agents. I do not trust replication monitor. If you actually go to the subscription in replication monitor that is not running and go to tools--> and then click stop sync and then at that point you can start it again. I think this is a bug, but i have seen this several times.
October 5, 2009 at 12:42 am
I also forgot to add with the log reader i have also seen this if for some reason depending on the upgrade or setup if you have multiple jobs running. For example, the old log-reader for db abc and then a new one is created but the old one isn't over-written or deleted. That is another way to see this message.
If you still can't figure it out, I would suggest putting the verbose flag on with the option 3 to capture the problem.
October 7, 2009 at 7:39 am
this problem has been solved. Thanks.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply