Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

RMO MergePullSubscription.SynchronizationAgent cannot connect to PublisherFailoverPartner Expand / Collapse
Author
Message
Posted Friday, August 8, 2014 7:23 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, August 18, 2014 1:28 PM
Points: 16, Visits: 40
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:
// 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";

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.

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!


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

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.

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




Post #1601162
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse