Error code: 8004e00f - COM+ was unable to talk to the MSDTC.


SYMPTOMS

When opening the Component Services in the Microsoft Management Console (MMC), an error is produced like the one displayed below:

An error occurred while processing the last operation. Error code: 8004e00f - COM+ was unable to talk to the MSDTC. The event log may contain additional troubleshooting information.

The Application event log may contain:

   Event Type: Error
   Event Source: MSDTC Event
   Category: LOG
   Event ID: 4163
   Description: MS DTC log file not found.

   Event Type: Error
   Event Source: MSDTC Event
   Category: TM
   Event ID: 4185
   Description: MS DTC Transaction Manager start failed. LogInit returned error 0x2.

   Event Type: Error
   Event Source: MSDTC Event
   Category: SVC Event
   ID: 4112
   Description: Could not start the MS DTC Transaction Manager.

CAUSE

These errors are a result of a missing or damaged MS DTC (Microsoft Distributed Transaction Coordinator). Make sure that all Resource Manager that are coordinated by MS DTC have no "in-doubt" transactions.

RESOLUTION

To fix the problem:

1. Use Windows Explorer to expand the %SystemRoot%\System32\Dtclog folder.

2. If a Msdtc.log file exists, rename it to Msdtc.old.

3. Opens NOTEPAD and save an empty file as %SystemRoot%\System32\Dtclog\Msdtc.log.

4. Open a CMD prompt and type: msdtc -resetlog and press Enter.

MORE INFORMATION

ASP 0177 : Web mail or web administration fail with The server process could not be started because the configured identity is incorrect: http://www.mailenable.com/kb/content/article.asp?ID=ME020030

MailEnable Web Mail - MTS/COM+ Features error: http://www.mailenable.com/kb/content/article.asp?ID=ME020355

Error 'ASP 0177 : 800401f3' when accessing the MEMail COM component: http://www.mailenable.com/kb/content/article.asp?ID=ME020247



Product:MailEnable (Pro-Any Pro-1.X Ent-Any Ent-1.X)
Article:ME020370
Module:Other
Keywords:COM+,MS,DTC,Microsoft,Distributed,Transaction,coordinator,8004e00f,MSDTC
Class:ERR: Product Error
Revised:Wednesday, May 4, 2016
Author:
Publisher:MailEnable