| Event Id | 4395 |
| Source | MSDTC |
| Description | "MSDTC detected that MSDTC related information in the local registry is different from that in the shared cluster registry. Error Specifics: d:\nt\com\com1x\dtc\shared\mtxclu\mtxclusetuphelper.cpp:541, CmdLine: C:\WINNT\System32\msdtc.exe, Pid: 796 " |
| Event Information | According to Microsoft: CAUSE : This behavior occurs if the following conditions are true: • You installed the MSDTC service as a non-clustered resource on a Windows 2000 Server-based cluster. • You installed the MS04-012 software update. Note: The MS04-012 software update is included in the Windows 2000 post Service Pack 4 COM+ hotfix rollup package 27. The MS04-012 software update includes a change to the MSDTC proxy (Msdtcprx.dll). The software update reveals the requirement to have the MSDTC service configured as a clustered resource. After you first install the update, the MSDTC service can start on the local cluster because the service is initialized before the Cluster service starts. However, if you stop the MSDTC service after the Cluster service is running, you cannot restart MSDTC until you restart the server. Note: If you install MSDTC as a non-clustered resource, this configuration could lead to orphaned transactions. Orphaned transactions can cause data corruption if a cluster failover occurs. We do not recommend or support this configuration. By default, Microsoft Windows Server 2003 requires MSDTC to be installed as a clustered resource. Resolution: For Resolution click the Article Q867520 . |
| Reference Links | Q867520:Resolution for Event id 4384 You may receive error messages when you start MSDTC on a node of a cluster server |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.