42 solutions found, page 1 of 3
0X80010109 RPC_E_RETRY means COM object asked caller to retry later. Usually caused by a busy or stale interface in Outlook, Excel, or Windows shell extensions....
0X80110605 This error strikes when your queued component app rejects an unauthenticated message. The fix is to align COM+ security settings with your app's authe...
0X8004D100 This error means the MSDTC transaction coordinator blocked your connection. It's usually a firewall or authentication issue. Here's the real fix....
0X8011041D This error happens when a COM+ component can't load a DLL—often after a failed update or corrupt registration. Here's how to fix it....
0X80010139 This error means your ACL has too many access control entries—usually from repeated COM app or registry edits. The fix: audit and prune excess ACEs....
0X000401E7 This COM error means a moniker is already registered in the Running Object Table. Here's how to clear it and prevent it from coming back....
0X80110450 Got this error when trying to create or configure a COM+ partition? It means you're already on the base partition—here's the real fix....
0X8004D008 This error means your app is asking for a transaction isolation level that DTC doesn't support. We'll show you the three most common causes and their ...
0X80004009 Class cache initialization fails due to a stuck COM+ catalog or corrupted cache files. Restarting the service or clearing the cache fixes it....
0X80010118 This COM+ error pops up when a server app tries to impersonate a client over an unsecure call. The fix is almost always a DCOM config tweak or a code ...
0X000006DE This RPC error usually means a DCOM object won't unexport cleanly. Most common cause: a leftover registry reference or a hung COM+ app....
0X000002E8 This error means a transaction already committed but something still references it. Here's how to stop it from wrecking your queries....
0X0000085D This error pops up when a client tries to run a transaction against a server that's not set up for it. Real fix: enable the transaction service or che...
0X80004014 This DCOM error means Windows can't resolve the server name for a remote activation. Usually a DNS or SPN issue....
0X8004D025 This error means the remote machine's MSDTC won't accept network transactions. You'll need to tweak DTC security settings or firewall rules....
0XC000020F SQL Server transaction aborts when DTC or network transport drops the connection mid-commit. Here's how to fix it without rebooting everything....
0X80110812 This error shows up when you try to recycle a COM+ application process that's already been recycled. Here's why and how to fix it....
0X8004E024 COM+ activation timed out. This fix clears the component services queue and restarts the DTC service. Works in 5 minutes....
0X8004D016 This error means a DTC transaction is stuck in an indeterminate state. It usually happens after a power loss or network timeout between SQL Server and...
0X80004025 COM+ app pool got paused by the system. We'll unpause it, then fix why it happened. Usually due to repeated crashes or DCOM config issues....