DCOM Error 10010 in the Event logs and SLUGGISH server performance
We have come across this specific issue on Windows 2003 (post service pack 1) and Windows XP (post service pack 2) where the machine experiences slow performance and we observe many DCOM 10010 ERRORS in the event logs. If you are running in to this issue, you may see some of the symptoms/errors listed below.
- Doing anything takes forever. You click Start button and it responds to you after a minute (or may be more than that). Switching windows in the Taskbar takes very long.
- If you have IIS installed on the server, the IIS related services may not start or may hang while starting. Typically these errors appear when you try to start them.
- Trying to start the IISADMIN service throws an error - Windows Could not start the IIS Admin Service on Local Computer. For more information, review the system Event log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code –2147221164(0x80040154) or The IIS Admin Service service terminated with service-specific error 2147746132 (0x80040154).
- If IISADMIN service is started, trying to start the World Wide Web Publishing Service hangs and the service goes into the Starting state and after some time it may throw the error - The World Wide Web Publishing Service service terminated with service-specific error 2148007941 (0x80080005)
- While expanding COM+ Applications inside component services, you may get the below error
- An error occurred while processing the last operation
- Error code 8000FFF - Catastrophic failure
- You observe many DCOM Errors 10010 in the event viewer (like this)
- The server {BA126AD1-2166-11D1-B1D0-00805FC1270E} did not register with DCOM within the required timeout
- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout
Read the full post here https://blogs.msdn.microsoft.com/puneetgupta/2009/01/21/dcom-error-10010-in-the-event-logs-and-sluggish-server-performance/