BUG: MSDTC Fails to Start if Different Drives/Paths Are Chosen

ID: Q150020

The information in this article applies to:

Microsoft SQL Server version 6.5

BUG#: 14794 (6.50)

SYMPTOMS

If you choose different drives or paths for the SQL Server binaries and data (for example, place binaries on C:\MSSQL and data on D:\MSSQL), the MSDTC is registered incorrectly. The log file is always put wherever the Master.Dat file is, but the MSDTC is registered saying it is in the DATA subdirectory beneath the binaries. (In the example above, the log would be in D:\MSSQL\DATA, but setup calls to register MSDTC saying it is in C:\MSSQL\DATA).

WORKAROUND

Use the Microsoft SQL Enterprise Manager (SEM) to reset the log. Right click the Servers, Distributed Transaction Coordinator icon and choose Configure, this will bring up the Configuration window. Choose an appropriate path and click the Reset Log button. The MSDTC service will now be able to start.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: sql65 msdtc


Keywords          : kbsetup kbtool SSrvDTC SSrvEntMan kbbug6.50 
Version           : 6.5
Platform          : WINDOWS 
Issue type        :

Last Reviewed: March 26, 1999