The process could not connect to Distributor.

Question

hi friends

i am creating the Merge Replication between two server(both SQLServer-2005, on XP).

Server names are as

1. HB5B

2. VSNET1

i)    On server HB5B, i had created the Publication with name 'hb_pub'.

(publisher & Distributer on HB5B server)

ii)   On server VSNET1, i had created the Pull Subscription, for the publication name hb_pub( form the server HB5B), this starts fine.

iii)   When i went to Viwe Synchroniztion status, it says

      The process could not connect to Distributor 'HB5B'

 

iv)  i too check the Distributor properties, its seems fine for me.

v)  On server VSNET1, if creats the Push Subscription, for the publication name hb_pub( form the server HB5B), this starts fine.

vi)   When i went to Viwe Synchroniztion status, it says

     The server 'VSNET1' is not a Subscriber. (.Net SqlClient Data Provider)

vii)   if i try again the Start button on the Viwe Synchroniztion status, it says the job is already running (with job name), Change the database context to 'HBmyDB' ( this is my database name).

 

the check list i made is

i)  I had log on as service(SQL Server Agent (MSSQLSERVER) & SQL Server (MSSQLSERVER) ) as Administrator at server VSNET1(i mean it had the administrative right) & restarted them.

ii)  I do have the administrative rights on the both of the machines.

iii)   both Server have same 'sa' passwords.

please help me

any solution, hint or idea.

Regards

Thanks

Gurpreet S. Gill

 

 

 

 

 

Answer 1

are you setting up replication via the UI?  If so, and if you specified alternate proxy accounts to start the agents, make sure those accounts have access to the publisher/distributor machine.

Answer 2

No i am not using the UI, i am just setting up the Merge Replication in the SQL-Server 2005 itself.

i am still with same error...

help me

Regards,

Thnanks,

Gurpreet S. Gill

 

Answer 3

Hi all

Finally i am able to solve the problem, now my Merge Replication works very fine.

I would like to thank all who help me.

now i want to share that what i made

1) Create a Distributor & publisher one SERVER 1

2) Create the Subscriber on the SERVER 2.

point to note

i) i am on XP(with SP2) & SQL-Server 2005

ii) Default Snapshort Folder path at SERVER 1 must be in UNC (this is where i was making mistake)

iii) at theSERVER 2, the Subscription Properties page

       Security Setting as as follows(number 6 in list)

       a) Agent process accont

             Account name : SERVER2\Administrator

             Password :*********

       b) Distributor Connection  : SQL Server Authentication(sa)

       c) Publisher Connection :  SQL Server Authentication(sa)

iv)  Both Machines having same user name & password for the SQL Server as well as the Machine login(Administrator)

 

if somebody still have any problem, then do post in this as a reply

Thanks

Regards

Gurpreet S. Gill

 

 

 

Answer 4

Hi Gurpreet,

How are you?

i need some help on  the "Merge Replication". Following code im using to replicate from SQL Server 2005 to SQL Express with OS - XP SP2

private void SynchronizeSubscription()

{

MergeSynchronizationAgent myAgent = new MergeSynchronizationAgent(); // declaring the synchrinization variable

try

{

// connection to the subscriber

subconn = new ServerConnection(subscriber);

subconn.Connect();

}

catch (Microsoft.SqlServer.Replication.ConnectionFailureException ex)

{

string str = ex.Message;

}

mergpull = new MergePullSubscription();

// Connection Info & Databases

mergpull.ConnectionContext = subconn;

mergpull.PublicationName = publication;

mergpull.PublicationDBName = PublisherDatabase;

mergpull.PublisherName = publisher;

mergpull.DatabaseName = SubScriberDatabase;

mergpull.PublisherSecurity.SecurityMode = ReplicationSecurityMode.SqlStandard;

// Distributor Security

mergpull.DistributorName = @"YH315\SQLORA";

//mergpull.DistributorSecurity.SqlStandardLogin = "sa";

//mergpull.DistributorSecurity.SqlStandardPassword = "pwd!123";

//Publisher Security

mergpull.PublisherSecurity.SqlStandardLogin = "sa";

mergpull.PublisherSecurity.SqlStandardPassword = "pwd!123";

//load properties of existing subscription

if (!mergpull.LoadProperties())

{

//raise exception

}

//get merge agent for synchronization execution

myAgent = mergpull.SynchronizationAgent;

//specify upload / download

//myAgent.ExchangeType = MergeExchangeType.Download;

myAgent.SubscriberSecurityMode = SecurityMode.Integrated;

//Generate a Troubleshoot log file

myAgent.Output = outputlogfile;

myAgent.OutputVerboseLevel = outputverboslevel;

//Define the event handler

myAgent.Status += new AgentCore.StatusEventHandler(myAgent_Status);

//Start the merg Agent Job

try

{

myAgent.Synchronize();

}

catch (Exception ex)

{

string msg = ex.Message;

}

}

