Transactional replication fails with connection refused error
in [Replication]
|
Prev: Reinitialize without upload error and KB Article ID: 953624
Next: Replication monitor shows duplicate merge subscription
From: Susan Cooper on 17 Sep 2008 11:32 Hi, I've setup transactional replication on 4 SQL Server 2005 clustered servers. I have three different publications all configured as push with the distributor running on the server with the publications. it looks like this: Cluster 1 has 2 databases that have 3 publications -distributor is here ClusterA - subscribes to one publication ClusterB - subscribes to 2 publications ClusterC - subscribes to all 3 publications replication is working perfectly for ClusterA and ClusterB, but ClusterC (really named ove-crmsql01) fails with the following error: The process could not connect to Subscriber 'OVE-CRMSQL01'. (Source: MSSQL_REPL, Error number: MSSQL_REPL0) Get help: http://help/MSSQL_REPL0 TCP Provider: No connection could be made because the target machine actively refused it. (Source: MSSQLServer, Error number: 10061) Get help: http://help/10061 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: 10061 The distributor is connecting to the subscriber with a sql server authenticated user that has sysadmin permissions, and I've made sure that I can connect from Cluster1 to ClusterA using Management Studio. Our network admins insist there isn't a firewall between the two, so what can I be missing? this is driving me crazy... Thanks for the help! -Susan
From: predei on 17 Sep 2008 12:50 On Sep 17, 8:32 am, Susan Cooper <SusanCoo...(a)discussions.microsoft.com> wrote: > Hi, > > I've setuptransactionalreplicationon 4 SQL Server 2005 clustered servers. > I have three different publications all configured aspushwith the > distributor running on the server with the publications. it looks like this: > > Cluster 1 has 2 databases that have 3 publications -distributor is here > ClusterA - subscribes to one publication > ClusterB - subscribes to 2 publications > ClusterC - subscribes to all 3 publications > > replicationis working perfectly for ClusterA and ClusterB, but ClusterC > (really named ove-crmsql01) fails with the following error: > > The process could not connect to Subscriber 'OVE-CRMSQL01'. (Source: > MSSQL_REPL, Error number: MSSQL_REPL0) > Get help:http://help/MSSQL_REPL0 > TCP Provider: No connection could be made because the target machine > actively refused it. (Source: MSSQLServer, Error number: 10061) > Get help:http://help/10061 > 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: 10061 > > The distributor is connecting to the subscriber with a sql server > authenticated user that has sysadmin permissions, and I've made sure that I > can connect from Cluster1 to ClusterA using Management Studio. > > Our network admins insist there isn't a firewall between the two, so what > can I be missing? this is driving me crazy... > > Thanks for the help! > > -Susan Are you using windows or SQL Server authentication? Make sure that the DistributorSecurityMode is correctly set (1 for windows and zero for SQL Server authentication). Peter Redei
From: Susan Cooper on 17 Sep 2008 13:15 Hi Peter, thanks for the response, but I'm not sure that's the issue. The security is set exactly the same for all of the servers. One more thing to mention - Replication was working for all of the servers until I rebuilt replication last night. We had a CRM deployment that requires us to kill replication and rebuild it. I scripted all of the publications and subscriptions, then used those scripts to rebuild replication. I also should mention that we recently had a data center move. Before the move, the server I'm having trouble with was a different subnet, so all of the servers were in the same subnet except the one having trouble with. After the data center move, the servers are all now in the subnet. any ideas? thanks! -Susan "predei(a)voltdelta.com" wrote: > On Sep 17, 8:32 am, Susan Cooper > <SusanCoo...(a)discussions.microsoft.com> wrote: > > Hi, > > > > I've setuptransactionalreplicationon 4 SQL Server 2005 clustered servers. > > I have three different publications all configured aspushwith the > > distributor running on the server with the publications. it looks like this: > > > > Cluster 1 has 2 databases that have 3 publications -distributor is here > > ClusterA - subscribes to one publication > > ClusterB - subscribes to 2 publications > > ClusterC - subscribes to all 3 publications > > > > replicationis working perfectly for ClusterA and ClusterB, but ClusterC > > (really named ove-crmsql01) fails with the following error: > > > > The process could not connect to Subscriber 'OVE-CRMSQL01'. (Source: > > MSSQL_REPL, Error number: MSSQL_REPL0) > > Get help:http://help/MSSQL_REPL0 > > TCP Provider: No connection could be made because the target machine > > actively refused it. (Source: MSSQLServer, Error number: 10061) > > Get help:http://help/10061 > > 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: 10061 > > > > The distributor is connecting to the subscriber with a sql server > > authenticated user that has sysadmin permissions, and I've made sure that I > > can connect from Cluster1 to ClusterA using Management Studio. > > > > Our network admins insist there isn't a firewall between the two, so what > > can I be missing? this is driving me crazy... > > > > Thanks for the help! > > > > -Susan > > Are you using windows or SQL Server authentication? Make sure that the > DistributorSecurityMode is correctly set (1 for windows and zero for > SQL Server authentication). > > Peter Redei >
From: bhaskar on 26 Sep 2008 16:15 Susan, the windows-ID / SQL Agent Id used to connect to clusterA,B should have login in Cluster-C as well. if you do not have a sql-login/windowslogin defined on cluster-c and try to connect , you com across such errors. compare sql-logins across A,B,C. I had this problem last week. Once i created Login(on cluster-c) for the windows-id , i was able to replicate again. Hope this helps. "Susan Cooper" wrote: > Hi Peter, > > thanks for the response, but I'm not sure that's the issue. The security is > set exactly the same for all of the servers. One more thing to mention - > Replication was working for all of the servers until I rebuilt replication > last night. We had a CRM deployment that requires us to kill replication and > rebuild it. I scripted all of the publications and subscriptions, then used > those scripts to rebuild replication. > > I also should mention that we recently had a data center move. Before the > move, the server I'm having trouble with was a different subnet, so all of > the servers were in the same subnet except the one having trouble with. > After the data center move, the servers are all now in the subnet. > > any ideas? > > thanks! > -Susan > > "predei(a)voltdelta.com" wrote: > > > On Sep 17, 8:32 am, Susan Cooper > > <SusanCoo...(a)discussions.microsoft.com> wrote: > > > Hi, > > > > > > I've setuptransactionalreplicationon 4 SQL Server 2005 clustered servers. > > > I have three different publications all configured aspushwith the > > > distributor running on the server with the publications. it looks like this: > > > > > > Cluster 1 has 2 databases that have 3 publications -distributor is here > > > ClusterA - subscribes to one publication > > > ClusterB - subscribes to 2 publications > > > ClusterC - subscribes to all 3 publications > > > > > > replicationis working perfectly for ClusterA and ClusterB, but ClusterC > > > (really named ove-crmsql01) fails with the following error: > > > > > > The process could not connect to Subscriber 'OVE-CRMSQL01'. (Source: > > > MSSQL_REPL, Error number: MSSQL_REPL0) > > > Get help:http://help/MSSQL_REPL0 > > > TCP Provider: No connection could be made because the target machine > > > actively refused it. (Source: MSSQLServer, Error number: 10061) > > > Get help:http://help/10061 > > > 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: 10061 > > > > > > The distributor is connecting to the subscriber with a sql server > > > authenticated user that has sysadmin permissions, and I've made sure that I > > > can connect from Cluster1 to ClusterA using Management Studio. > > > > > > Our network admins insist there isn't a firewall between the two, so what > > > can I be missing? this is driving me crazy... > > > > > > Thanks for the help! > > > > > > -Susan > > > > Are you using windows or SQL Server authentication? Make sure that the > > DistributorSecurityMode is correctly set (1 for windows and zero for > > SQL Server authentication). > > > > Peter Redei > >
From: Susan Cooper on 29 Sep 2008 07:19
thanks for the suggestion. I've run into that same problem in the past, so I'd already checked that. Turns out that the problem was caused by tcp/ip somehow getting turned off on the target box. I still have no idea how that happened... "bhaskar" wrote: > Susan, the windows-ID / SQL Agent Id used to connect to clusterA,B should > have login in Cluster-C as well. if you do not have a sql-login/windowslogin > defined on cluster-c and try to connect , you com across such errors. compare > sql-logins across A,B,C. I had this problem last week. Once i created > Login(on cluster-c) for the windows-id , i was able to replicate again. Hope > this helps. > > "Susan Cooper" wrote: > > > Hi Peter, > > > > thanks for the response, but I'm not sure that's the issue. The security is > > set exactly the same for all of the servers. One more thing to mention - > > Replication was working for all of the servers until I rebuilt replication > > last night. We had a CRM deployment that requires us to kill replication and > > rebuild it. I scripted all of the publications and subscriptions, then used > > those scripts to rebuild replication. > > > > I also should mention that we recently had a data center move. Before the > > move, the server I'm having trouble with was a different subnet, so all of > > the servers were in the same subnet except the one having trouble with. > > After the data center move, the servers are all now in the subnet. > > > > any ideas? > > > > thanks! > > -Susan > > > > "predei(a)voltdelta.com" wrote: > > > > > On Sep 17, 8:32 am, Susan Cooper > > > <SusanCoo...(a)discussions.microsoft.com> wrote: > > > > Hi, > > > > > > > > I've setuptransactionalreplicationon 4 SQL Server 2005 clustered servers. > > > > I have three different publications all configured aspushwith the > > > > distributor running on the server with the publications. it looks like this: > > > > > > > > Cluster 1 has 2 databases that have 3 publications -distributor is here > > > > ClusterA - subscribes to one publication > > > > ClusterB - subscribes to 2 publications > > > > ClusterC - subscribes to all 3 publications > > > > > > > > replicationis working perfectly for ClusterA and ClusterB, but ClusterC > > > > (really named ove-crmsql01) fails with the following error: > > > > > > > > The process could not connect to Subscriber 'OVE-CRMSQL01'. (Source: > > > > MSSQL_REPL, Error number: MSSQL_REPL0) > > > > Get help:http://help/MSSQL_REPL0 > > > > TCP Provider: No connection could be made because the target machine > > > > actively refused it. (Source: MSSQLServer, Error number: 10061) > > > > Get help:http://help/10061 > > > > 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: 10061 > > > > > > > > The distributor is connecting to the subscriber with a sql server > > > > authenticated user that has sysadmin permissions, and I've made sure that I > > > > can connect from Cluster1 to ClusterA using Management Studio. > > > > > > > > Our network admins insist there isn't a firewall between the two, so what > > > > can I be missing? this is driving me crazy... > > > > > > > > Thanks for the help! > > > > > > > > -Susan > > > > > > Are you using windows or SQL Server authentication? Make sure that the > > > DistributorSecurityMode is correctly set (1 for windows and zero for > > > SQL Server authentication). > > > > > > Peter Redei > > > |