ERROR_RESOURCEMANAGER_NOT_FOUND (0x1A3C) – Fix It Now
This error pops up when a program tries to use a resource manager (like a database or transaction log) that's been deleted or never existed. The fix is usually a registry clean or a service restart.
When This Error Hits
You're setting up a new SQL Server instance, or maybe you're migrating an old app to Windows Server 2019. Then bam — you get error code 0x00001A3C. The message says 'The specified resource manager object could not be opened because it was not found.' This usually happens right after a failed uninstall of a database cluster, or when someone manually deleted a transaction log file that a COM+ component still relies on.
Why It Happens
Windows uses something called the Kernel Transaction Manager (KTM) and the Microsoft Distributed Transaction Coordinator (MSDTC) to manage resources like databases, queues, and files. Think of a resource manager as a door to a specific database or log. The error means your program is holding a ticket (a reference) to a door that no longer exists. The culprit here is almost always a stale registry entry left behind by an uninstall or a failed update.
Don't bother checking event logs first — they rarely tell you which resource manager is missing. The real fix is to clean up orphaned references in the registry or restart the MSDTC service from scratch.
Fix It: Step-by-Step
- Back up the registry. Seriously. One wrong delete and you've broken a production server. Open regedit, right-click
Computer, and choose Export. Save the whole thing as a backup. - Navigate to the resource managers. Go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XAPrep - Check the orphaned entries. In the right pane, look for any GUID (long string like
{12345678-...}) that doesn't match a known resource. If you see entries from a program you already uninstalled, delete them. Be careful — only delete what you're certain is stale. - Restart the MSDTC service. Run CMD as admin, then:
net stop msdtc
net start msdtc - Reboot. Yeah, I know. But it flushes the KTM cache and makes sure everything starts clean.
If the Error Persists
Sometimes the registry isn't the problem. Check two things:
- COM+ components. Open Component Services (comexp.msc), expand Computers, My Computer, and COM+ Applications. Look for any application with a red X — it's pointing to a missing resource manager. Right-click and shut it down, then delete it.
- SQL Server specific. If this is SQL Server, check
sys.resource_governor_resource_pools. A misconfigured resource governor can cause this error. RunALTER RESOURCE GOVERNOR RECONFIGUREin SSMS.
If nothing works, run sfc /scannow and check for corrupt system files. I've also seen this happen after a Windows Update patch broke the KTM driver — in that case, uninstall the latest KB update.
Was this solution helpful?