Problem with SQL Server Managment Studio 2012 (Replication)

DymekPL 1 Reputation point


I have a problem with replication in SQL Server Managment Studio 2012.

I have to replicate 140 locations and when I start from beginning (0 locations) everything is fine. I do 70-80 replications for 2-3 days and there is no problem with that. The problem appears after some time (about 2 weeks) when I want to add another location.

I add another location, the agent starts, I check "View synchronization status" and gets this information:


"The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. "

And it will keep trying forever.

If I started from beginning everything works again ...

Any suggestions?



SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,265 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. CathyJi-MSFT 21,121 Reputation points Microsoft Vendor

    Hi @DymekPL ,

    > The problem appears after some time (about 2 weeks) when I want to add another location.

    Did you mean add a new subscriber to merge replication? Then the replication sync failed?

    Please share us more related error message from replication monitor as below screenshot.


    The error message that you offered is a general error message. You can maximize the history logging by selecting 3 for the –HistoryVerboseLevel property of the Snapshot Agent and Merge Agent as below screenshot. The more log information you will have, it will be better to find out and identify the merge replication problems.




    To enable detailed logging by the Replication Agent. You will need to stop and restart the Replication Agent for the setting to take effect.

    If the response is helpful, please click "Accept Answer" and upvote it, thank you.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. DymekPL 1 Reputation point


    Thanks a lot for qucik answer!!

    These logs will be automatically saved (where can I find them)? Or I need to add the "-output c: /log.txt" parameter? Or something?


    I added the agent run logs (photo above) but it is probably not about these logs :)


    0 comments No comments

  3. DymekPL 1 Reputation point

    More logs with parameters:
    -output c:/log.txt -outputverboselevel 3


    0 comments No comments

  4. CathyJi-MSFT 21,121 Reputation points Microsoft Vendor

    Hi @DymekPL ,

    > 2021-03-19 10:00:01.315 The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process.

    Please try to increase the default time out period for “–QueryTimeOut” then restart the Merge agent.


    Did you see any other useful error information from replication monitor?

    0 comments No comments