Microsoft KB Archive/910695

From BetaArchive Wiki

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)



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


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.


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 ComputerName using any of the configured protocols.

Note In this error message, ComputerName 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.

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


Hotfix information

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:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Ole

  3. On the Edit menu, click Add Value, and then add the following registry value.
    Value name Data type Value Notes
    EnableEELogging REG_DWORD 1 This registry value enables or disables logging in text format. This format is appropriate for manual analysis of the logs.
    LogEEInfoAsNative REG_DWORD 1 This registry value enables or disables logging in Event Viewer. If you enable this kind of logging, you can use automated analysis to examine the extended error information.
  4. Quit Registry Editor.

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.

File information

Windows Server 2003, Itanium Architecture
File name File version File size Date Time Platform Service branch
Catsrv.dll 2001.12.4720.445 622,080 17-Nov-2005 02:45 IA-64 Not Applicable
Catsrvut.dll 2001.12.4720.445 1,555,456 17-Nov-2005 02:45 IA-64 Not Applicable
Clbcatex.dll 2001.12.4720.445 263,680 17-Nov-2005 02:45 IA-64 Not Applicable
Clbcatq.dll 2001.12.4720.445 1,287,168 17-Nov-2005 02:45 IA-64 Not Applicable
Colbact.dll 2001.12.4720.445 171,008 17-Nov-2005 02:45 IA-64 Not Applicable
Comadmin.dll 2001.12.4720.445 411,136 17-Nov-2005 02:45 IA-64 Not Applicable
Comrepl.dll 2001.12.4720.445 275,456 17-Nov-2005 02:45 IA-64 Not Applicable
Comsvcs.dll 2001.12.4720.445 3,143,168 17-Nov-2005 02:45 IA-64 Not Applicable
Comuid.dll 2001.12.4720.445 1,873,408 17-Nov-2005 02:45 IA-64 Not Applicable
Es.dll 2001.12.4720.445 654,336 17-Nov-2005 02:45 IA-64 Not Applicable
Msdtcprx.dll 2001.12.4720.445 1,311,744 17-Nov-2005 02:45 IA-64 Not Applicable
Msdtctm.dll 2001.12.4720.445 3,152,384 17-Nov-2005 02:45 IA-64 Not Applicable
Msdtcuiu.dll 2001.12.4720.445 463,360 17-Nov-2005 02:45 IA-64 Not Applicable
Mtxclu.dll 2001.12.4720.445 203,776 17-Nov-2005 02:45 IA-64 Not Applicable
Mtxdm.dll 2001.12.4720.445 45,568 17-Nov-2005 02:45 IA-64 Not Applicable
Mtxoci.dll 2001.12.4720.445 320,000 17-Nov-2005 02:45 IA-64 Not Applicable
Ole32.dll 5.2.3790.445 3,582,976 17-Nov-2005 02:45 IA-64 Not Applicable
Olecli32.dll 5.2.3790.445 223,744 17-Nov-2005 02:45 IA-64 Not Applicable
Olecnv32.dll 5.2.3790.445 89,088 17-Nov-2005 02:45 IA-64 Not Applicable
Rpcproxy.dll 5.2.3790.141 73,216 17-Nov-2005 02:45 IA-64 Not Applicable
Rpcrt4.dll 5.2.3790.141 2,150,400 17-Nov-2005 02:45 IA-64 Not Applicable
Rpcss.dll 5.2.3790.445 694,272 17-Nov-2005 02:45 IA-64 Not Applicable
Stclient.dll 2001.12.4720.445 140,800 17-Nov-2005 02:45 IA-64 Not Applicable
Txflog.dll 2001.12.4720.445 280,064 17-Nov-2005 02:45 IA-64 Not Applicable
Wcatsrv.dll 2001.12.4720.445 258,560 17-Nov-2005 02:45 x86 WOW
Wcatsrvut.dll 2001.12.4720.445 584,192 17-Nov-2005 02:45 x86 WOW
Wclbcatex.dll 2001.12.4720.445 98,304 17-Nov-2005 02:45 x86 WOW
Wclbcatq.dll 2001.12.4720.445 490,496 17-Nov-2005 02:45 x86 WOW
Wcolbact.dll 2001.12.4720.445 56,832 17-Nov-2005 02:45 x86 WOW
Wcomadmin.dll 2001.12.4720.445 189,440 17-Nov-2005 02:45 x86 WOW
Wcomsvcs.dll 2001.12.4720.445 1,209,344 17-Nov-2005 02:45 x86 WOW
Wes.dll 2001.12.4720.445 226,816 17-Nov-2005 02:45 x86 WOW
Wmsdtcprx.dll 2001.12.4720.445 445,952 17-Nov-2005 02:45 x86 WOW
Wmsdtcuiu.dll 2001.12.4720.445 160,768 17-Nov-2005 02:45 x86 WOW
Wmtxclu.dll 2001.12.4720.445 76,288 17-Nov-2005 02:45 x86 WOW
Wmtxdm.dll 2001.12.4720.445 18,944 17-Nov-2005 02:45 x86 WOW
Wmtxoci.dll 2001.12.4720.445 109,056 17-Nov-2005 02:45 x86 WOW
Wole32.dll 5.2.3790.445 1,193,984 17-Nov-2005 02:45 x86 WOW
Wolecli32.dll 5.2.3790.445 72,192 17-Nov-2005 02:45 x86 WOW
Wolecnv32.dll 5.2.3790.445 36,352 17-Nov-2005 02:45 x86 WOW
Wrpcproxy.dll 5.2.3790.141 26,112 17-Nov-2005 02:45 x86 WOW
Wrpcrt4.dll 5.2.3790.141 544,256 17-Nov-2005 02:45 x86 WOW
Wstclient.dll 2001.12.4720.445 60,416 17-Nov-2005 02:45 x86 WOW
Wtxflog.dll 2001.12.4720.445 95,232 17-Nov-2005 02:45 x86 WOW
Windows Server 2003 SP1, Itanium Architecture
File name File version File size Date Time Platform SP requirement Service branch
Catsrv.dll 2001.12.4720.2572 657,408 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Catsrvut.dll 2001.12.4720.2572 1,632,256 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Clbcatex.dll 2001.12.4720.2572 279,040 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Clbcatq.dll 2001.12.4720.2572 1,353,728 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Colbact.dll 2001.12.4720.2572 181,760 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Comadmin.dll 2001.12.4720.2572 420,352 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Comrepl.dll 2001.12.4720.2572 285,184 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Comsvcs.dll 2001.12.4720.2572 3,366,912 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Comuid.dll 2001.12.4720.2572 1,977,856 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Es.dll 2001.12.4720.2572 701,440 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Msdtcprx.dll 2001.12.4720.2572 1,337,344 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Msdtctm.dll 2001.12.4720.2572 3,096,064 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Msdtcuiu.dll 2001.12.4720.2572 486,400 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Mtxclu.dll 2001.12.4720.2572 207,872 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Mtxdm.dll 2001.12.4720.2572 47,616 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Mtxoci.dll 2001.12.4720.2572 322,048 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Ole32.dll 5.2.3790.2572 3,999,744 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Olecli32.dll 5.2.3790.2572 252,416 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Olecnv32.dll 5.2.3790.2572 90,112 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Rpcss.dll 5.2.3790.2572 859,136 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Stclient.dll 2001.12.4720.2572 149,504 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Txflog.dll 2001.12.4720.2572 301,568 17-Nov-2005 02:45 IA-64 SP1 Not Applicable
Wcatsrv.dll 2001.12.4720.2572 273,920 17-Nov-2005 02:45 x86 SP1 WOW
Wcatsrvut.dll 2001.12.4720.2572 619,520 17-Nov-2005 02:45 x86 SP1 WOW
Wclbcatex.dll 2001.12.4720.2572 104,960 17-Nov-2005 02:45 x86 SP1 WOW
Wclbcatq.dll 2001.12.4720.2572 514,048 17-Nov-2005 02:45 x86 SP1 WOW
Wcolbact.dll 2001.12.4720.2572 58,880 17-Nov-2005 02:45 x86 SP1 WOW
Wcomadmin.dll 2001.12.4720.2572 196,608 17-Nov-2005 02:45 x86 SP1 WOW
Wcomsvcs.dll 2001.12.4720.2572 1,268,736 17-Nov-2005 02:45 x86 SP1 WOW
Wcomuid.dll 2001.12.4720.2572 596,480 17-Nov-2005 02:45 x86 SP1 WOW
Wes.dll 2001.12.4720.2572 238,592 17-Nov-2005 02:45 x86 SP1 WOW
Wmsdtcprx.dll 2001.12.4720.2572 470,528 17-Nov-2005 02:45 x86 SP1 WOW
Wmsdtcuiu.dll 2001.12.4720.2572 165,888 17-Nov-2005 02:45 x86 SP1 WOW
Wmtxclu.dll 2001.12.4720.2572 78,848 17-Nov-2005 02:45 x86 SP1 WOW
Wmtxdm.dll 2001.12.4720.2572 20,992 17-Nov-2005 02:45 x86 SP1 WOW
Wmtxoci.dll 2001.12.4720.2572 111,104 17-Nov-2005 02:45 x86 SP1 WOW
Wole32.dll 5.2.3790.2572 1,247,232 17-Nov-2005 02:45 x86 SP1 WOW
Wolecli32.dll 5.2.3790.2572 75,776 17-Nov-2005 02:45 Not Applicable SP1 WOW
Wolecnv32.dll 5.2.3790.2572 38,912 17-Nov-2005 02:45 x86 SP1 WOW
Wstclient.dll 2001.12.4720.2572 64,000 17-Nov-2005 02:45 x86 SP1 WOW
Wtxflog.dll 2001.12.4720.2572 98,816 17-Nov-2005 02:45 x86 SP1 WOW
Windows Server 2003 SP1, x64
File name File version File size Date Time Platform SP requirement Service branch
Catsrv.dll 2001.12.4720.2572 418,304 17-Nov-2005 02:45 x64 SP1 Not Applicable
Catsrvut.dll 2001.12.4720.2572 1,083,904 17-Nov-2005 02:45 x64 SP1 Not Applicable
Clbcatex.dll 2001.12.4720.2572 175,104 17-Nov-2005 02:45 x64 SP1 Not Applicable
Clbcatq.dll 2001.12.4720.2572 882,688 17-Nov-2005 02:45 x64 SP1 Not Applicable
Colbact.dll 2001.12.4720.2572 97,280 17-Nov-2005 02:45 x64 SP1 Not Applicable
Comadmin.dll 2001.12.4720.2572 288,768 17-Nov-2005 02:45 x64 SP1 Not Applicable
Comrepl.dll 2001.12.4720.2572 188,928 17-Nov-2005 02:45 x64 SP1 Not Applicable
Comsvcs.dll 2001.12.4720.2572 2,194,944 17-Nov-2005 02:45 x64 SP1 Not Applicable
Comuid.dll 2001.12.4720.2572 1,478,144 17-Nov-2005 02:45 x64 SP1 Not Applicable
Es.dll 2001.12.4720.2572 365,568 17-Nov-2005 02:45 x64 SP1 Not Applicable
Msdtcprx.dll 2001.12.4720.2572 830,464 17-Nov-2005 02:45 x64 SP1 Not Applicable
Msdtctm.dll 2001.12.4720.2572 2,073,088 17-Nov-2005 02:45 x64 SP1 Not Applicable
Msdtcuiu.dll 2001.12.4720.2572 291,328 17-Nov-2005 02:45 x64 SP1 Not Applicable
Mtxclu.dll 2001.12.4720.2572 144,896 17-Nov-2005 02:45 x64 SP1 Not Applicable
Mtxdm.dll 2001.12.4720.2572 30,208 17-Nov-2005 02:45 x64 SP1 Not Applicable
Mtxoci.dll 2001.12.4720.2572 175,104 17-Nov-2005 02:45 x64 SP1 Not Applicable
Ole32.dll 5.2.3790.2572 2,546,688 17-Nov-2005 02:45 x64 SP1 Not Applicable
Olecli32.dll 5.2.3790.2572 131,584 17-Nov-2005 02:45 x64 SP1 Not Applicable
Olecnv32.dll 5.2.3790.2572 56,832 17-Nov-2005 02:45 x64 SP1 Not Applicable
Rpcss.dll 5.2.3790.2572 698,368 17-Nov-2005 02:45 x64 SP1 Not Applicable
Stclient.dll 2001.12.4720.2572 101,888 17-Nov-2005 02:45 x64 SP1 Not Applicable
Txflog.dll 2001.12.4720.2572 180,224 17-Nov-2005 02:45 x64 SP1 Not Applicable
Wcatsrv.dll 2001.12.4720.2572 273,920 17-Nov-2005 02:45 x86 SP1 WOW
Wcatsrvut.dll 2001.12.4720.2572 619,520 17-Nov-2005 02:45 x86 SP1 WOW
Wclbcatex.dll 2001.12.4720.2572 104,960 17-Nov-2005 02:45 x86 SP1 WOW
Wclbcatq.dll 2001.12.4720.2572 514,048 17-Nov-2005 02:45 x86 SP1 WOW
Wcolbact.dll 2001.12.4720.2572 58,880 17-Nov-2005 02:45 x86 SP1 WOW
Wcomadmin.dll 2001.12.4720.2572 196,608 17-Nov-2005 02:45 x86 SP1 WOW
Wcomsvcs.dll 2001.12.4720.2572 1,268,736 17-Nov-2005 02:45 x86 SP1 WOW
Wcomuid.dll 2001.12.4720.2572 596,480 17-Nov-2005 02:45 x86 SP1 WOW
Wes.dll 2001.12.4720.2572 238,592 17-Nov-2005 02:45 x86 SP1 WOW
Wmsdtcprx.dll 2001.12.4720.2572 470,528 17-Nov-2005 02:45 x86 SP1 WOW
Wmsdtcuiu.dll 2001.12.4720.2572 165,888 17-Nov-2005 02:45 x86 SP1 WOW
Wmtxclu.dll 2001.12.4720.2572 78,848 17-Nov-2005 02:45 x86 SP1 WOW
Wmtxdm.dll 2001.12.4720.2572 20,992 17-Nov-2005 02:45 x86 SP1 WOW
Wmtxoci.dll 2001.12.4720.2572 111,104 17-Nov-2005 02:45 x86 SP1 WOW
Wole32.dll 5.2.3790.2572 1,247,232 17-Nov-2005 02:45 x86 SP1 WOW
Wolecli32.dll 5.2.3790.2572 75,776 17-Nov-2005 02:45 Not Applicable SP1 WOW
Wolecnv32.dll 5.2.3790.2572 38,912 17-Nov-2005 02:45 x86 SP1 WOW
Wstclient.dll 2001.12.4720.2572 64,000 17-Nov-2005 02:45 x86 SP1 WOW
Wtxflog.dll 2001.12.4720.2572 98,816 17-Nov-2005 02:45 x86 SP1 WOW
Windows Server 2003, x86
File name File version File size Date Time
Catsrv.dll 2001.12.4720.445 258,560 17-Nov-2005 03:09
Catsrvut.dll 2001.12.4720.445 584,192 17-Nov-2005 03:09
Clbcatex.dll 2001.12.4720.445 98,304 17-Nov-2005 03:09
Clbcatq.dll 2001.12.4720.445 490,496 17-Nov-2005 03:09
Colbact.dll 2001.12.4720.445 56,832 17-Nov-2005 03:09
Comadmin.dll 2001.12.4720.445 189,440 17-Nov-2005 03:09
Comrepl.dll 2001.12.4720.445 86,528 17-Nov-2005 03:09
Comsvcs.dll 2001.12.4720.445 1,209,344 17-Nov-2005 03:09
Comuid.dll 2001.12.4720.445 565,248 17-Nov-2005 03:09
Es.dll 2001.12.4720.445 226,816 17-Nov-2005 03:09
Msdtcprx.dll 2001.12.4720.445 445,952 17-Nov-2005 03:09
Msdtctm.dll 2001.12.4720.445 965,120 17-Nov-2005 03:09
Msdtcuiu.dll 2001.12.4720.445 160,768 17-Nov-2005 03:09
Mtxclu.dll 2001.12.4720.445 76,288 17-Nov-2005 03:09
Mtxdm.dll 2001.12.4720.445 18,944 17-Nov-2005 03:09
Mtxoci.dll 2001.12.4720.445 109,056 17-Nov-2005 03:09
Ole32.dll 5.2.3790.445 1,193,984 17-Nov-2005 03:09
Olecli32.dll 5.2.3790.445 72,192 17-Nov-2005 03:09
Olecnv32.dll 5.2.3790.445 36,352 17-Nov-2005 03:09
Rpcproxy.dll 5.2.3790.141 26,112 16-Mar-2004 03:17
Rpcrt4.dll 5.2.3790.141 659,968 16-Mar-2004 03:17
Rpcss.dll 5.2.3790.445 296,960 17-Nov-2005 03:09
Stclient.dll 2001.12.4720.445 60,416 17-Nov-2005 03:09
Txflog.dll 2001.12.4720.445 95,232 17-Nov-2005 03:09
Windows Server 2003 SP1, x86
File name File version File size Date Time Platform SP requirement
Catsrv.dll 2001.12.4720.2572 273,920 17-Nov-2005 03:20 x86 SP1
Catsrvut.dll 2001.12.4720.2572 619,520 17-Nov-2005 03:20 x86 SP1
Clbcatex.dll 2001.12.4720.2572 104,960 17-Nov-2005 03:20 x86 SP1
Clbcatq.dll 2001.12.4720.2572 514,048 17-Nov-2005 03:20 x86 SP1
Colbact.dll 2001.12.4720.2572 58,880 17-Nov-2005 03:20 x86 SP1
Comadmin.dll 2001.12.4720.2572 196,608 17-Nov-2005 03:20 x86 SP1
Comrepl.dll 2001.12.4720.2572 88,576 17-Nov-2005 03:20 x86 SP1
Comsvcs.dll 2001.12.4720.2572 1,268,736 17-Nov-2005 03:20 x86 SP1
Comuid.dll 2001.12.4720.2572 596,480 17-Nov-2005 03:20 x86 SP1
Es.dll 2001.12.4720.2572 238,592 17-Nov-2005 03:20 x86 SP1
Msdtcprx.dll 2001.12.4720.2572 470,528 17-Nov-2005 03:20 x86 SP1
Msdtctm.dll 2001.12.4720.2572 1,009,664 17-Nov-2005 03:20 x86 SP1
Msdtcuiu.dll 2001.12.4720.2572 165,888 17-Nov-2005 03:20 x86 SP1
Mtxclu.dll 2001.12.4720.2572 78,848 17-Nov-2005 03:20 x86 SP1
Mtxdm.dll 2001.12.4720.2572 20,992 17-Nov-2005 03:20 x86 SP1
Mtxoci.dll 2001.12.4720.2572 111,104 17-Nov-2005 03:20 x86 SP1
Ole32.dll 5.2.3790.2572 1,247,232 17-Nov-2005 03:20 x86 SP1
Olecli32.dll 5.2.3790.2572 75,776 17-Nov-2005 03:20 Not Applicable SP1
Olecnv32.dll 5.2.3790.2572 38,912 17-Nov-2005 03:20 x86 SP1
Rpcss.dll 5.2.3790.2572 421,888 17-Nov-2005 03:20 x86 SP1
Stclient.dll 2001.12.4720.2572 64,000 17-Nov-2005 03:20 x86 SP1
Txflog.dll 2001.12.4720.2572 98,816 17-Nov-2005 03:20 x86 SP1


STATUS

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

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

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

http://support.microsoft.com 


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:

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


REFERENCES

For more information about TCP port usage when a client makes a DCOM call to a COM+ server application, click the following article number to view the article in the Microsoft Knowledge Base:

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


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Keywords: kbwinserv2003sp2fix kbqfe kbfix kbbug kbpubtypekc KB910695



Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.


Retrieved from ‘https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/910695&oldid=336307’
the Creative Commons 3.0 ShareAlike (except the Microsoft KB Archive).
Powered by MediaWiki