Computer name change at subscriber and Replication fail

Hello,
The computer name of one of the subscribers was changed and now the
sychronization does not go through.
It is not possible to changed back and I would like to know if there is an
easy way to get the subscriber back to work.
Thanks,
car.
Realistically you'll need to reinitialize. You could hack the system tables
if you are on SQL Server 2000 but I wouldn't advise it.
Paul Ibison
|||You need to drop your subscription and recreate it for the new subscriber.
"Car" <Car@.discussions.microsoft.com> wrote in message
news:5F57C2E3-0ADF-4CCE-95DF-A693BF317398@.microsoft.com...
> Hello,
> The computer name of one of the subscribers was changed and now the
> sychronization does not go through.
> It is not possible to changed back and I would like to know if there is an
> easy way to get the subscriber back to work.
> Thanks,
> car.
|||I don't know the kind of replication you're using. But maybe this can help
you.
Now I'm testing the replication that we'll set up in our customer and I've
done this:
Backup a subscription database in computer A.
Copied backup to computer B.
Switched off computer A.
Restore backup in computer B.
Changed name in computer B, setting computer's A name.
Execute:
Use Master
go
Sp_DropServer 'B\INSTANCE_NAME'
GO
Use Master
go
Sp_Addserver 'A\INSTANCE_NAME', 'local'
GO
This works if you have synchronized before doing the backup. I still need to
try if I do the backup before (so the changes are already replicated to
Publisher).
So for this, I think that just executing the script will be enough for you.
But now I'm afraid for what Paul an Hilary has said...
Josep.
"Hilary Cotter" <hilary.cotter@.gmail.com> escribi en el mensaje
news:%23zMmeLqgHHA.3796@.TK2MSFTNGP02.phx.gbl...
> You need to drop your subscription and recreate it for the new subscriber.
> "Car" <Car@.discussions.microsoft.com> wrote in message
> news:5F57C2E3-0ADF-4CCE-95DF-A693BF317398@.microsoft.com...
>