COM+ Unable to talk to Microsoft Distributed Transaction coordinator

[JOJUJACOBJOY]

An error had occured while processing the last operation. Error code 8004E00F  COM+ Unable to talk to Microsoft Distributed Transaction coordinator

[CherylG]

When are you getting the Error message?

The post here may be applicable:

https://answers.microsoft.com/en-us/windows/forum/windows_8-performance/8004e00f-com-unable-to-talk-...

[JOJUJACOBJOY]

Thank you Cheryl 

I had changed the registry settings of  TurnOffRpcSecurity earlier but this didnt work either.Also the MSDTC is running with the network account

I am a Microsoft developer my self here are the sequence of things which i did  which might help.

1. Tried fixing the isuue with the regedit TurnOffRpcSecurity I mentioned earlier also cheking the MSDTC account which it is running under.

2. Did the OS restore both by windows repair and HP recovery method from the boot - After the fresh OS install I still saw the error. Both the OS Install was done as fresh install opting out to keep the old files - My Laptop is relatively new.

3. Then I bought a new Windows pro edition and upgraded this- To justify my 220£ craziness ,Initially I ran into the reported issue when Installing Microsoft BizTalk Server, and MSDTC is one of the prime requirement for this. Single Sign on is one of the features for windows pro and I thought upgrade would fix the component services. However it didnt,and I have the same issue with the upgraded pro version.

4.Reading bytes and bytes of blogs and forums ,I saw many users reporting same issue particularly when the system drivers don't match . After this it hit me the OS has nothing to do with the problem in Hand , it might be the drivers and services installed after that.

5. This revelation started my long hunt . I started of by disabling the serices one after the other to check what is crashing the component services. And shockinly when i disabled hp services the component services work fine.

Please find the Screen shot for the services.

6. I was not able to nail down the exact service which is causing this . This might be a multiple services causing the issue. 

Still I did a study of some which was suspicious like HPNetworkCap and checked the path of the executable of this service which is "C:\WINDOWS\System32\DriverStore\FileRepository\hpcustomcapcomp.inf_amd64_44dd2c42f20b4640\x64\NetworkCap.exe"

7. Checking the drivers folder C:\Windows\System32\DriverStore\FileRepository\ .I see all the drivers/files within have amd64 inside the folders . I have an intel i7 8th gen Envy 13 ah0003na . 

Its not uncommon for OEM to use the drivers for different models, I suspect mine might hold amd drivers.

And the services might be running for AMD  drivers.Can you please check if this is the case.

I can confirm that disabling the above mentioned services is making the component services to work .

[CherylG]

AMD64 is the name sometimes given to 64 bit drivers since it was AMD that developed the first 64 bit specification for microprocessors.  Intel adapted that specification. Microsoft uses x86 for 32 bit and AMD64 or x64 for 64 bit.

Odd to find the HP services are what is causing it- but most are non-critical drivers/services anyway. I was on  Lenovo forum and saw a thread with the same problem -it was some proprietary Lenovo driver/service causing the same problem.

For more info on AMD64 check this Wikipedia article. If too much info just skip down to "Industry Naming Conventions" near the bottom:

https://en.wikipedia.org/wiki/X86-64