8004E00F when double clicking on COM+ Applications in Component Services mmc

Bruce Sanderson

unread,

Feb 25, 2004, 1:40:52 PM2/25/04

to

Windows 2003 Enterprise Server

When I open Component Services, "My Computer" is shown with a downward
pointing red arrow. If I double click on "COM+ Applications", I get this
error message.

---------------------------
Catalog Error
---------------------------
An error occurred while processing the last operation.
Error code 8004E00F - COM+ was unable to talk to the Microsoft Distributed
Transaction Coordinator
The event log may contain additional troubleshooting information.

DTC is started and is configured to run under the local SYSTEM account. If
DTC is restarted, I get this Application Event Log entry:

Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4437
Date: 25/Feb/2004
Time: 9:47:17 AM
User: N/A
Computer: BCAS6
Description:

The account that the MS DTC service is running under is invalid. This can
happen if the service account information has been changed using the
Services snap-in in Microsoft Management Console (MMC). MS DTC service will
continue to start. Please make sure that the MS DTC service account
information is updated using the Component Services Explorer.

What is causing this problem and what do I need to do to fix it?

--
Bruce Sanderson MVP

It's perfectly useless to know the right answer to the wrong question.

Yan-Hong Huang[MSFT]

unread,

Feb 25, 2004, 8:37:13 PM2/25/04

to

Hi Bruce,

Thanks for posting in the group.

Based on the problem description, now the issue is: When you open Component
Services, "My Computer" is shown with a downward pointing red arrow. In
Services, DTC is running under local system account and you got "Error code

8004E00F - COM+ was unable to talk to the Microsoft Distributed Transaction

Coordinator" error message when opening "com+ applications". Is it right?

This is caused by MSDTC (Distributed transaction coordinator) Service being
set run under the local system account. It should run under NT
Authority\NetworkService account instead.

To resolve this issue.
==================
- Run regedt32 and locate HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC.
-Add a DWORD value TurnOffRpcSecurity with a value data of 1.
- Open services and locate Distributed Transaction Coordinator Stop
this service
- Click on the Log On tab.
- Change the Log on account back to NT Authority\NetworkService
- Just type NT Authority\NetworkService
- the Password is blank.
- Click Apply and Ok
- Start Distributed Transaction Coordinator service

(After verifying that everything is now working correctly delete the
TurnOffRpcSecurity value from the registry.)

Hope that helps. If the problem is not resolved, please feel free to post
here.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Bruce Sanderson

unread,

Feb 26, 2004, 4:07:20 PM2/26/04

to

Thanks for the info. Changing the DTC account as you suggested corrected
the problem.

Now, if you have any suggestions about the other problem I'm having with
COM+ (see the thread "error 80110031 exporting Proxy from Component
Services...") on a different Windows 2003 Enterprise Server, that would be
very useful.

Thanks again for responding so quickly.

--
Bruce Sanderson MVP

It's perfectly useless to know the right answer to the wrong question.

"Yan-Hong Huang[MSFT]" <yhh...@online.microsoft.com> wrote in message
news:MDA9ujA$DHA...@cpmsftngxa06.phx.gbl...

Yan-Hong Huang[MSFT]

unread,

Feb 26, 2004, 9:49:46 PM2/26/04

to

Hi Bruce,

You are welcome. I am glad to hear that the first problem has been resolved.

For the second problem, error number 80110031, I have no clear idea on it
yet. In order to troubleshoot it, we may need to collect COM+ event log or
dump file, which is not easy to do in the newsgroup.

However, I am still happy to share my idea on it with you.

Does the problem happen with the very beginning or just after some time?
From your description, it seems that the problem didn't exist before.
Generally speaking, renaming a machine name won't cause it. Did you install
some special software on that machine? We did get report that some third
party component may cause it. Please double check this machine first.

By the way, if you create a simple COM+ applicaiton on that machine, did
this problem happen also? This is to make sure this issue only happens to
one component, or all components on the machine.

Thanks very much.

Bruce Sanderson

unread,

Feb 27, 2004, 3:48:13 PM2/27/04

to

Well, I'm happy to report that this problem has mysteriously vanished!

It happened yesterday, but is not happening today. We can happily export
any COM+ application we want (we only have three!).

The only action taken related to this is that a simple dll was added to a
new application, exported, then the application was deleted. Nothing was
done to the OS or any of the other applications. Well, at least, no one
associated with this server is admitting to doing anything that would
correct the problem!

Chalk up another one to the software gods!

--
Bruce Sanderson MVP

It's perfectly useless to know the right answer to the wrong question.

"Bruce Sanderson" <Bruce.S...@junk.junk> wrote in message
news:OaR8GyK$DHA....@TK2MSFTNGP12.phx.gbl...

Yan-Hong Huang[MSFT]

unread,

Feb 29, 2004, 8:31:23 PM2/29/04

to

Hi Bruce,

This is strange. Anyway, I am glad to hear the problem is gone. If you met
such problems again, please feel free to post here and we are here to
support you at your convenience.

Thanks.

veekay

unread,

Jan 10, 2011, 8:09:28 AM1/10/11

to

yhhuang wrote on 02/25/2004 20:37 ET :
> Hi Bruce,
>
> Thanks for posting in the group.
>
> Based on the problem description, now the issue is: When you open Component

> Services, "My Computer" is shown with a downward pointing red
arrow.
> In
> Services, DTC is running under local system account and you got "Error

> code
> 8004E00F - COM+ was unable to talk to the Microsoft Distributed Transaction

> Coordinator" error message when opening "com+ applications".

Is
> it right?
>
> This is caused by MSDTC (Distributed transaction coordinator) Service being
> set run under the local system account. It should run under NT

> AuthorityNetworkService account instead.
>
> To resolve this issue.
> == - Run regedt32 and locate HKEY_LOCAL_MACHINESoftwareMicrosoftMSDTC.

> -Add a DWORD value TurnOffRpcSecurity with a value data of 1.
> - Open services and locate Distributed Transaction Coordinator Stop
> this service
> - Click on the Log On tab.

> - Change the Log on account back to NT AuthorityNetworkService
> - Just type NT AuthorityNetworkService

> - the Password is blank.
> - Click Apply and Ok
> - Start Distributed Transaction Coordinator service
>
> (After verifying that everything is now working correctly delete the
> TurnOffRpcSecurity value from the registry.)
>
> Hope that helps. If the problem is not resolved, please feel free to post
> here.
>
> Best regards,
> Yanhong Huang
> Microsoft Community Support
>

> Get Secure! ¨C www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
Hi Yhhuang,

I followed all the steps you have mentioned but still i am getting the same
error.
I am using win 2008 R2 x64.

Thanks,
-Veekay

gautam...@gmail.com

unread,

Jan 19, 2015, 5:39:17 AM1/19/15

to

Hi Yanhong,

I am facing the same issue as mentioned by Bruce. I have followed the steps mentioned by you, but the issue is not solved. Can you please suggest what else can be looked into.

Regards,
Gautam Ramini

charlie...@sito.com.ve

unread,

May 15, 2015, 10:45:49 AM5/15/15

to

hello I have the same problem, I followed all the steps and still have the problem.

kuyoge...@gmail.com

unread,

Jun 19, 2019, 7:52:16 AM6/19/19

to

Hi Sir,

I am unable to fix error after apply your suggested process.kindly help to fix error 8004E00F.

Regards
Yogendra Kumar