Results 1 to 2 of 2
  1. #1
    Join Date
    Jan 2003
    Location
    Santa Fe, NM
    Posts
    5

    Unhappy Unanswered: SQL Agent & replication Merge Agent

    I am experiencing strange behavior by SQL Server Agent, and a replication Merge Agent. In the publisher SQL Server, we get the error cannot start the job when SQL Server Agent is starting. However, the agent icon, etc indicate that it is indeed running.


    The agent on the subscriber is working. When I run the Merge Agent from either machine, it seems to start, and then time out.

    I do get this error message, but it is too cryptic for me:

    -------------------------------------------------------------
    Category:COMMAND
    Source: Failed Command
    Number: 0
    Message: {?=call [sp_upd_73F052A0694D44811A4D222D622D416F] (?,?,?,?,?,?,?, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , )}{?=call [sp_upd_73F052A0694D44811A4D222D622D416F] (?
    -------------------------------------------------------------


    These are the error 'details' for the above:

    The process could not deliver update(s) at the 'Publisher'.
    (Source: Merge Replication Provider (Agent);
    Error number: -2147200989)
    ---------------------------------------------------------------------------------------------------------------
    The merge process timed out while executing a query. Reconfigure the QueryTimeout parameter and retry the operation.
    (Source: NMEMNRDSQL (Data source); Error number: 0)
    ---------------------------------------------------------------------------------------------------------------



    This is become of major concern here!
    Thanks for any help!
    MichaelGG

  2. #2
    Join Date
    Jun 2003
    Location
    cape town, south africa
    Posts
    102
    Hi

    run sp_helpmergesubscription,sp_helpsubscription for trans & merge...make sure all articles are correctly listed.

    Also, if it is a timout issue, right click on replciation monitor, choose "refresh rate & settings" and increase thamount of time t will consider an agent faulty after .

    Had this problem when publications meta data is a mess, if possible a complete fresh start is advisable. But make sure all info of previous publications is completely eradicated...

    DesmondX

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •