Active Directory has killed Replication...

Hi folks,
We've just upgraded our SQL servers to active directory. Have deleted all
of the existing jobs and replications before upgrading, as one is supposed
to do, but now when I create a new replication it just fails, saying it
can't find the distribution server specified.
The snapshot is failing at the Run agent step with "The process could not
create file '\\DIVCS-SQL1\F$\Replication\unc'. The step failed.", where
DIVCS-SQL1 is the old name of the server.
When I go to the configuration screen for the replication agent it shows the
old server name as the Distribution Server name (DIVCS-SQL1)
I assume that there is a registry item that points SQL server to the right
agent, but I don't want to start playing with it without some advice...
Thanks in advance...
Paul
Paul,
Try:
Use Master
go
Select @.@.Servername
This should return your current server name but if it
returns NULL or the oldname then try:
Use Master
go
Sp_DropServer 'Server1'
GO
Use Master
go
Sp_Addserver 'Server1', 'local'
GO
Stop and Start SQL Services
NB: You can use the @.@.SERVERNAME global variable or the SERVERPROPERTY('ServerName') function in SQL Server to find the network name of the computer running SQL Server. The ServerName property of the SERVERPROPERTY function automatically reports the chang
e in the network name of the computer when you restart the computer and the SQL Server service. The @.@.SERVERNAME global variable retains the original SQL Server computer name until the SQL Server name is manually reset.
HTH,
Paul Ibison
|||Hi,
Just tried sp_dropserver and got the following error message :
"Server: Msg 20582, Level 16, State 1, Procedure sp_MSrepl_check_server,
Line 39
Cannot drop server 'DIVCS-SQL1' because it is used as a Publisher in
replication."
I tried the 'droplogins' parameter as well, but to no avail.
Any ideas?
Cheers...P
"Paul Ibison" <Paul.Ibison@.Pygmalion.com> wrote in message
news:84A80174-EB3D-4414-9288-C84A01B6C72E@.microsoft.com...
> Paul,
> Try:
> Use Master
> go
> Select @.@.Servername
> This should return your current server name but if it
> returns NULL or the oldname then try:
> Use Master
> go
> Sp_DropServer 'Server1'
> GO
> Use Master
> go
> Sp_Addserver 'Server1', 'local'
> GO
> Stop and Start SQL Services
> NB: You can use the @.@.SERVERNAME global variable or the
SERVERPROPERTY('ServerName') function in SQL Server to find the network name
of the computer running SQL Server. The ServerName property of the
SERVERPROPERTY function automatically reports the change in the network name
of the computer when you restart the computer and the SQL Server service.
The @.@.SERVERNAME global variable retains the original SQL Server computer
name until the SQL Server name is manually reset.
> HTH,
> Paul Ibison
>
|||Paul,
am I right in saying that
Select @.@.Servername
Select SERVERPROPERTY('ServerName')
return different values?
This is the case I mentioned when you need to update the value in sysservers.
If this is so, then it means that you have set up replication on a renamed server, or you have set up replication then renamed the server. The simplest method to solve the issue is to drop the publications, disable replication, update sysservers using the
script in my previous post, then recreate the publications.
HTH,
Paul Ibison
|||Phew...Got it working.
Thanks for your help...I kind of got it...eventually.
P
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:016D7C4C-5BAF-416F-87E6-0184DE7FD002@.microsoft.com...
> Paul,
> am I right in saying that
> Select @.@.Servername
> Select SERVERPROPERTY('ServerName')
> return different values?
> This is the case I mentioned when you need to update the value in
sysservers.
> If this is so, then it means that you have set up replication on a renamed
server, or you have set up replication then renamed the server. The simplest
method to solve the issue is to drop the publications, disable replication,
update sysservers using the script in my previous post, then recreate the
publications.
> HTH,
> Paul Ibison