We have a SQL2005 server running on Windows Server 2003 R2.
It has been running fine and replacting data for almost a year now.
Last Tuesday June 17 a number of microsft updates were applied to the server
- including several SQL Server updates. After the patches all seemed well.
We then noticed that the replication had stopped. When I try to restart it
it looks like it is going but stops itself a few seconds later.
I then uninstalled the updates and was successfull at getting two of the SQL
updates removed but can't get the third off.
Does anyone have any suggestions?
Thank you
Can you run the binary from the command prompt?
Hilary
"Mark" <Ma...@discussions.microsoft.com> wrote in message
news:D3605196-9B8F-4BF5...@microsoft.com...
Seems that all the jobs had lost thier owner
I added an owner to each job in the properties
started the jobs and kicked of replication and wala
So how the heck could that happen? Could updates do that?