MS SQL Server Replication - The process could not connect to the distributor.

Author

The process could not connect to the distributor.

Maverick06

2006-11-28, 7:20 pm

I have a small problem, I get this following error when trying to start
the snapshot agent "The process could not connect to the distributor
'distributor name'. NOTE: The step was retried the requested number of
times [10] without succeeding. The step failed.

I thought it was related to users or rights but I am using the same
user than in previous replication with the server and the rights
haven't been altered. I don't know if someone has some knowledge of
what to do or a workaround solution, any help would be greatly
appreciated.

Thank you in advance.

Hilary Cotter

2006-11-28, 7:20 pm

The account you are using to connect to your distributor does not have
rights to connect to it. You have to make sure that this account is in the
dbo role in the distribution database.

--
Hilary Cotter

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

"Maverick06" < swift_kick125@hotmai
l.com> wrote in message
news:1164727117.680290.127270@n67g2000cwd.googlegroups.com...
>I have a small problem, I get this following error when trying to start
> the snapshot agent "The process could not connect to the distributor
> 'distributor name'. NOTE: The step was retried the requested number of
> times [10] without succeeding. The step failed.
>
> I thought it was related to users or rights but I am using the same
> user than in previous replication with the server and the rights
> haven't been altered. I don't know if someone has some knowledge of
> what to do or a workaround solution, any help would be greatly
> appreciated.
>
> Thank you in advance.
>

Paul Ibison

2006-11-28, 7:20 pm

This may be the case if the server has been renamed. You may alternatively
see these cryptic errors :
18483 - could not connect to server 'Newname' because distributor_admin is
not defined as a remote login at the server.
18482 - could not connect to server 'Newname' because 'Oldname' is not
defined as a remote server.
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
NB: You can use the @@SERVERNAME global variable or the
SERVERPROPERTY('Serv
erName') 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.

Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Maverick06

2006-11-28, 7:20 pm

Thank you very much both of you for your help. The problem has been
fixed.... It was kind of odd at the server the SqlServer Agent started
with a user name that wasn't even known to him..

Anyhow that wasn't the source of the problem I believe... because even
when it had started the problem was still recurring. I played in the
login properties for the owner of the snapshot agent didn't change any
settings but pressed ok and the agent started normally...

I am a newbie at the replication game but am I the only one that finds
that it is filled with BUGS over its head??!!?!?!?!?!?!

Paul Ibison wrote:
> This may be the case if the server has been renamed. You may alternatively
> see these cryptic errors :
> 18483 - could not connect to server 'Newname' because distributor_admin is
> not defined as a remote login at the server.
> 18482 - could not connect to server 'Newname' because 'Oldname' is not
> defined as a remote server.
> 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
> NB: You can use the @@SERVERNAME global variable or the
> SERVERPROPERTY('Serv
erName') 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.
>
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .

Sponsored Links