Error Dcom 10009
Contents |
platform and distributed applications How to troubleshoot DCOM 10009 error logged in system event? ★★★★★★★★★★★★★★★ APGC DSI TeamMarch 15, 201021 0 0 0 dcom error 10009 xp Symptom: Sometimes, we may see below DCOM 10009 errors in our
Dcom Error 10009 Windows Xp
system event, or we may receive the exception code 0x800706ba in our DCOM client application: Event Type: dcom error 10009 server 2008 ErrorEvent Source: DCOM|Event Category: NoneEvent ID: 10009Date: 2010-2-22Time: 10:02:07User: N/AComputer:
Dcom Error 10016
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 communication issue exists between these two servers, for example: serv
Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent dcom error 10009 xp pro ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 10009 (Error) Source: dcom 10009 dcom was unable to communicate with the computer DCOM How important is this event? (41 votes) 1 2 3 4 5 not important very
Dcom Error 10009 Server 2008 R2
important Description < < Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C https://blogs.msdn.microsoft.com/asiatech/2010/03/15/how-to-troubleshoot-dcom-10009-error-logged-in-system-event/ 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 https://community.spiceworks.com/windows_event/show/4-dcom-10009 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 configured protocols.Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of http://www.eventid.net/display-eventid-10009-source-DCOM-eventno-579-phase-1.htm them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and dcom error other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 10009 Source: DCOM Source: DCOM Maintenance: Recommended maintenance tasks for Windows servers Type: Error Description:DCOM was unable to communicate with the computer