Event ID 10009 DCOM

26,294

I did a bit of research and found an interesting technet blog article from MS about the ID 10009 DCOM Troubleshooting. It does give the reason of the DCOM attempts, but explains you what is triggering the DCOM call and gives tips on getting rid of it.

In the same article (comments section from the blog team), it's suggested to run tools like Network Monitor and Process Monitor, look at which process keeps sending failured RPC requests to identify which application is culprit in your scenario.

Hope it helps

sources : http://blogs.msdn.com/b/asiatech/archive/2010/03/16/how-to-troubleshoot-dcom-10009-error-logged-in-system-event.aspx

Share:
26,294

Related videos on Youtube

josh
Author by

josh

Updated on September 18, 2022

Comments

  • josh
    josh almost 2 years

    We have a Server 2008 R2 DC that is generating Event ID 10009 - "DCOM was unable to communicate with the computer X using any of the configured protocol." I found this question: Event ID 10009 on Server 2008 R2 DCOM was unable to communicate with computer X. The only difference for me is that I know what the "computers" are. They are all our networking gear: switches, routers, firewall, WAPs etc.

    Why would our DC being trying to contact network equipment via DCOM? And is there any way to stop it? It's really annoying seeing thousands of errors a day in the event log.