SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


RMO MergePullSubscription.SynchronizationAgent cannot connect to PublisherFailoverPartner


RMO MergePullSubscription.SynchronizationAgent cannot connect to PublisherFailoverPartner

Author
Message
paulvanleemput
paulvanleemput
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
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. Ermm

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)SadPublicationDBName)'. 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



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search