Dcom Error 10009 Windows Xp
Contents |
platform and distributed applications How to troubleshoot DCOM 10009 error logged in system event? ★★★★★★★★★★★★★★★ APGC DSI TeamMarch 15, 201021 0 0 dcom 10009 windows server 2008 0 Symptom: Sometimes, we may see below DCOM 10009 errors
Dcom 10009 Windows Server 2008 R2
in our system event, or we may receive the exception code 0x800706ba in our DCOM client application: dcom error 10009 unable to communicate with computer Event Type: ErrorEvent Source: DCOM|Event Category: NoneEvent ID: 10009Date: 2010-2-22Time: 10:02:07User: N/AComputer:
Event Id 10009 Dcom Was Unable To Communicate With The Computer
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 target server happens to be offline for a short time, for example, just for maintenance. Scenario 2: Both servers are online. However, there RPC commu
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet dcom was unable to communicate with the computer using any of the configured protocols 10028 Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library dcom was unable to communicate with the computer domain.local using any of the configured protocols TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud
Dcom Was Unable To Communicate With The Computer 8.8.8.8 Using Any Of The Configured Protocols.
and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 https://blogs.msdn.microsoft.com/asiatech/2010/03/15/how-to-troubleshoot-dcom-10009-error-logged-in-system-event/ SP1 Windows 8.1 Enterprise See 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 https://technet.microsoft.com/en-us/library/cc774368(v=ws.10).aspx Certification overview MCSA: Windows 10 Windows Server Certification (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 conte
Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent https://community.spiceworks.com/windows_event/show/4-dcom-10009 ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 10009 (Error) Source: http://blogs.msmvps.com/bradley/2009/11/28/dcom-was-unable-to-communicate-with-the-computer/ DCOM How important is this event? (41 votes) 1 2 3 4 5 not important very important Description < < Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C unable to C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages DCOM was unable to communicate with the computer swbend531 using any of the configured protocols.
Jun 12, 2009 DCOM was unable to communicate with unable to communicate the computer tracy using any of the configured protocols. Jun 21, 2009 DCOM was unable to communicate with the computer 216.34.131.135 using any of the configured protocols. Jun 22, 2009 DCOM was unable to communicate with the computer 192.192.0.139 using any of the configured protocols. Jun 23, 2009 DCOM was unable to communicate with the computer 192.168.200.178 using any of the configured protocols. Jun 26, 2009 DCOM was unable to communicate with the computer 192.168.168.117 using any of the configured protocols. Jul 02, 2009 111 Feb 21, 2013 DCOM was unable to communicate with the computer 192.168.42.101 using any of the configured protocols. Jul 17, 2009 DCOM was unable to communicate with the computer 10.10.10.254 using any of the configured protocols. Jul 24, 2009 DCOM was unable to communicate with the computer tshepo-pc.mds.local using any of the configured protocols. Aug 06, 2009 DCOM was unable to communicate with the computer hutt.deansci.ubc.ca using any of the cPM MESSAGE DCOM was unable to communicate with the computer ANOTHERSERVER.DOMAIN.lan using any of the configured protocol So when you put another server on the network and just set it up for a specific purpose it may not open up all of the needed protocols in the firewall that it needs to correspond to the SBS 2008 box. So here's how to adjust the firewall to get the Dcom messages out of your event logs: Event ID 10009 Source DCOM: http://www.eventid.net/display.asp?eventid=10009&eventno=579&source=DCOM&phase=1 Check the firewall settings and enable the firewall exception rule To check the firewall settings and enable the firewall exception rule: Click Start, and then click Run. Type wf.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. In the console tree, click Inbound rules. In the list of firewall exception rules, look for COM+ Network Access (DCOM In). If the firewall exception rule is not enabled, in the details pane click Enable rule, and then scroll horizontally to confirm that the protocol is TCP and the LocalPort is 135. Close Windows Firewall with Advanced Security Right mouse click and enable the rule Then to get the server to be able to query thename/model of theremote server enable the WMI in theinbound firewall rules as well. Once you do that your server will report into the console and provide the hardware information on the Network/Computers tab. Posted in: Migrationextras 3 Thoughts on “Dcom was unable to communicate with the computer” Dennis on November 29, 2009 at 3:41 pm said: Should the actions be performed on the SERVER, or on the machine in question that cannot be reached? admin on November 29, 2009 at 4:40 pm said: I was lazy and just did this on the machine in question. You could do a group policy at the server to push out this policy to the machine in question. RVR on December 28, 2009 at 3:29 pm said: As per http://support.microsoft.com/kb/957713 article we have resolved the DCOM issue. 2.1 DCOM Event ID 10009: Problem: The DCOM event ID 10009 will occur when a client workstation has a miscon