Merge/Replication working intermittently

Last Post 24 Oct 2011 06:36 AM by rm. 1 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Paul
New Member
New Member

--
12 Oct 2011 06:03 AM
Guys

I have a situation where i am publishing to a subscriber in a different windows domain, separated by firewalls.
Both are sql 2008 and uses a witness, and the subscriber connection dbase authentication uses a local sql account.

This works intermittently, it's scheduled to start every 10mins, and when it works it works fine, no problems, so i know the network & firewalls are all ok.

It seems to be developing a pattern of working 3 times, then fails 2 times, then works 3 times etc etc but i cant see where/why its failing ....

ANY IDEAS ??!?!??

When it fails i get the following in the logfile viewer on the distributor:-
[On the agent profile for this subscription (mirroring high volume server-toserver Profile), i have increased the LoginTimeout from 15 to 90 and QueryTimeout from 300 to 950]



Message
2011-10-12 12:30:00.712 Connecting to Publisher 'CRICK-LON1-A'
2011-10-12 12:31:31.760 Connecting to Subscriber 'burgess-cam2-a\dbaccounting'
2011-10-12 12:31:31.760 The process could not connect to Subscriber 'burgess-cam2-a\dbaccounting'.
2011-10-12 12:31:31.760 Category:AGENT
Source: burgess-cam2-a\dbaccounting
Number: 20084
Message: The process could not connect to Subscriber 'burgess-cam2-a\dbaccounting'.
2011-10-12 12:31:31.760 Category:SQLSERVER
Source: burgess-cam2-a\dbaccounting
Number: -1
Message: SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
2011-10-12 12:31:31.760 Category:SQLSERVER
Source: burgess-cam2-a\dbaccounting
Number: -1
Message: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
2011-10-12 12:31:31.760 Category:SQLSERVER
Source: burgess-cam2-a\dbaccounting
Number: 0
Message: Login timeout expired
2011-10-12 12:31:31.760 Category:SQLSERVER
Source: burgess-cam2-a\dbaccounting
Number: 0
Message: The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
2011-10-12 12:31:31.760 Category:NULL
Source: Merge Process
Number: -2147201019
Message: The subscription to publication 'Primary' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription.
2011-10-12 12:31:31.760 The merge process will restart after waiting 30 second(s)...


Connecting to Distributor 'FULTON-LON1-C'
2011-10-12 12:32:01.777 Initializing
2011-10-12 12:32:01.777 Connecting to Publisher 'CRICK-LON1-A'
2011-10-12 12:33:32.840 Connecting to Subscriber 'burgess-cam2-a\dbaccounting'
2011-10-12 12:33:32.840 The process could not connect to Subscriber 'burgess-cam2-a\dbaccounting'.
2011-10-12 12:33:32.840 Category:AGENT
Source: burgess-cam2-a\dbaccounting
Number: 20084
Message: The process could not connect to Subscriber 'burgess-cam2-a\dbaccounting'.
2011-10-12 12:33:32.856 Category:SQLSERVER
Source: burgess-cam2-a\dbaccounting
Number: -1
Message: SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
2011-10-12 12:33:32.856 Category:SQLSERVER
Source: burgess-cam2-a\dbaccounting
Number: -1
Message: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
2011-10-12 12:33:32.856 Category:SQLSERVER
Source: burgess-cam2-a\dbaccounting
Number: 0
Message: Login timeout expired
2011-10-12 12:33:32.856 Category:SQLSERVER
Source: burgess-cam2-a\dbaccounting
Number: 0
Message: The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
2011-10-12 12:33:32.856 Category:NULL
Source: Merge Process
Number: -2147201019
Message: The subscription to publication 'Primary' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription
rm
New Member
New Member

--
24 Oct 2011 06:36 AM
Sounds network related issue to me. By the way, you use witness for replication? How?
You are not authorized to post a reply.

Acceptable Use Policy