Merge Replication not working with Mirroring for merge subscriber when publisher and subscriber in different domains


  • We tried creating Merge replication with Sync_Type as "None" along with Mirroring for merge subscriber but were getting following error when publisher and subscriber are in different domain (principal subscriber and mirror subscriber are in same domain):

    {call sp_MSsetconflicttable (N'acl_form_group_permission', N'MSmerge_conflict_dmsdb_master_Merge_Repl_acl_form_group_permission', N'ASTDB01\DDMASTER', N'dmsdb_master', N'dmsdb_master_Merge_Repl')}

    The same scenario is working fine when publisher and subscriber are within same domain.

    Any help will be highly appreciated.

    Thank you,


    Tuesday, November 20, 2012 8:53 AM

All replies

  • Are the domains for publisher and subscriber server trusting each other ? For merge replication to work fine across servers in differnet domains..the domains need to trust each other.. 

    Gaurav Mathur | Please mark solved if I've answered your question
    This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, November 20, 2012 11:40 AM
  • I have tried the same scenarion on same servers, But by creating new databases and it worked fine.

    But it is not working on the database on which we are trying to setup. Also (just for information) we are using Push Subscription

    So it seems the domains trust each other. 
    Tuesday, November 20, 2012 1:39 PM
  • Hi Aakash,

    It looks like the account you are using to connect to the Subscriber is impersonating the process account which is ASTDB01\DDMASTER and will not work over non-trusted domains unless you are using pass-through authentication.

    Try using SQL Server Authentication for the account used to connect to the Subscriber.  Make sure this account is a member of the db_owner fixed database role in the subscription database.

    Brandon Williams (blog | linkedin)

    Tuesday, November 20, 2012 6:22 PM
  • By any chance did you deploy this via a no-sync subscription?

    looking for a book on SQL Server 2008 Administration? looking for a book on SQL Server 2008 Full-Text Search?

    Tuesday, November 20, 2012 6:28 PM
  • Actually I can now see that you did do a no-sync. There are issues with no-sync merge subscriptions and Microsoft recommends you do not do this. Any way you can do it via a sync subscription?

    looking for a book on SQL Server 2008 Administration? looking for a book on SQL Server 2008 Full-Text Search?

    Tuesday, November 20, 2012 6:29 PM
  • Hi Brandon,

    We were also thinking what You suggested must be the issue.. but then same scenario works for other database on the same server..:(
    Wednesday, November 21, 2012 2:01 AM
  • We need to implement mirroring as well as merge replication.. So it is not possible to use sync_type other than 'none' ... 
    Wednesday, November 21, 2012 2:03 AM
  • We found out that different domain was not an issue since we were using SQL Server Authentication.

    We were using same name for Merge Replication publisher, subscriber and mirror of subscriber. And in that case we were getting the error as described above. What worked though was changing the database name of either the publisher or subscriber.

    We tried two things:

    1.     Changed the database name of publisher and it worked fine.

      2.       Changed the database name of subscriber and again it worked fine.

    Can anyone please help me out on this. It seems like a very weird issue. Why does keeping the same database name throws error?

    • Edited by A_R_A_J_E Friday, November 23, 2012 8:58 AM
    Friday, November 23, 2012 7:00 AM