locked
Another merge agent for the subscription or subscriptions is running, or the server is working on a previous request by the same agent. RRS feed

  • Question

  • Hi All,

    Using Merge Replication over the web (https). Server is running SQL Server 2008, client using SQL Server Express 2008.

    I am getting these error messages while trying to synchronize, and it won't let me sync:

    {call sp_MSensure_single_instance (N'{459D0BBA-53EC-4F65-AF52-E7DA478841DA}', 4)}

    Another merge agent for the subscription or subscriptions is running, or the server is working on a previous request by the same agent.

    Can you please advice what can be done to fix. Do I need to kill a process in SQL Server?

    Tuesday, April 20, 2010 3:36 PM

Answers

  • Hi Carlos,


    If there is no blocking and parallel job running, it might be a connectivity issue. I suggest the following modifications in the registry:

    Change 1
    =======
    1. Click Start, click Run, type regedit , and then click OK.
    2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    3. Check whether you find a DWORD Value EnableRSS.
    4. Double-click EnableRSS, type 0 , and then click OK.

    Change 2
    =======
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    1. Check whether you find a DWORD Value EnableTCPA.
    2. Double-click EnableTCPA, type 0 , and then click OK.

    Change 3
    =======
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    1. Check whether you find a DWORD Value EnableTCPChimney.
    2. Double-click EnableTCPChimney, type 0 , and then click OK.

    Change 4
    ========
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    1. On the Edit menu, point to New, click DWORD Value, and then type
    DisableTaskOffload .
    2. Double-click DisableTaskOffload , type 1 , and then click OK.
    3. Exit Registry Editor.


    If there are any more problems, please let me know.
    Thanks.


    ***Xiao Min Tan***Microsoft Online Community***
    Monday, April 26, 2010 7:02 AM

All replies

  • Try deleting the contents of
    MSsnapshotdeliveryprogress to see if this fixes the problem.


    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941
    • Marked as answer by Carlos Araya Thursday, April 22, 2010 4:40 PM
    • Unmarked as answer by Carlos Araya Thursday, April 22, 2010 4:41 PM
    • Proposed as answer by gnease Friday, March 22, 2013 10:44 PM
    Tuesday, April 20, 2010 5:12 PM
    Answerer
  • Hi,


    Generally, the error above indicates that there is another merge job which is running or in hung state and not letting this merge agent job to run through, and making it to fail. The agent can handle only a Single job at a time.

    To troubleshoot the issue, try the following steps:
    1. Check if any job is running at the same time. If so, you could wait for the job competed and then run your merge replication again.
    2. Execute sp_who2 on the Publisher and Subscriber servers to check any blocking.

    If there are any more problems, please let me know.
    Thanks.


    ***Xiao Min Tan***Microsoft Online Community***
    • Marked as answer by Carlos Araya Thursday, April 22, 2010 4:41 PM
    • Unmarked as answer by Carlos Araya Thursday, April 22, 2010 7:57 PM
    Thursday, April 22, 2010 3:41 AM
  • Hi,

    Thanks, I did not know the agent could handle a single job at a time.

    The replication eventually made it through when I retried later, I guess because there was no agent running at the same time at that time.

    Thanks,
    Carlos

    Thursday, April 22, 2010 4:38 PM
  • Hi Xiao,

    I have the same issue with a different subscription. I tried the two steps you specified and did not find jobs running at the same time.

    Also ran sp_who2 on the Publisher and Subscriber and found no blockings.

    What else can be tried?

    Thanks,
    Carlos

    Thursday, April 22, 2010 8:01 PM
  • Hi Carlos,


    If there is no blocking and parallel job running, it might be a connectivity issue. I suggest the following modifications in the registry:

    Change 1
    =======
    1. Click Start, click Run, type regedit , and then click OK.
    2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    3. Check whether you find a DWORD Value EnableRSS.
    4. Double-click EnableRSS, type 0 , and then click OK.

    Change 2
    =======
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    1. Check whether you find a DWORD Value EnableTCPA.
    2. Double-click EnableTCPA, type 0 , and then click OK.

    Change 3
    =======
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    1. Check whether you find a DWORD Value EnableTCPChimney.
    2. Double-click EnableTCPChimney, type 0 , and then click OK.

    Change 4
    ========
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    1. On the Edit menu, point to New, click DWORD Value, and then type
    DisableTaskOffload .
    2. Double-click DisableTaskOffload , type 1 , and then click OK.
    3. Exit Registry Editor.


    If there are any more problems, please let me know.
    Thanks.


    ***Xiao Min Tan***Microsoft Online Community***
    Monday, April 26, 2010 7:02 AM
  • I had the same issue with two different subscribers (pull subscriptions) to the same merge replication publication.  In one case, it was a permissions issue.  The client was using SQL Server authentication and the user was not added to the publication access list (see Publication properties.) 

    For the other subscriber, with the exact same error message, it turned out that a network connection was lost in the middle of a synchronization.  This caused some orphan merge agent processes on the publisher to remain and prevented the subscriber's merge agent from running again.  If you run query SELECT * FROM sys.sysprocesses you will see the hostname of the subscriber and program_name with the merge agent job name.  You will need to kill these orphan processes.

    Tuesday, August 31, 2010 8:22 PM