OMG, MSDTC Ran Out of Memory!

Symptom

I opened Component Services and browsed to Computers and My Computer. When I right-click My Computer and click the MSDTC tab I run into an out of memory error message.

Resolution

This is because the registry on your server is pointing to a default DTC that no longer exists. To resolve this problem you need to update the registry with the GUID of the new DTC. To do this follow these steps:

  • Open Services.msc and locate your DTC
  • Notice that when you open the services properties you will see the GUID of your DTC in the Path to Executable field
    • Document or copy this GUID

DTC_Service

 

 

 

 

 

 

 

 

 

 

  • Now open regedit
  • Browse to HKLM\Cluster\ResourceTypes\Distributed Transaction Coordinator
    • Backup this key
  • Edit the Cluster Default Resource property and paste in the GUID you copied from the previous step

DTC_Registry

 

 

 

  • Now attempt to access the MSDTC tab and verify the out of memory error message disappears and that your DTC is now listed under Default DTC.

 

Set-Realm UCS Errors During Firmware Upgrade

 

exclamation_warningHelp! I’m in the middle of upgrading the firmware on my UCS fabric interconnects and after I upgraded the first fabric interconnect I received these set-realm errors in UCS Manager:

  • set-realm-peer-failed
  • set-realm-local-failed

If you googled around you probably found a handful of completely useless Cisco articles that suggested you Google more or call support 🙁

Good news! According to Cisco support these errors can be caused by having mismatched firmware on the fabric interconnects. To verify everything is still working properly simply login with both an LDAP account and a local account. If you can, you are safe to proceed!