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

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: 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 "No such host is known" 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:

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 "Symptoms" 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:

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: