Hello,
I am having a problem trying to run websync but can run replication over the lan. During the websync it errors out stating cannot connect to the distributor. The same login and password are used in both scenarios. Am I missing a setting
John
Hello,
I am having a problem trying to run websync but can run replication over the lan. During the websync it errors out stating cannot connect to the distributor. The same login and password are used in both scenarios. Am I missing a setting
John
Unable to replicate over websync but via the lan
Nexus_019
So are you saying that you are using this IIS server to get another Web Synchronization scenario working
Can you check the distributor Login and password once more please
Also can you post the complete error message here with your command line you used to run the synchronization
Dan.G
Mahesh,
Sorry I should have been more specific. I didn't configure the distributor for the live box until a month ago. That was the only difference, that I can remember, between the test install and the live upgrade. I was just curious on why one instance would require a distributor login via the code and the other would not, but it works over https so I am happy. Thanks for the help.
John
muku
Mahesh,
The distributor and publisher are on the same box. IIS is on a different box. We are using the sql login to connect to the distributor. The sql login is able to connect via query analyzer. We are using basic authentication over https. The same IIS box is used to connect to another SQL instance for testing purposes, so I believe that IIS is configured correctly.
Sajid Saeed
Mahesh,
It's a problem with our vb.net application. It seems that the test machine requires us to add these lines to the code with the live instance does not. Can you tell me if there are any pros/cons to not having this in the code for the live instance
agent.DistributorLogin =
"sqllogin"agent.PublisherLogin =
"sqllogin"agent.DistributorPassword =
"2Passwords"agent.PublisherPassword =
"2Passwords"agent.PublisherSecurityMode = SecurityMode.Standard
agent.DistributorSecurityMode = SecurityMode.Standard
BloomyMB
Since it is SQL Standard auth, I would assume it would not work with the live instance without these parameters, unless you are using windows auth to connect.
Make sure your auth is set correctly.
Another way to verify is to run the Merge agent through the sqlserver agent or even command line. That can make things more clearer.
No matter what some form of authentication is needed for the sync to work correctly.
So I would not be too worried if you had to add these to your code and if the sync works fine.
Ananda85
Are your Publisher, Distributor, IIS and Subscriber machines separate
Are you using Integrated authentication
If so, try with Basic authentication (for IIS) and SQL authentication for SQL connections.
Souhail
Yes, basic over HTTPS is the recommended way.
Maybe you should try this on a different set of machines to further narrow down the cause.
And what do you mean by installing the distributor later on the live.
Kelly Stich
Mahesh,
Thanks for the response. It's weird that one instance needs to have those lines of code and the other instance doesn't. I cannot find anything done differently between the machines with the exception of installing the distributor later on the live. Running basic auth over hhtps should be pretty secure in your opinion