August 3, 2007 at 3:14 pm
Hi - hoping some folks here can help me. I've got a SQL 2000, Service Pack 4 database that I need to publish, but I'm getting the following error on the exec sp_addpublication statement when I try to set up publication in Management Studio:
Msg 8526, Level 16, State 2, Procedure sp_addpublication, Line 802
Cannot go remote while the session is enlisted in a distributed transaction that has an active savepoint.
I also tried to set up the Publisher in Enterprise Studio, on the theory that the system sproc was not backwards compatible, and there I got this error:
Error 627: Cannot use SAVE TRANSACTION within a distributed transaction
There is one proc in the publisher's database that uses SAVE TRANSACTION, but it isn't currently being run and it isn't dependent on the table being published. Has anybody else encountered this? Any ideas about how to make this go away?
August 7, 2007 at 5:41 am
Replication had a lot of changes from 2000 to 2005. We have, however, been replicating to and from 2000 and 2005 databases for nearly a year without any issues relating to version compatibility.
However, I would recommend you use Enterprise Manager to set up your publisher if it is a SQL 2000 server. Once your publisher and distributor is set up (assuming a push subscription), use Management Studio to configure the subscription at the 2005 end.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply