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

Replication failing with Merge process could not enumerate Expand / Collapse
Author
Message
Posted Monday, August 06, 2012 3:01 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, May 10, 2013 4:42 AM
Points: 38, Visits: 93
Hi All,

Out of the blue my SQL server started going slow sporadically and every so often throws up some errors.

SQL Sever : 2008
Windows Server : 2008
Merge replication with 1 subscriber

The error that is occurring...

Error messages:
The merge process could not enumerate changes at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200999)
Get help: http://help/MSSQL_REPL-2147200999
TCP Provider: An existing connection was forcibly closed by the remote host. (Source: MSSQLServer, Error number: 10054)
Get help: http://help/10054
Communication link failure (Source: MSSQLServer, Error number: 10054)
Get help: http://help/10054
Protocol error in TDS stream (Source: MSSQLServer, Error number: 0)
Get help: http://help/0

Has anyone come across this before??
How does one switch on verbose logging for a merge replication?

Thanks

Reggie


Time to make a change

Post #1340424
Posted Monday, August 06, 2012 4:51 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 5:35 AM
Points: 1,327, Visits: 4,483
I have seen this message (and various others) frequently when trying to replicate over slow/poor quality network connections and/or poorly performing servers. They have usually been followed (eventually) by a successful sync.

To set verbose logging, you need to set the -Output and -OutputVerboseLevel parameters on the merge agent job.



Post #1340511
Posted Monday, August 06, 2012 7:06 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, May 10, 2013 4:42 AM
Points: 38, Visits: 93
Yeah everything points to a problem with connectivity between the two SQL servers.. I just need to prove that now!!

They are across VPN's where traditionally the speed hasnt been an issue.. anybody have any ideas on ways I can watch the traffice between the two servers?


Time to make a change

Post #1340578
Posted Monday, August 06, 2012 7:07 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, May 10, 2013 4:42 AM
Points: 38, Visits: 93
Oh and thank you for replying earlier appreciate your time :)

Time to make a change

Post #1340579
Posted Thursday, July 04, 2013 8:01 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, October 17, 2013 10:41 PM
Points: 3, Visits: 42
Hi All,

Ya this is one of the major issue , For me , distribtion , publisher , subscriber all are in the same instance, Even I have also getting the same issue....But we couldnt find the any sepecific Error message even in verbose log itself. Any body have solution....
Post #1470546
Posted Monday, March 31, 2014 6:01 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 08, 2014 10:10 AM
Points: 1, Visits: 5
i've the same problem.

Do you have a issue ?
Post #1556437
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse