No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


DCOM 10009 errors in event viewer

Publication Date:  2013-07-29 Views:  121 Downloads:  0
Issue Description
We may see below DCOM 10009 errors in our system event, or we may receive the exception code 0x800706ba in our DCOM client application:

Event Type:        Error
Event Source:    DCOM
Event Category:   None
Event ID:              10009

Alarm Information
DCOM was unable to communicate with the computer <Target Computer Name> using any of the configured protocols.

DCOM 10009 indicates that the DCOM client located on this <Computer Name> can’t communicate with the DCOM|COM+ server located on that <Target Computer  Name>.

Handling Process
For scenario 1:
If DCOM 10009 is logged during the period of maintenance of   remote target server, it’s an expected behaviour because the remote target server is offline. We can verify it by ping <remote server>

For Scenario 2:
If the remote target server is online while DCOM 10009 is still logged, then we can perform below tests:
1)      Ping <remote server> & IP Address of remote server to make sure network traffic is fine.

2)      Telnet <remote server> 135 to make sure the Port 135 is not blocked by firewall.

3)      If we have configured dynamic port for RPC communication, we can check what status the port resources are  on both servers using  below command:   netstat –anb   if all dynamic ports are used , or only few left, you can consider expanding the dynamic port.

4)      If all above tests are fine, we can use DTCPing tool to verify if the DCOM communication   between two servers is fine.

For scenario 3:
Need capture more resources like Network traffic, or even iDNA trace to further investigate how this failure happens.

For scenario 4:
Grant the specific account mentioned in DCOM event 10027 with corresponding permission through “Component Services MMC”

Root Cause
 The reason why DCOM 10009 is logged is that: local RPCSS service can’t reach the remote RPCSS service of remote target server.
There are many possibilities which can cause this issue.
Scenario 1:
The remote target server happens to be offline for a short time, for example, just for maintenance.
•Scenario 2:
Both servers are online. However, there RPC communication issue exists between these two servers, for example:  server name resolvation failure, port resources for RPC communication exhaustion, firewall configuration.
Scenario 3:
Even though the TCP connection to remote server has no any problem, but if the communication of RPC authentication gets problem, we may get the error status code like 0x80070721 which means “A security package specific error occurred” during the communication of RPC authentication, DCOM 10009 will also be logged on the client side.
•Scenario 4:
The target DCOM |COM+ service failed to be activated due to permission issue. Under this kind of situation, DCOM 10027 will be logged on the server side at the same time
You cannot obtain detailed error information about DCOM 10009 errors in Windows Server 2003