BUG: DTC Remote Coordinator Fails After DTC Is Configured for an Invalid Remote Host Name (246679)
The information in this article applies to:
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.
RESOLUTIONWARNING: 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:
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 6/11/2002 |
---|
Keywords: | kbbug kbDSupport kbDTC kbSysAdmin KB246679 |
---|
|