SQL Server 2016
- The Merge Agent failed after detecting that retention-based metadata cleanup, deleted metadata at the Publisher for changes ...
- The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the ...
- The Merge Agent failed to add an application header to a message during Web synchronization. When troubleshooting, restart ...
- The Merge Agent failed to add or update the subscription entry in the distribution database. When troubleshooting, restart ...
- The Merge Agent failed to apply replication metadata. When troubleshooting, increase the -OutputVerboseLevel setting and ...
- The Merge Agent failed to connect to the Internet proxy server for user '%1' during Web synchronization. Ensure that the ...
- The Merge Agent failed to connect to the Web server or Internet proxy server using authentication mode %1. Ensure that the ...
- The Merge Agent failed to create a partitioned snapshot job for this subscription. When troubleshooting, use SQL Profiler ...
- The Merge Agent failed to delete a batch of rows because of the following error: %1. When troubleshooting, use SQL Profiler ...
- The Merge Agent failed to determine if the subscription has expired. When troubleshooting, use SQL Profiler or restart the ...
- The Merge Agent failed to determine the location of the partitioned snapshot generated for this subscription. When troubleshooting, ...
- The Merge Agent failed to drop the table used to store retry information. This can occur when there is too much activity ...
- The Merge Agent failed to enumerate retry information. This can occur when there is too much activity on the tempdb system ...
- The Merge Agent failed to generate a request message during Web synchronization. When troubleshooting, restart the Merge ...
- The Merge Agent failed to insert a batch of rows because of the following error: %1. When troubleshooting, use SQL Profiler ...
- The Merge Agent failed to locate the partitioned snapshot for this subscription in the expected location. If the publication ...
- The Merge Agent failed to obtain a new set of identity ranges for the Subscriber. When troubleshooting, restart the Merge ...
- The Merge Agent failed to retrieve article information for publication '%1'. Increase the -QueryTimeOut parameter and restart ...
- The Merge Agent failed to retrieve information about received generations for server subscriptions from the '%1' database. ...
- The Merge Agent failed to retrieve information for resolver '%1' with CLSID '%2'. When troubleshooting, use SQL Profiler ...
- The Merge Agent failed to retrieve Publisher properties. When troubleshooting, use SQL Profiler or restart the agent with ...
- The Merge Agent failed to retrieve replication state information from the '%1' database. When troubleshooting, use SQL Profiler ...
- The Merge Agent failed to retrieve the Publisher's comparison style. When troubleshooting, use SQL Profiler or restart the ...
- The Merge Agent failed to retrieve the Publisher's location identifier. When troubleshooting, use SQL Profiler or restart ...
- The Merge Agent failed to retrieve the snapshot schema script file '%1'. Run the Snapshot Agent to regenerate the snapshot ...
- The Merge Agent failed to update a batch of rows because of the following error: %1. When troubleshooting, use SQL Profiler ...
- The Merge Agent failed to update received generation information in the '%1' database. When troubleshooting, use SQL Profiler ...
- The Merge Agent failed to update replication state information in the '%1' database. When troubleshooting, use SQL Profiler ...
- The Merge Agent failed to update retry information. This can occur when there is too much activity on the tempdb system database. ...
- The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with ...
- The Merge Agent failed when initializing the Snapshot Agent to create the snapshot. When troubleshooting, check the Snapshot ...
- The Merge Agent failed while registering the publication id in the snapshot progress table. When troubleshooting, restart ...
- The Merge Agent has encountered an unanticipated empty string on line %1!d! of file %2. When troubleshooting, ensure that ...
- The Merge Agent has encountered an unanticipated null pointer on line %1!d! of file %2. When troubleshooting, ensure that ...
- The Merge Agent process could not write Web synchronization metadata in the message header. Verify that there is sufficient ...
- The Merge Agent received the following error status and message from the Internet Information Services (IIS) server during ...
- The Merge Agent was unable to connect to the Publisher using SQL Server Authentication. Ensure that the Publisher login used ...
- The Merge Agent was unable to determine if another subscription exists for the same partition. Restart the synchronization, ...
- The Merge Agent was unable to generate a partitioned snapshot for this subscription; either the Snapshot Agent failed to ...
- The Merge Agent was unable to mark the subscription as validated. When troubleshooting, use SQL Profiler or restart the agent ...
- The Merge Agent was unable to obtain a required lock on the table article '%1' needed to perform data validation. Restart ...
- The merge agent was unable to replicate one or more deletes to the '%1'. When troubleshooting, look for errors executing ...
- 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 ...
- The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, ...
- The merge process could not perform retention-based metadata cleanup in database '%1'. If this failure continues, try increasing ...
- The merge process could not query the last generation received from the Publisher. If this failure persists, reinitialize ...
- The merge process could not register an alternate synchronization partner. Troubleshoot by restarting the synchronization ...
- The merge process could not remove the registration for an alternate synchronization partner. When troubleshooting, restart ...
- The merge process could not replicate one or more INSERT statements to the '%1'. A stored procedure failed to execute. Troubleshoot ...
- The merge process could not replicate one or more UPDATE statements to the '%1' because a stored procedure failed to execute. ...
- The merge process could not retrieve column information for table '%1.%2'. Verify that you have sufficient privileges on ...
- The merge process could not retrieve generation information at the '%1'. If this failure persists, reinitialize the subscription. ...
- The merge process could not retrieve schema information from the Publisher. When troubleshooting, use SQL Profiler or restart ...
- The merge process could not retrieve the last generation received from the Publisher. If this failure persists, reinitialize ...
- The merge process could not store conflict information for article '%1'. Check the publication properties to determine where ...
- The merge process could not store delete conflict information for an article. Check the publication properties to determine ...
- The merge process could not update the last generation received from the Publisher. If this failure persists, reinitialize ...
- The merge process could not update the last sent generation sent to the Publisher. If this failure persists, reinitialize ...
- The merge process detected a mismatch while evaluating the subscriber partition validation expression. The problem can be ...
- The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some ...
- The merge process failed to enumerate changes in articles with parameterized row filters. If this failure continues, increase ...
- The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout ...
- The merge process failed to get correct information about the Interactive Resolver component from the registry. Verify that ...
- The merge process failed when obtaining a new identity range for the subscriber, or failed to determine if the subscriber ...
- The merge process timed out while making a connection. Increase the login timeout for this process (-LoginTimeOut). When ...
- The merge process was unable to access metadata at the '%1' that was needed to retry an operation. When troubleshooting, ...
- The merge process was unable to access row metadata at the '%1'. When troubleshooting, restart the synchronization with verbose ...