Debugging MSDTC Issues

Recently we experienced a range of MSDTC errors on upgrading to Windows 2003,
running separate web and database servers. The DTC would run fine to
Windows 2000 servers and locally (to itself), but no between Win2003 servers.
The following items summarize the checks made to finally resolve our issues.

Check 1 - DTC Security Configuration

This is a mandatory check on both W2003 boxes if MSDTC service is intended to
be used.

In administrative tools, navigate down through Component Services ->
Computers, and right-click on My Computer to get properties. There should be an
MSDTC tab, with a "Security Configuration" button. Click on that, and make sure
network transactions are enabled.

Apply of all server involved in the DTC conversation. You need to restart the
MSDTC service.

Check 5 - Win 2003 only - COM+ Default Component Security

New COM+ containers created in COM 1.5 (Windows 2003) will have the
"enforce access checks for this application" enabled.

Uncheck this option is you are experiencing component access errors, or
cannot instantiate object errors on previously running DLL's. Upgraded
operation systems and their containers will not have this option checked.

Join the most active online SQL Server Community

SQL knowledge, delivered daily, free:

Email address:

You make SSC a better place

As a member of SQLServerCentral, you get free access to loads of fresh content: thousands
of articles and SQL scripts, a library of free eBooks, a weekly database news roundup,
a great Q & A platform… And it’s our huge, buzzing community of SQL Server Professionals
that makes it such a success.