when i call this method it gives me error - [Microsoft.SqlServer.Replication.ComErrorException] = {"The process could not connect to Distributor 'YH315\\SQLORA'."}

i tried the point u highlighted but its giving me the same error.

So please do suggest me to overcome this problem.

 

Regards,

Naveen Kumar M
[e-mail]

Answer 5

hi

I dont know how to do it, using C#

first check that are you able to ping the destination server

but seems like set the line as

mergpull.DistributorName = @"\\YH315\SQLORA";

this might help

Regards,

Thanks.

Gurpreet S. Gill

 

 

Answer 6

The error is this:

when i call this method it gives me error - [Microsoft.SqlServer.Replication.ComErrorException] = {"The process could not connect to Distributor 'YH315\\SQLORA'."}

Is this the proper instance of your distributor machine?  WHy is there two slashes between instance name and machine name?  Not sure if this makes a difference or not.

Also, I notice DIstributorSecurity is not set, and I don't know if it automatically defaults to integrated or sql security , can you try specifying this property with appropriate values?

 

Answer 7

Greg Y

The single slash is an escape character in C# hence you need to use \\ to let it know you intend to use the \.

Answer 8

Enable these 2 lines:

//mergpull.DistributorSecurity.SqlStandardLogin = "sa";

//mergpull.DistributorSecurity.SqlStandardPassword = "pwd!123";

Hopefully the password is correct and it shold work.

By default the authentication method is SQL and you are not providing the login and password.

Tye the above and post back if you still have issues.

Answer 9

Hi Gill,

I'm implementing merger replication via UI and have the same problem as yours:

"The process could not connect to Distributor SERVER1"

(I'm using Win XP and SQL2005)

I didn't get "ii) Default Snapshort Folder path at SERVER 1 must be in UNC (this is where i was making mistake)"

Could I know what you mean by UNC?

Besides, my SQL server user name & passwords are not the same for both machines. Is there any way to change one of them?

Would you do me a favor and guide me? this is and urgent job I have to perform.

 

Thanks in Advance

 

Answer 10

 

Hi,

 

I am also facing the same problem i had my distributor and publisher on the same system and a subcriber on the other system later on due to some reason i had to perform vise versa of this but now when i try to run merge agent on the subscriber it say server 'A' is not a subcriber even thgouth i disabled the publisher and distributor on the Server A.

 

Please help me solve this problem.

Thanks in advance.

Answer 11

Hi,

I have the same problem. Could u get this resoved?

Thank you.
Reza

Answer 12

Hi,

I have two instances of SQL server 20005 on my win 2003 R2 machine.
I have setup one instance as publisher and distributer, and the second one as a subscriber.
I setup a transactional publication, and followed your instructions.
Now, the table doesn't get replicated from publisher to the subscriber.
When, on subscriber I click on "view synchronization status" is shows "in-progress" but never passes that point.

Any idea?

Thank you.
Reza
[e-mail]

Answer 13

hi i am also having same error, the process couldn't connect to subscriber. i have created publisher and subscriber in same server.

Answer 14

no answer by anyone????

Answer 15

In case anyone finds this thread, my solution: If you're running distrib.exe from the command-line, I've had this error message ("could not connect to distributor") when the distrib.exe command-line specifies a database name for the subscription to go into that doesn't match the database name that you setup when you configured the subscription! i.e. double-check the -SubscriberDB option