RMO MergePullSubscription.SynchronizationAgent cannot connect to PublisherFailoverPartner

• paulvanleemput

  SSC Enthusiast

  Points: 182

  More actions

  August 8, 2014 at 7:23 am

  #289688

  for test purposes we used the example program from Brandon Williams on this url: http://code.msdn.microsoft.com/SQL-Server-Express-Merge-4e01e119

  with as parameters for our testlab servers:

  [font="Courier New"] // Define the server, subscription, publication, and database names.

  string subscriberName = "MORSWV447";

  string subscriptionDbName = "TicketOrdersSub";

  string publisherName = "MORSWV558";

  string publisherFailoverPartnerName = "MORSWV559";

  string publicationName = "TicketOrders";

  string publicationDbName = "TicketOrdersPub";

  //string distributorName = "MORSWV560";

  [/font]

  to evaluate DRP scenarios we added the parameter agent.PublisherFailoverPartner = (Mirror server name)

  If we do the failover while the program is running (but not replicating) it is working. 🙂

  [font="Courier New"]Initializing

  Connecting to Publisher 'MORSWV558'

  Connecting to mirrored instance of Publisher 'MORSWV559'

  Retrieving publication information

  Retrieving subscription information.

  Uploading data changes to the Publisher

  No data needed to be merged.

  Downloading data changes to the Subscriber

  No data needed to be merged.

  Merge completed with no data changes processed.

  Done![/font]

  If we close and restart the program it can't find the failoverpartner anymore. :ermm:

  [font="Courier New"]Initializing

  Connecting to Publisher 'MORSWV558'

  The merge process could not connect to the Publisher 'MORSWV558:TicketOrdersPub'. Check to ensure that the server is running.

  The merge process could not connect to the Publisher 'MORSWV558:TicketOrdersPub'. Check to ensure that the server is running.

  The process could not access database 'TicketOrdersPub' on server 'MORSWV558'.

  Cannot open database "TicketOrdersPub" requested by the login. The login failed.

  Login failed for user 'xxx'.

  Error: The subscription could not be synchronized. Verify that the subscription has been defined correctly.

  [/font]InnerException = {"The merge process could not connect to the Publisher '(Primary Principal):(PublicationDBName)'. Check to ensure that the server is running."}

  What did we do wrong here? or is this a bug in the RMO MergePullSubscription.SynchronizationAgent?

  We used for all server Microsoft SQL Server standard Edition 2008 R2 SP2 CU3 on Windows Server 2008 R2 Sp2 - 64 Bit.

  By using the cmd line executable replmerge.exe we can use this parameter as expected.

  thanks in advance for sorting this out.

  Paul