Error 10009 Unable To Communicate With The Computer
Contents |
platform and distributed applications How to troubleshoot DCOM 10009 error logged in system event? ★★★★★★★★★★★★★★★ APGC DSI TeamMarch error 10009 dcom was unable to communicate with the computer 15, 201021 0 0 0 Symptom: Sometimes, we may
Dcom Was Unable To Communicate With The Computer 10009 Server 2008
see below DCOM 10009 errors in our system event, or we may receive the exception code 10009 dcom was unable to communicate with the computer using any of the configured protocols 0x800706ba in our DCOM client application: Event Type: ErrorEvent Source: DCOM|Event Category: NoneEvent ID: 10009Date: 2010-2-22Time: 10:02:07User: N/AComputer:
Dcom Was Unable To Communicate With The Computer Using Any Of The Configured Protocols 10028
to activate a component, the COM runtime contacts its local SCM COM activator (RPCSS service) in order to launch the corresponding COM server that will host the desired component. If the component is remote, the local RPCSS service will forward the request to the RPCSS service of the remote machine. However, if the RPCSS service of remote target server is not available, DCOM 10009 will be logged locally to notify administrator. The typical call stack is as follows:ChildEBP RetAddr 006df364 757f8b72 ADVAPI32!ReportEventW-> then DCOM 10009 is logged. 006df3a0 757f6542 rpcss!LogRemoteSideUnavailable+0x63 ->here we don’t found the server. 006df40c 757f6781 rpcss!CRemoteMachine::Activate+0x294 006df648 757f6861 rpcss!RemoteActivationCall+0xf2 006df664 757edb5c rpcss!ActivateRemote+0x8e 006df6c0 757d629c rpcss!Activation+0x343 006df718 757d7680 rpcss!ActivateFromProperties+0x1c2 006df724 757d76c0 rpcss!CScmActivator::CreateInstance+0xd…… Why this happens: Totally speaking, 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
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs dcom was unable to communicate with the computer event id 10009 TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions dcom was unable to communicate with the computer domain.local using any of the configured protocols TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization
Dcom Was Unable To Communicate With The Computer Dns Forwarder
Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See https://blogs.msdn.microsoft.com/asiatech/2010/03/15/how-to-troubleshoot-dcom-10009-error-logged-in-system-event/ all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification https://technet.microsoft.com/en-us/library/cc774368(v=ws.10).aspx (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Application Server COM COM Remote Service Availability COM Remote Service Availability Event ID 10009 Event ID 10009 Event ID 10009 Event ID 10006 Event ID 10008 Event ID 10009 Event ID 10011 Event ID 18205 TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This document
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://serverfault.com/questions/531043/event-id-10009-dcom about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the unable to top Event ID 10009 DCOM up vote 3 down vote favorite 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 unable to communicate "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. windows-server-2008-r2 dcom share|improve this question asked Aug 14 '13 at 20:18 josh 28127 Do the error messages follow any sort of pattern? –Mitch May 4 '15 at 18:58 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote 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|improve this answer answered Aug 26 '13 at 6:59 Douda 765 add a comment| Your Answer draft saved draft discarded Sign up or log in S