Re: Replication fails after June 17 updates
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Fri, 27 Jun 2008 09:27:48 -0400
I am not sure, but I have seen this before.
"Mark" <Mark@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:982F48A4-3E16-46CD-95AD-E39D3ADC03EC@xxxxxxxxxxxxxxxx
Great news.....I got it going again
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?
"Hilary Cotter" wrote:
are any error messages logged?
Can you run the binary from the command prompt?
Hilary
"Mark" <Mark@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D3605196-9B8F-4BF5-8366-5EE66BCC3984@xxxxxxxxxxxxxxxx
> Hello,
>
> 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
.
- References:
- Re: Replication fails after June 17 updates
- From: Hilary Cotter
- Re: Replication fails after June 17 updates
- Prev by Date: Re: SQL Server could not create a suscription for Subscriber
- Next by Date: Re: replicating stored procedures
- Previous by thread: Re: Replication fails after June 17 updates
- Next by thread: Re: SQL Server could not create a suscription for Subscriber
- Index(es):
Relevant Pages
|