DCOM 10009 error after renaming local computer name. (No network computers involved in this issue)

Question

The DCOM 10009 error generated references the previous name of the computer. Here is the scenario:
These aren't the real names of the computer). The computer was named
computerX-NEW and was renamed to computerX during deployment setup. The DCOM error states "DCOM was unable to communicate with the computer
computerX-NEW using any of the configured protocols." When I look at the error details, a PID is referenced which turns out to be the RPCSS process/service. I suspected a piece of software that was installed on the computer until I performed
a Clean Boot with all startup programs disabled and all non-Microsoft services disabled. The error still occured. Also the error is occuring about 5 or 6 times per minute. The only thing I can start doing at this point is disabling MS services at boot to find
the culprit, but I'd like a less brutal approach to correct the issue. Any suggestions?

Answer 1

Hi,
The following are possible causes of this error:
1. Name resolution errors are occurring.
2. All TCP ports on the server are being used.
3. TCP port collisions are occurring.
4. The network connections may not be configured properly.
To troubleshoot DCOM 10009 errors, use the following methods.
Method 1: Verify that name resolution is working correctly
The activation page for a COM+ proxy application contains a Remote Server Name (RSN) property. The RSN property can be an IP address, a Fully Qualified Domain Name (FQDN), or a NetBIOS name. To troubleshoot this issue, use the ping command to test connectivity
to the remote server by using the IP address, the FQDN, and the NetBIOS name.
Method 2: Verify TCP port usage
When a client makes DCOM calls to a COM+ server application, each connection may use a different TCP port. Therefore, all TCP ports on the server may be used. When this condition occurs, the server cannot accept additional connections.
Method 3: Verify basic network connectivity to troubleshoot TCP collision issues
Method 4: Check the network connections. Check the Registry under HKEY Local Machine/Software/Microsoft/RPC/DCOM Protocols for the list of RPC protocol sequences.
For further troubleshooting information, please also refer to the following Microsoft article:
Known post installation event errors in SBS 2008 (and how to resolve them)
http://blogs.technet.com/b/sbs/archive/2008/08/26/known-post-installation-event-errors-in-sbs-2008-and-how-to-resolve-them.aspx
Hope it helps.
Regards,
Blair Deng
Blair Deng
TechNet Community Support