That would probably do it. I think there is a list of agents in the replication monitor where you might be able to shut off the log reader. How many times have you set up replication?
The process could not connect to Subscriber- replication. Folks, I'm having trouble setting up replication from a server hosted outside our domain that is hosted in Mar 14, 2012 · Replication-Replication Distribution Subsystem: agent HOU-CX-01-CT-ca_tables-HOU-SQL02-5 failed. The process could not connect to Subscriber 'HOU-SQL02'. I can ping the subscriber system with no problem. Thanks in advance for any help! Jan 05, 2011 · 2011-01-05 10:50:00:112 The process could not connect to Subscriber 'TuitionaffordableREP1'. 2011-01-05 10:50:00:112 The agent failed with a 'Retry' status. Try to run the agent at a later time. Apr 04, 2008 · "The process could not connect to subscriber", on workgroup If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. RE: Replication failure- the process could not connect to subscriber LOS (IS/IT--Management) 13 Nov 00 07:08 One of the problems I encountered in setting up a Merge between two servers in different locations is that you need to set-up an OS_Shell Job to dial-up. May 28, 2003 · I have a domain user named domain_user in both the publisher and the subscriber. Although, the domains for these two users are different: (ie. office1 and officermt). My startup account for the server and server agent for the SqlServer in my remote domain (officermt, the publisher) is domain_user and this is not true for the subscriber. The process could not connect to Subscriber 'WEBDB3'. If i open Replication monitor: SQL 2008 R2 replication error: The process could not connect to Distributor. 0.
When trying to connect to that network, the process fails before I can even connect and be presented with an xfinitywifi login dialog. " Non-Comcast subscriber access is limited to complimentary passes or the purchase of WiFi On Demand passes.
Mar 14, 2012 · Replication-Replication Distribution Subsystem: agent HOU-CX-01-CT-ca_tables-HOU-SQL02-5 failed. The process could not connect to Subscriber 'HOU-SQL02'. I can ping the subscriber system with no problem. Thanks in advance for any help! Jan 05, 2011 · 2011-01-05 10:50:00:112 The process could not connect to Subscriber 'TuitionaffordableREP1'. 2011-01-05 10:50:00:112 The agent failed with a 'Retry' status. Try to run the agent at a later time. Apr 04, 2008 · "The process could not connect to subscriber", on workgroup If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed.
Mar 27, 2002 · Agent message code 20084. The process could not connect to Distributor 'TRIWEB02'. [3/25/2002 2:58:47 PM]D0115\VSdotNET.replicationTest: exec dbo.sp_MSupdatelastsyncinfo N'TRIWEB02',N'Northwind', N'', 0, 6, N'The process could not connect to Distributor ''TRIWEB02''.' Disconnecting from Subscriber 'D0115\VSdotNET'
This merge replication error: The merge process could not connect to the Publisher ‘Server:database’ is so misleading We have a merge topology in place with pull subscriptions, this is the merge agent runs at the subscribers. That would probably do it. I think there is a list of agents in the replication monitor where you might be able to shut off the log reader. How many times have you set up replication?