Microsoft KB Archive/246679

= BUG: DTC Remote Coordinator Fails After DTC Is Configured for an Invalid Remote Host Name =

Article ID: 246679

Article Last Modified on 6/11/2002

-

APPLIES TO


 * Microsoft COM+ 1.0

-



This article was previously published under Q246679



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
Microsoft Distributed Transaction Coordinator (MS DTC) fails and the Component Services Explorer stops responding (hangs) when DTC is configured for a remote host name and later the remote system is renamed to an invalid name.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this problem, do one of the following:  Rename the remote system with the original name and restart both the local and remote systems. -or-

 Stop the MS DTC service, and follow these steps to reinstall it:  Stop All Services that will affect the MS DTC installation (SQL Server, Component Services, IISADMIN, Simple Mail Transfer Protocol (SMTP), (File Transfer Protocol) FTP, Protected Storage, and so on.) Run msdtc -uninstall from %WINDIR%\System32.  In the registry, remove the following keys (if they exist): HKEY_CLASSES_ROOT\CID HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC  Delete the DTC log file, %WINDIR%\System32\Dtclog\Msdtc.log.</li> Run Dtcsetup.exe from %WINDIR%\System32.</li> Manually install DTC, as follows:

msdtc -install

</li></ul> </li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

<div class="moreinformation_section">

Steps to reproduce the behavior:
<ol> Launch Component Services Explorer. On the Start menu, point to Programs, Administrative Tools, and then click Component Services.</li> Stop MS DTC services by right-clicking My Computer, and then clicking Stop MS DTC.</li> Right-click My Computer. Click the Properties - MSDTC tab.</li> Change the Default Coordinator setting from Use local coordinator to Remote Host. Select an available Remote Host system, for example, "hostA".</li> Go to the "hostA" system, and rename it "hostB". Then, restart the remote system.</li> Shut down Component Services on the local system and then re-open it.</li> Attempt to open the Computers folder. The following error message is generated:

Catalog Error: An error occurred while processing the last operation. Error code 80080005 -- server execution failed. The event log may contain additional troubleshooting information.

</li> You will find the following error logged in the Application log of Event viewer:

The run-time environment has detected an inconsistency in its internal state. Please contact Microsoft Product Services to report this error. Error in .\dtcinfo.cpp(106), hr = 8004d01b: Transaction Manager --> GetWhereabouts.

</li></ol>

Additional query words: dtc msdtc remote com+

Keywords: kbbug kbsysadmin kbdtc kbpending KB246679

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.