chpicker
Programmer
- Apr 10, 2001
- 1,316
I'm trying to set up transactional replication with updatable subscriptions for the first time using SQL Server 2005. I've never done replication before, so I followed Microsoft's tutorial on how to set up replication. It works fine. What's NOT working is the updates back to the publisher.
The error I get always starts with "Unable to set the Publisher login for the updatable subscription. You may have to set this up directly on the Subscriber machine using sp_link_publication." The current error is: "The operation could not be performed because OLE DB provider "SQLNCLI" for linked server REPLLINK_SQL01..." was unable to begin a distributed transaction." This is followed by: OLE DB provider "SQLNCLI" for linked server "REPLLINK_SQL01..." returned message "No transaction is active.". (Microsoft SQL Server, Error: 7391)
This is the latest in a LONG string of error messages that SQL Server has thrown at me when attempting to subscribe to my publication. On each of the previous ones, I did some research using Google searches and was able to find the solution, leading me to the next error message. It's like one of those games you used to play as a kid, each clue leading to yet another clue, the prize always ahead of you but out of reach. I've dealt with things like RPC not being enabled, no link back to the source server available, DTC not having access, etc.
I've hit a brick wall with this one, though. It's so unbelievably generic that Google searches just don't return anything relevant. I've been fighting with this thing for 4 days now.
Can someone give me step-by-step directions for creating a Transactional publication with updatable subscriptions, and then subscribing to it? I am so thoroughly frustrated with Microsoft right now it's ridiculous. The whole project is at a complete standstill until I can get the updates for this replication working.
I should probably emphasize that the replication works perfectly. I can make changes on the source server, open the table on the subscriber and see the changes. I just can't get updates from the subscriber to go back to the publisher.
Ian
The error I get always starts with "Unable to set the Publisher login for the updatable subscription. You may have to set this up directly on the Subscriber machine using sp_link_publication." The current error is: "The operation could not be performed because OLE DB provider "SQLNCLI" for linked server REPLLINK_SQL01..." was unable to begin a distributed transaction." This is followed by: OLE DB provider "SQLNCLI" for linked server "REPLLINK_SQL01..." returned message "No transaction is active.". (Microsoft SQL Server, Error: 7391)
This is the latest in a LONG string of error messages that SQL Server has thrown at me when attempting to subscribe to my publication. On each of the previous ones, I did some research using Google searches and was able to find the solution, leading me to the next error message. It's like one of those games you used to play as a kid, each clue leading to yet another clue, the prize always ahead of you but out of reach. I've dealt with things like RPC not being enabled, no link back to the source server available, DTC not having access, etc.
I've hit a brick wall with this one, though. It's so unbelievably generic that Google searches just don't return anything relevant. I've been fighting with this thing for 4 days now.
Can someone give me step-by-step directions for creating a Transactional publication with updatable subscriptions, and then subscribing to it? I am so thoroughly frustrated with Microsoft right now it's ridiculous. The whole project is at a complete standstill until I can get the updates for this replication working.
I should probably emphasize that the replication works perfectly. I can make changes on the source server, open the table on the subscriber and see the changes. I just can't get updates from the subscriber to go back to the publisher.
Ian