Replication failing with Merge process could not enumerate

  • 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
  • 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.

  • 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
  • Oh and thank you for replying earlier appreciate your time 🙂

    Time to make a change
  • 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....

  • i've the same problem.

    Do you have a issue ?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply