merge job failing

Hello,
Have a problem where a merge replication job is failing. I think I know why
I just don't know how to correct (without reinitialising).
By mistake, one of our guys (tracing another problem) deleted the remote
server on the subscriber which we can call serverS (the remote server
deleted in this case was itself - i.e ServerS is the name of the remote
server and this is on ServerS - it was referencing itself)
Now when the publisher serverP starts to synchronise with this subscriber we
get the following error message :-
The subscription could not be found
Source ServerS error number 20021
The remote server on serverS is set up again and looks just like it did
before but I'm guessing that the system is smart enough to know that this is
not the original and will not see the newly recreated remote server?
Any ideas/advice greatly appreciated..
Thanks
David
...forgot to say : the main error message displayed is
'The subscription to publication 'XXXX' is invalid'
rgds
David
"David Wilce" <david.wilce@.btinternet.com> wrote in message
news:1eqdnWxc4p43bdTYnZ2dnUVZ8qSdnZ2d@.bt.com...
> Hello,
> Have a problem where a merge replication job is failing. I think I know
why
> I just don't know how to correct (without reinitialising).
> By mistake, one of our guys (tracing another problem) deleted the remote
> server on the subscriber which we can call serverS (the remote server
> deleted in this case was itself - i.e ServerS is the name of the remote
> server and this is on ServerS - it was referencing itself)
> Now when the publisher serverP starts to synchronise with this subscriber
we
> get the following error message :-
> The subscription could not be found
> Source ServerS error number 20021
> The remote server on serverS is set up again and looks just like it did
> before but I'm guessing that the system is smart enough to know that this
is
> not the original and will not see the newly recreated remote server?
> Any ideas/advice greatly appreciated..
> Thanks
> David
>
|||Hi Dave,
I know we talked about this offline but for anyone else who needs the
solution......:
Try:
Use Master
go
Select @.@.Servername
This should return your current server name but if it
returns NULL then try:
Use Master
go
Sp_DropServer 'OldName'
GO
Use Master
go
Sp_Addserver 'NewName', 'local'
GO
Stop and Start SQL Services
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Thanks again Paul
Invaluable support as ever!
Regards
Dave
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uItsjMp$GHA.4592@.TK2MSFTNGP03.phx.gbl...
> Hi Dave,
> I know we talked about this offline but for anyone else who needs the
> solution......:
> Try:
> Use Master
> go
> Select @.@.Servername
> This should return your current server name but if it
> returns NULL then try:
> Use Master
> go
> Sp_DropServer 'OldName'
> GO
> Use Master
> go
> Sp_Addserver 'NewName', 'local'
> GO
> Stop and Start SQL Services
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>