Error connecting to subscriber

Question

Error connecting to subscriber

Clive Strong

SSChampion

Points: 11222
More actions
September 18, 2008 at 10:16 am

#193033

Hey All,
I bit of a head scratcher.
I was replicating to a client's database and all was well. Now I have noticed I am getting the errors:
The process could not connect to Subscriber 'XXXXX'. (Source: MSSQL_REPL, Error number: MSSQL_REPL0)
Named Pipes Provider: Could not open a connection to SQL Server [53]. (Source: MSSQLServer, Error number: 53)
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (Source: MSSQLServer, Error number: 53)
Login timeout expired (Source: MSSQLServer, Error number: HYT00)
We're replicating across the internet to a client site. I can telnet no problem and from SSMS, I can connect to the database.
The box is set up as publisher and distributor.
Any thoughts?

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

steveb. SSC-Forever Points: 46733 More actions · Answer 1

I have had a similar problem when i was setting up replication, it turned out to be an issue with running sql under a local account.

Could this be the issue?

Clive Strong SSChampion Points: 11222 More actions · Answer 2

Clive Strong

SSChampion

Points: 11222

September 18, 2008 at 10:37 am

#873769

Hey Steve,

Domain account at my end.

Adrian Robertson Mr or Mrs. 500 Points: 551 More actions · Answer 3

Sorry if I'm asking the obvious being a newbie and all, but is Named Pipes enabled in the SQL Server 2005 Network Configuration area of SQL Server Configuration Manager?

Clive Strong SSChampion Points: 11222 More actions · Answer 4

Hi Adrian,

Yes it was. I still have no clue as to what is wrong with this. In the end, I used a different box for replication in order to get it working. I've not had time in the past week to look at this box and resolve the issue.

forsqlserver SSCoach Points: 18902 More actions · Answer 5

Hi

I m getting the same issue,I think somewhere I have read that using lmhosts.sam file which exist in "C:\WINDOWS\system32\drivers\etc"

but not sure...

Thanks

jamie.greiver SSChasing Mays Points: 612 More actions · Answer 6

I had this same issue. I was working on a vm cluster. I had updated the host file on one server but not the other. Once I had the correct IP and hostname for the subscription server on each publisher node it was resolved. Hope this helps!