Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Error connecting to subscriber Expand / Collapse
Author
Message
Posted Thursday, September 18, 2008 10:16 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 7:31 AM
Points: 1,114, Visits: 6,445
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?
Post #571951
Posted Thursday, September 18, 2008 10:30 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, May 30, 2014 6:27 PM
Points: 2,808, Visits: 7,175
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?
Post #571964
Posted Thursday, September 18, 2008 10:37 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 7:31 AM
Points: 1,114, Visits: 6,445
Hey Steve,

Domain account at my end.
Post #571971
Posted Tuesday, October 7, 2008 12:12 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, October 11, 2009 3:17 PM
Points: 23, Visits: 107
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?

Post #581529
Posted Tuesday, October 7, 2008 2:10 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 7:31 AM
Points: 1,114, Visits: 6,445
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.
Post #581579
Posted Friday, February 27, 2009 3:11 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, July 31, 2014 5:19 AM
Points: 1,202, Visits: 1,929
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

Post #665574
Posted Friday, April 19, 2013 10:56 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, August 1, 2014 4:37 PM
Points: 14, Visits: 132
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!
Post #1444677
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse