unable to begin a distributed transaction (Msg 7391)

[c-eric.geil]

I am receiving the following error when I run a stored procedure:
Server: Msg 7391, Level 16, State 1, Procedure spXXXX

The SP inserts data into a local (sql 2000) table from a remote sql
2000 database. The SP works fine until I add a trigger to the
destination. The contents of the trigger do not appear to matter, as I
have tried removing everything but one line, which is just a declare
statement. Updating the table with the trigger (even the full trigger)
in place does not cause an error. Running the SP without the trigger
on the table does not cause the error.

I have the exact same setup on another server. Both the SP and the
trigger are IDENTICAL. This setup works on one server, but not the
other. The only difference I can see is that the non-working server is
Windows 2000 Server, while the working server is Windows 2003 Server.

Any idea what's going on here?

Thanks in advance.
Eric

[c-eric.geil]

After a little more testing, here's some more info on this:

Server A (non-working Win2K server) pulls from Server B (remote sql
2000 server)
Server C (working Win2003 server) pulls from Server D (remote sql 2000
server)

When I switch server C to pull from server B, I get the 7391 error.
Both B and D are sql 2000. I am unsure of the OS on B and D at this
point. I do know that the databases are identical, as they are set up
as part of a vendor software we use, and are the exact same version of
the software.

[c-eric.geil]

Server B and Server D are both windows 2003 server. I checked and the
Distributed Transaction Coordinator service is running on both.

[Erland Sommarskog]

(c-*********@mci.com) writes:

After a little more testing, here's some more info on this:

Server A (non-working Win2K server) pulls from Server B (remote sql
2000 server)
Server C (working Win2003 server) pulls from Server D (remote sql 2000
server)

When I switch server C to pull from server B, I get the 7391 error.
Both B and D are sql 2000. I am unsure of the OS on B and D at this
point. I do know that the databases are identical, as they are set up
as part of a vendor software we use, and are the exact same version of
the software.

Enter Component Services (under Adminstratve Tools in the Control Panel),
and under the Component Services node, right-click My Computer and select
Properties. Go to the MS DTC tab. I don't really know what you should
look for, but compare the working server with the non-working.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx