Microsoft KB Archive/910695

= FIX: You cannot obtain detailed error information about DCOM 10009 errors in Windows Server 2003 =

Article ID: 910695

Article Last Modified on 12/5/2007

-

APPLIES TO

 Microsoft COM+ 1.5, when used with:  Microsoft Windows Server 2003, Standard Edition (32-bit x86)

 Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

 Microsoft Windows Server 2003, Datacenter Edition (32-bit x86) 

-

<div class="notice_section">

<div class="notice_section">

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

<div class="summary_section">

SUMMARY
''This article discusses a hotfix that enables new logging functionality when DCOM errors occur in Microsoft COM+ applications. It also briefly discusses DCOM errors, the causes of DCOM errors, and how to troubleshoot DCOM errors.''

<div class="symptoms_section">

SYMPTOMS
When a DCOM error occurs, the error message does not contain sufficient information to determine the cause of the DCOM error. Instead, you may receive an error message that is similar to the following in Event Viewer:

Event Type: Error

Event Source: DCOM

Event ID: 10009

Description: DCOM was unable to communicate with the computer  using any of the configured protocols.

Note In this error message,  is a placeholder for the name of the computer that is unavailable.

No other information is available in the error log. To locate more information about the error that occurred, you must typically debug the application or analyze the network traffic.

<div class="resolution_section">

RESOLUTION
A hotfix for this problem is now available from Microsoft. After you apply this hotfix, DCOM will log remote procedure call (RPC) extended error information in the event log to help determine the cause of the DCOM error.

Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Hotfix rollup package information
This problem is fixed in Microsoft Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 7. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

910730 Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 7

Prerequisites
You must have Windows Server 2003 installed to apply this hotfix.

Restart requirement
You must restart the computer after you modify the registry to enable this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

Registry information
You must modify the registry to enable this hotfix.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To enable this hotfix, follow these steps: <ol> Click Start, click Run, type regedit, and then click OK.</li> Locate and then click the following registry key:

</li> On the Edit menu, click Add Value, and then add the following registry value. </li> Quit Registry Editor.</li></ol>

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 SP1, x86
<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Windows Server 2003 Service Pack 2.

<div class="moreinformation_section">

MORE INFORMATION
The DCOM 10009 event contains insufficient data about the underlying error that caused them to occur. Usually, the DCOM 10009 events are logged because of network communications failures with the DCOM server. These include problems such as name resolution issues and firewall issues. These issues frequently lead to 0x6ba (0x800706ba) RPC errors. To gather additional error information about the underlying error with this fix in Windows Server 2003, enable RPC Extended Error information (EEINFO). When EEINFO is enabled, additional data is written to the DCOM 10009 event data section of the event. In Windows Vista, you do not have to turn on EEINFO because it is on by default and will be dumped in the DCOM 10009 event data by default. EEinfo will typically contain winsock specific errors like 10048 (WSAEADDRINUSE) such as when all available TCP ports are exhausted.

For more information about RPC Extended Error information, including how to enable and how to interpret the information, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/aa373803.aspx

http://msdn2.microsoft.com/en-us/library/aa379109.aspx

The following is an example of the event that is logged. It contains the additional useful data. In particular, the status, gencomp, and detloc information in the error data will be of interest. For example, the status 11001 is &quot;No such host is known&quot; and is generated by winsock (gencomp = 8). Event Type: Error

Event Source: DCOM

Event Category: None

Event ID: 10009

Date: <Date>

Time: <Time>

User: N/A

Computer: <Server>

Description: DCOM was unable to communicate with the computer <Server>using any of the configured protocols.

For more information, see Help and Support Center at the following Microsoft Web site:

http://support.microsoft.com

<pre class="fixed_text">Data: 0000: 3c 52 65 63 6f 72 64 23 <Record# 0008: 31 3a 20 43 6f 6d 70 75 1: Compu 0010: 74 65 72 3d 28 6e 75 6c ter=(nul 0018: 6c 29 3b 50 69 64 3d 31 l);Pid=1 0020: 31 30 30 3b 31 2f 35 2f 100;1/5/ 0028: 32 30 30 36 20 31 34 3a 2006 14: 0030: 34 3a 33 33 3a 31 31 36 4:33:116 0038: 3b 53 74 61 74 75 73 3d ;Status= 0040: 31 37 32 32 3b 47 65 6e 1722;Gen 0048: 63 6f 6d 70 3d 38 3b 44 comp=8;D 0050: 65 74 6c 6f 63 3d 33 32 etloc=32 0058: 32 3b 46 6c 61 67 73 3d 2;Flags= 0060: 30 3b 50 61 72 61 6d 73 0;Params 0068: 3d 30 3b 3e 3c 52 65 63 =0;><Rec 0070: 6f 72 64 23 32 3a 20 43 ord#2: C 0078: 6f 6d 70 75 74 65 72 3d omputer= 0080: 28 6e 75 6c 6c 29 3b 50 (null);P 0088: 69 64 3d 31 31 30 30 3b id=1100; 0090: 31 2f 35 2f 32 30 30 36 1/5/2006 0098: 20 31 34 3a 34 3a 33 33 14:4:33 00a0: 3a 31 31 36 3b 53 74 61 :116;Sta 00a8: 74 75 73 3d 31 31 30 30 tus=1100 00b0: 31 3b 47 65 6e 63 6f 6d 1;Gencom 00b8: 70 3d 38 3b 44 65 74 6c p=8;Detl 00c0: 6f 63 3d 33 32 30 3b 46 oc=320;F 00c8: 6c 61 67 73 3d 30 3b 50 lags=0;P 00d0: 61 72 61 6d 73 3d 31 3b arams=1; 00d8: 7b 50 61 72 61 6d 23 30 {Param#0 00e0: 3a 7d 65 72 54 48 65 72 :Server 00e8: 7d 3e }> The error that is mentioned in the &quot;Symptoms&quot; section is frequently a network communications error. The following are possible causes of this error:
 * Name resolution errors are occurring.
 * All TCP ports on the server are being used.
 * TCP port collisions are occurring.

To troubleshoot DCOM 10009 errors, use the following methods.

Method 1: Verify that name resolution is working correctly
The activation page for a COM+ proxy application contains a Remote Server Name (RSN) property. The RSN property can be an IP address, a Fully Qualified Domain Name (FQDN), or a NetBIOS name. To troubleshoot this issue, use the ping command to test connectivity to the remote server by using the IP address, the FQDN, and the NetBIOS name.

Method 2: Verify TCP port usage
When a client makes DCOM calls to a COM+ server application, each connection may use a different TCP port. Therefore, all TCP ports on the server may be used. When this condition occurs, the server cannot accept additional connections.

For more information about how to determine TCP port usage when you troubleshoot TCP/IP connectivity issues, click the following article numbers to view the articles in the Microsoft Knowledge Base:

832919 New features and functionality in PortQry version 2.0

301512 Many TCP connections are established for COM+ proxy/stub

Method 3: Verify basic network connectivity to troubleshoot TCP collision issues
For more information about how use basic network troubleshooting to resolve TCP collision errors, click the following article number to view the article in the Microsoft Knowledge Base:

325487 How to troubleshoot network connectivity problems

<div class="references_section">