MSDTC Issue - COM+ Red Arrow, Delays in starting apps

kwgagel · 28 Aug 2018

My COM+ is not manageable because it cannot talk to MSDTC.

MSDTC Issue - COM+ Red Arrow, Delays in starting apps-image.png

Error is as below.

There is nothing in the event logs.

Many articles on this issue say the logon for the Distributed Transaction Coordinator is incorrect and to change it back to NT Authority/Network. But mine is that already. I tried changing it to local then back again to see if did anything. I didn't.

My Local DTC setup is.

I've followed many different articles on fixing this issue but none are exactly the same as mine (usually older version of windows or having the logon wrong). I'm stumped and can't seem to find anything to guide me to correct this on my machine.

This is Windows 10 ver 1803 with the latest patches.

Eagle51 · 28 Aug 2018

Hey kwgagel,
How about this - Error code: 8004e00f - COM+ was unable to talk to the MSDTC.

kwgagel · 29 Aug 2018

Eagle51 said:

Hey kwgagel,
How about this - Error code: 8004e00f - COM+ was unable to talk to the MSDTC.

No, that didn't work either.

kwgagel · 31 Aug 2018

Still trying to find solutions for this issue.

das10 · 31 Aug 2018

Do your firewall and antivirus programs report MSDTC as being blocked somehow, or whether all network protocols being used by MSDTC service are enabled ?

see the solution presented in this page for some ideas about it:

[SOLVED] Distributed Transaction Coordinator being blocked by Cisco 1841 router - Spiceworks

Onyx · 31 Aug 2018

I spent two days tracking this down as a software package my company develops relies on COM+
In the end it turns out to be a DOLBY service that blocks COM+ / MSDTC.
When disabled and rebooted the COM+ system works fine. Then starting the service it still works fine.

I set the service to delayed start and this has resolved the issue on a PC is was investigating (Lenovo Flex).
I had several such instances globally with Lenovo/HP/Dell. They all share the same Realtek driver that breaks this as soon as the first Windows Updates get installed. I traced this by doing a clean offline install and then searching for the driver that breaks it.

The service is DOLBYDAXAPI. Try to set it to delayed start from the services menu and reboot.

kwgagel · 31 Aug 2018

das10 said:

Do your firewall and antivirus programs report MSDTC as being blocked somehow, or whether all network protocols being used by MSDTC service are enabled ?

see the solution presented in this page for some ideas about it:

[SOLVED] Distributed Transaction Coordinator being blocked by Cisco 1841 router - Spiceworks

There are no network transactions going on here. This is strickly a standalone installation where COM+ is not functioning.

kwgagel · 31 Aug 2018

Onyx said:

I spent two days tracking this down as a software package my company develops relies on COM+
In the end it turns out to be a DOLBY service that blocks COM+ / MSDTC.
When disabled and rebooted the COM+ system works fine. Then starting the service it still works fine.

I set the service to delayed start and this has resolved the issue on a PC is was investigating (Lenovo Flex).
I had several such instances globally with Lenovo/HP/Dell. They all share the same Realtek driver that breaks this as soon as the first Windows Updates get installed. I traced this by doing a clean offline install and then searching for the driver that breaks it.

The service is DOLBYDAXAPI. Try to set it to delayed start from the services menu and reboot.

There is no DOLBYDAXAPI service in Services or in the Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services registry.

Onyx · 01 Sep 2018

Also check for Realtek Audio Universal Service.

I reset the laptop to Lenovos included OS, applied a registry fix and it worked immediately. Sorry this isn't helping you but after 15 hours of searching that is what solved the issue for Error code 8004E00F - COM+ was unable to talk to the MDTC

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\DolbyDAXAPI]
"Start"=dword:00000002
"DelayedAutostart"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DolbyDAXAPI]
"Start"=dword:00000002
"DelayedAutostart"=dword:00000001

kwgagel · 01 Sep 2018

Onyx said:

Also check for Realtek Audio Universal Service.

I reset the laptop to Lenovos included OS, applied a registry fix and it worked immediately. Sorry this isn't helping you but after 15 hours of searching that is what solved the issue for Error code 8004E00F - COM+ was unable to talk to the MDTC

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\DolbyDAXAPI]
"Start"=dword:00000002
"DelayedAutostart"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DolbyDAXAPI]
"Start"=dword:00000002
"DelayedAutostart"=dword:00000001

As I mentioned, I don't have those entries. I added them anyway and restarted the computer. Still have the same issue. Red arrow with several messages in system event about DistributedCOM errors needing launch permissions. But I can't manage the launch permissions because COM+ cannot communicate with MSDTS (even with the firewall turned off it cannot).