merge Replication Error

FAQ

Profile

merge Replication Error

Database Forums (Home) -> Replication

Next: Struggling granting SYSADM on AIX

Author

Message

moh hams

External

Since: Mar 16, 2011
Posts: 1

(Msg. 1) Posted: Wed Mar 16, 2011 4:25 pm Post subject: merge Replication Error Archived from groups: microsoft>public>sqlserver>replication (more info?)

Hi, i configure the merge replication (sql server 2000) and snapshot agent worked correctly and merge agent start to apply script to the subscribe and then make bulk copy for the data to subscrip correctly, then come the Error xp_execresultset: unable to get a bound connection back to server publish & distributor on the same server: windows server 2008 sp2 (use domain) subscr : windows 7 (without domain) plz can any one help me.. Submitted via EggHeadCafe Obsessive Defragmentation Disorder (ODD) and You http://www.eggheadcafe.com/tutorials/aspnet/b5f241d0-4e5d-44f9-aad9-78...fdea4df >> Stay informed about: merge Replication Error

Display posts from previous:

Related Topics:

SQL2000 - Merge Replication - Timeout error - Hi NG We have merge replication running successfully between 2 SQL2000 boxes via VPN. The agent profile is "Slow Link". On Tuesday, the replication stopped working. Verbose logging indicated a timeout issue. I created a new profile with...

Merge Replication - We have Server A, which is running Merge replication and acting as Publisher and Distributor. We have new server C which we needs to move our replication from A to this. Server B is the only subscriber Right now we have established the logshippin...

problem with merge replication - Hi, I ran an update query on the publisher. When I start the merge agent manually, I got the following error after a while. The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout....

Merge Replication - SP - I have created Merge Replication and it worked perfactly fine. All the tables and replicating fine. I have created new stored procedure on Publisher but it's not replicated into Subscriber. Can anyone tell me which command I have to used to make sure...

Merge Replication Deadlocks - On our servers that participate in the same merge replication various deadlocks happen. Below some examples. I’ve done some research but have not come up with a solution so far. What is the best way to prevent these deadlocks from happening? 1)..

	Database Forums (Home) -> Replication	All times are: Pacific Time (US & Canada)
Page 1 of 1

You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum