Event Id | 4440 |
Source | Microsoft-Windows-MSDTC |
Description | The MS DTC Service is terminating because it didnt startup in a timely manner. This may be because MS DTC took too long to recover its log file. Try increasing the startup timeout by specifying a larger "MaxRecoveryTimePerMbInMinutes" DWORD value under the HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC registry key. The default for this value is 3 (minutes). Debugging context follows: %1 %0 |
Event Information | According to Microsoft : Diagnose : Check the system for a low-memory condition. If a low-memory condition exists, close applications to free system memory. There may be missing files. Check to ensure that Comres.dll is present by following the steps in "Confirm that Comres.dll is present in the System32 folder." When you have resolved a low-memory condition and ensured that Comres.dll exists, restart MSDTC by following the steps in "Restart MSDTC." Resolution : Check the XA provider registry key An error condition may have resulted from a problem with the registry key for an X/Open Distributed Transaction Processing Standard (XA) provider. Check that the registry key is appropriate for your XA provider, and then restart the Microsoft Distributed Transaction Coordinator service (MSDTC). To perform these procedures, you must have membership in Administrators , or you must have been delegated the appropriate authority. To check that the registry key is appropriate for your XA provider: Caution : Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
The system could not load the Comres.dll file. An error condition may result if a required file is missing from the System32 folder in the Windows directory or if the file is corrupted. To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority. To confirm that the required file Comres.dll is present in the System32 folder:
The system reports that the Microsoft Distributed Transaction Coordinator service (MSDTC) encountered an invalid Class ID for the Transaction Bridge component. At this time there is no troubleshooting information for this issue. We recommend that you restart the service. If this does not resolve the issue and you continue to get this error, note any details in the event message. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To restart MSDTC:
You can alternatively stop and restart the Microsoft Distributed Transaction Coordinator service (MSDTC) using the steps listed below:
Close some applications to free up the memory. When you have closed applications to free up some additional memory, restart the Microsoft Distributed Transaction Coordinator service (MSDTC). To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority. To restart MSDTC:
To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority. To verify that the Microsoft Distributed Transaction Coordinator service (MSDTC) is running:
|
Reference Links | Event ID 4440 from Source Microsoft-Windows-MSDTC |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.