The merge process could not access row data at the '%1'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to write to, or run the SQL Profiler utility to identify the source of the failure.
The Merge Agent was unable to start the SQL Server Agent job to generate the partitioned snapshot for this subscription. ...
The Merge Agent was unable to synchronize the row due to one or more unanticipated errors in the batch of changes. When troubleshooting, ...
The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription ...
The merge process cleaned up %1!d! row(s) in MSmerge_genhistory, %2!d! row(s) in MSmerge_contents, and %3!d! row(s) in MSmerge_tombstone. ...
The merge process could not access row data at the '%1'. When troubleshooting, restart the synchronization with verbose history ...
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the ...
The merge process could not delete retry information at the Publisher on tempdb. This may be due to too much activity on ...
The merge process could not enumerate changes at the '%1'. When troubleshooting, restart the synchronization with verbose ...
The merge process could not enumerate deletions at the '%1'. Troubleshoot by restarting the synchronization with verbose ...