Distributed Dcom Error 10009
Contents |
platform and distributed applications How to troubleshoot DCOM 10009 error dcom error 10009 server 2008 r2 logged in system event? ★★★★★★★★★★★★★★★ APGC DSI TeamMarch 15, dcom error 10009 unable to communicate with computer 201021 0 0 0 Symptom: Sometimes, we may see below DCOM 10009 errors distributedcom 10009 in our system event, or we may receive the exception code 0x800706ba in our DCOM client application: Event Type: ErrorEvent Source: DCOM|Event Category:
Distributedcom 10009 Domain Controller
NoneEvent ID: 10009Date: 2010-2-22Time: 10:02:07User: N/AComputer:
Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS New Server Room Replace all of the servers and Implement ereignis 10009 distributedcom a new server with virtualization and also replace the all of
Distributedcom 10009 Nas
the network hardware with up to date systems Client 1 Relocation Project Complete business relocation project to
Dcom Was Unable To Communicate With The Computer 10028
a different physical location. From the start of working with the architect on entire floor dimensions to the final build out. SQL 2012 CLUSTER DEPLOYMENT SQL cluster deployment, will https://blogs.msdn.microsoft.com/asiatech/2010/03/15/how-to-troubleshoot-dcom-10009-error-logged-in-system-event/ update when have more time TECHNOLOGY IN THIS DISCUSSION Broadcom NetXt...net Controller Join the Community! Creating your account only takes a few minutes. Join Now I have a server at a client site that is registering DCOM 10009 errors once an hour or so in the event log. There is no other events logged from DCOM with the 10009, https://community.spiceworks.com/topic/502109-dcom-10009-error-on-dns-forwarders and the 10009 errors come in pairs, one for each Forwarder I have setup in DNS. An example of the error is listed below (4.2.2.1 and 8.8.8.8). I have done some research on this, and what I have found talks about setting ports and firewall rules to allow RPC so the DCOM request is successful. I don't think that is my answer here given that these are public DNS servers. I am wondering if it has to do with my internal domain name. Instead of %client%.local, they used %client%.com. I'm pretty sure that these errors arent anything to worry about, but they are mucking up my logs and I want them gone. Any suggestions? *Note that the server in question is the DNS server, as it is the only Domain Controller on the network. (I wish they had a backup DC.). That is why the server has itself listed in its DNS config.
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated http://www.eventid.net/display-eventid-10009-source-DCOM-eventno-579-phase-1.htm view for all logs Free for subscribers Event ID: 10009 Source: DCOM http://blogs.msmvps.com/bradley/2009/11/28/dcom-was-unable-to-communicate-with-the-computer/ Source: DCOM Maintenance: Recommended maintenance tasks for Windows servers Type: Error Description:DCOM was unable to communicate with the computer
PM 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 misconfigured firewall or other issues affecting its network communications within the domain. For example, if the workstation is not managed by an SBS GPO. In this scenario, the DCOM event ID 10009 will happen repeatedly, potentially hundreds per day. Resolution: To attempt to resolve configuration issues with the firewall try the following: Make sure to allow remote management exception. Depending on your firewall solution this might be implemented or might require opening several ports. Unfortunately, t