Event ID 10009 — COM Remote Service Availability

Updated: February 22, 2008

Applies To: Windows Server 2008

red

COM+ applications use Microsoft Component Object Model (COM) technology in Microsoft Windows operating systems to communicate and take advantage of Windows services. COM technologies include COM+, DCOM, and ActiveX Controls.

COM+ Network Access enables remote invocation of applications that are built with COM+. The firewall exception rule, COM+ Network Access (DCOM In), must be turned on for the TCP protocol and LocalPort 135.

Event Details

Product: Windows Operating System
ID: 10009
Source: Microsoft-Windows-DistributedCOM
Version: 6.0
Symbolic Name: EVENT_RPCSS_REMOTE_SIDE_UNAVAILABLE
Message: DCOM was unable to communicate with the computer %1 using any of the configured protocols.

Resolve

Ensure that the remote computer is available

There is a problem accessing the COM Service on a remote computer. To resolve this problem:

  • Ensure that the remote computer is online.
  • This problem may be the result of a firewall blocking the connection. For security, COM+ network access is not enabled by default. Check the system to determine whether the firewall is blocking the remote connection.
  • Other reasons for the problem might be found in the Extended Remote Procedure Call (RPC) Error information that is available in Event Viewer.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Ensure that the remote computer is online

To verify that the remote computer is online and the computers are communicating over the network:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. At the command prompt, type ping, followed by a space and the remote computer name, and then press ENTER. For example, to check that your server can communicate over the network with a computer named ContosoWS2008, type ping ContosoWS2008, and then press ENTER.
  3. A successful connection results in a set of replies from the other computer and a set of ping statistics.

Check the firewall settings and enable the firewall exception rule

To check the firewall settings and enable the firewall exception rule:

  1. Click Start, and then click Run.
  2. 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.
  3. In the console tree, click Inbound rules.
  4. In the list of firewall exception rules, look for COM+ Network Access (DCOM In).
  5. 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.

Review available Extended RPC Error information for this event in Event Viewer

