The merge process could not clean up the subscription

Answered The merge process could not clean up the subscription

  • Friday, December 07, 2012 10:09 PM
     
     

    hi,

    I made a merge replication and used a push subscription , i always got the following error:
    Error messages:
    The merge process could not clean up the subscription to 'RTSSRVSQL1':'RALADA:'RALADAAfterShrinkPub'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
    Get help: http://help/MSSQL_REPL-2147200965
    Parameter 1 is incorrect for this DBCC statement. (Source: MSSQLServer, Error number: 2560)
    Get help: http://help/2560
    The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, and reregister the subscription if necessary. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201011)
    Get help: http://help/MSSQL_REPL-2147201011

    and one more thing if i create pull subscription i got the status uninitialized subscription


    Any help will appreciated

    Thanks

    Ahmad


    • Edited by aabdan Saturday, December 08, 2012 7:14 AM
    •  

All Replies

  • Saturday, December 08, 2012 8:21 AM
    Moderator
     
     

    Hi Ahmad,

    Has the subscription database been a subscriber in the past?  Or does the subscription database have any other existing subscriptions?

    If so, you may want to execute sp_dropmergesubscription at the Publisher to remove any orphaned metadata.  Also, if the subscription database does not have any other existing subscriptions then execute sp_removedbreplication at the subscriber to remove any orphaned metadata.

    If you are getting uninitialized subscription message when you do a pull subscription then you will need to generate a new snapshot and start the Merge Agent to initialize the subscription.


    Brandon Williams (blog | linkedin)

  • Saturday, December 08, 2012 11:17 AM
     
     

    Hi Brandon,

    Thanks for replying

    the subscription database doesn't have any subscriber or subscriptions because it's new.

    Note:

    1 - the replication process stopped after replicate DB schema(tables) then we get this error

    2 - i tried replicate a two tables from database and it's working(schema and data) without any problems!!


    • Edited by aabdan Saturday, December 08, 2012 11:56 AM
    •  
  • Saturday, December 08, 2012 7:12 PM
     
     Answered

    Hi Brandon,

    thank you for trying to help

    just to know who face this issue it was becuase there is some errors in views like accessing from other databases which is not exist.

    Regards,

  • Saturday, December 08, 2012 7:20 PM
    Moderator
     
     

    Hi Ahmad,

    That is good to hear.  So is your issue resolved?


    Brandon Williams (blog | linkedin)

  • Sunday, December 09, 2012 2:48 AM
     
     
    yes, everything is working now.