To review available Extended RPC Error information for this event in Event Viewer:

  1. Click Start, and then click Run.
  2. Type comexp.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.
  3. Under Console Root, expand Event Viewer (Local).
  4. In the details pane, look for your event in the Summary of Administrative Events, and then double-click the event to open it.
  5. The Extended RPC Error information that is available for this event is located on the Details tab. Expand the available items on the Details tab to review all available information.

    For more information about Extended RPC Error information and how to interpret it, see Obtaining Extended RPC Error Information (http://go.microsoft.com/fwlink/?LinkId=105593).

Verify

You can verify that the COM service is available remotely by running the Component Services administrative tool and ensuring that the required properties for remote access are configured.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To open Component Services and verify that the required properties for remote access are configured:

  1. Click Start, and then click Run.
  2. Type comexp.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.
  3. To locate your computer, click Component Services, click Computers, and then click My Computer.
  4. Right-click My Computer, and then click Properties.
  5. Click the Default Protocols tab, and confirm that the appropriate communication protocols are listed.
  6. Click each protocol, and then click Properties to verify that the settings for the protocol are correct.

You can verify that the COM+ Network Access firewall exception rule is enabled so that components can communicate over the network.

To open Windows Firewall with Advanced Security and verify that the firewall exception rule for COM+ Network Access is enabled:

  1. Click Start, and then click Run.
  2. 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.
  3. In the console tree, click Inbound rules.
  4. In the list of firewall exception rules, locate COM+ Network Access (DCOM In).
  5. Ensure that this firewall exception rule is enabled, and then scroll horizontally to confirm that the protocol is TCP and the LocalPort is 135.

Related Management Information

COM Remote Service Availability

Application Server

Tags :


Community Content

jdpp
huh
We already know this, why does this not mention what steps can be found to locate these items to begin with. Just saying. We already know these computers should be on, but we removed them. Dont tell me to go to tech soup either. I hate trolls. Either help or shut up.
Tags :

Thomas Lee
DCOM Unable to communicate with old servername
<p>We have the same symptom, the Windows 2008 R2 server has been renamed and DCOM is still trying to communicate with the old name...</p> <p> <br /> Log Name: System<br /> Source: Microsoft-Windows-DistributedCOM<br /> DCOM was unable to communicate with the computer OldComputername using any of the configured protocols.<br /> Event Xml:<br /> &lt;Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"&gt;<br />&lt;System&gt;<br />&lt;Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /&gt;<br /> &lt;EventID Qualifiers="49152"&gt;10009&lt;/EventID&gt;<br />&lt;Version&gt;&lt;/Version&amp;gt;<br />&lt;Level&gt;2&lt;/Level&amp;gt;<br /> &lt;Task&gt;&lt;/Task&gt;<br /> &lt;Opcode&gt;&lt;/Opcode&gt;<br /> &lt;Keywords&lt;0x80000000000000&amp;lt;/Keywords&gt;<br /> &lt;EventRecordID&gt;383020&lt;/EventRecordID&gt;<br /> &lt;Correlation /&gt;<br /> &gt;Execution ProcessID="0" ThreadID="0" /&gt;<br /> &lt;Channel&gt;System&lt;/Channel&gt;<br /> &lt;Computer&gt;NewComputername&lt;/Computer&gt;<br /> &lt;Security /&gt;<br /> &lt;/System&gt;<br /> &lt;EventData&gt;<br /> &lt;Data Name="param1"&gt;OldComputerName&lt;/Data&gt;<br /> &lt;/Event&gt;</p> <p> <br /> DCOM was unable to communicate with the computer DBNNTEWEB-G4S using any of the configured protocols.DCOM was unable to communicate with the computer DBNNTEWEB-G4S using any of the configured protocols.</p> <p>The GUID links to System32\oleres</p> <p>Any ideas?</p> <p> <br /> </p> <p>[tfl - 28 02 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the Technet Forums at http://forums.microsoft.com/technet, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.<br /></p>

Thomas Lee
Computer doesn't exist
I have this error every 2min on my server, but the computer doesn't exist anymore. When I Ping it, I ping another computer. I deleted the computer from AD , did a flushdns , and when I ping it, I have ping from another computer.<br /><br /> Can anyone help me please.<br /><br /> Thanks<br /><br />[tfl - 28 02 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the Technet Forums at http://forums.microsoft.com/technet, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.<br />
Tags :

Thomas Lee
Computer Doesn't exist
Same symptom for me a Computer has been renamed and DCOM is still trying to communicate with the old name...<br /> What to do?<br /> Thanks,<br /> Dom<br /><br />[tfl - 28 02 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the Technet Forums at http://forums.microsoft.com/technet, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.<br />
Tags :

Thomas Lee
Computer Re-Named
i renamed a server then i started getting this error each 2 minutes, any solution?<br /><br />[tfl - 28 02 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the Technet Forums at http://forums.microsoft.com/technet, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.<br />
Tags :

Thomas Lee
Removed Server
We removed a server from our rack and aren't replacing it. We are receiving this error. The server was removed from AD. How can we get rid of this error?<br /><br />[tfl - 28 02 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the Technet Forums at http://forums.microsoft.com/technet, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.<br />
Tags :

Thomas Lee
Computer Doesn't Exist - Why is this not an OPTION in this EVENT ID Resolution
We also have remove these computers that we are getting these event logs for - From what I can see this question has been asked multiple times and not response - PLEASE this actually is severely affecting our server as we are getting literally thousands of these event logs per day.<br /><br />[tfl - 28 02 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the Technet Forums at http://forums.microsoft.com/technet, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.<br />
Tags :

LoneWolf15
Error involves DNS forwarders
I have a customer whose server is throwing these errors --and the IP addresses are of the server's DNS forwarders outside the network.<br /><br /> Why would DCOM be trying to communicate with the DNS forwarders?&nbsp; I've done some searching, but found no satisfactory answers.<br />
Tags :

Page view tracker