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

Article translations Article translations
Article ID: 910695 - View products that this article applies to.
Expand all | Collapse all

On This Page

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.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows


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.
    Collapse this tableExpand this table
    Value nameData typeValueNotes
    EnableEELoggingREG_DWORD1 This registry value enables or disables logging in text format. This format is appropriate for manual analysis of the logs.
    LogEEInfoAsNative REG_DWORD1This 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformService branch
Catsrv.dll2001.12.4720.445622,08017-Nov-200502:45IA-64Not Applicable
Catsrvut.dll2001.12.4720.4451,555,45617-Nov-200502:45IA-64Not Applicable
Clbcatex.dll2001.12.4720.445263,68017-Nov-200502:45IA-64Not Applicable
Clbcatq.dll2001.12.4720.4451,287,16817-Nov-200502:45IA-64Not Applicable
Colbact.dll2001.12.4720.445171,00817-Nov-200502:45IA-64Not Applicable
Comadmin.dll2001.12.4720.445411,13617-Nov-200502:45IA-64Not Applicable
Comrepl.dll2001.12.4720.445275,45617-Nov-200502:45IA-64Not Applicable
Comsvcs.dll2001.12.4720.4453,143,16817-Nov-200502:45IA-64Not Applicable
Comuid.dll2001.12.4720.4451,873,40817-Nov-200502:45IA-64Not Applicable
Es.dll2001.12.4720.445654,33617-Nov-200502:45IA-64Not Applicable
Msdtcprx.dll2001.12.4720.4451,311,74417-Nov-200502:45IA-64Not Applicable
Msdtctm.dll2001.12.4720.4453,152,38417-Nov-200502:45IA-64Not Applicable
Msdtcuiu.dll2001.12.4720.445463,36017-Nov-200502:45IA-64Not Applicable
Mtxclu.dll2001.12.4720.445203,77617-Nov-200502:45IA-64Not Applicable
Mtxdm.dll2001.12.4720.44545,56817-Nov-200502:45IA-64Not Applicable
Mtxoci.dll2001.12.4720.445320,00017-Nov-200502:45IA-64Not Applicable
Ole32.dll5.2.3790.4453,582,97617-Nov-200502:45IA-64Not Applicable
Olecli32.dll5.2.3790.445223,74417-Nov-200502:45IA-64Not Applicable
Olecnv32.dll5.2.3790.44589,08817-Nov-200502:45IA-64Not Applicable
Rpcproxy.dll5.2.3790.14173,21617-Nov-200502:45IA-64Not Applicable
Rpcrt4.dll5.2.3790.1412,150,40017-Nov-200502:45IA-64Not Applicable
Rpcss.dll5.2.3790.445694,27217-Nov-200502:45IA-64Not Applicable
Stclient.dll2001.12.4720.445140,80017-Nov-200502:45IA-64Not Applicable
Txflog.dll2001.12.4720.445280,06417-Nov-200502:45IA-64Not Applicable
Wcatsrv.dll2001.12.4720.445258,56017-Nov-200502:45x86WOW
Wcatsrvut.dll2001.12.4720.445584,19217-Nov-200502:45x86WOW
Wclbcatex.dll2001.12.4720.44598,30417-Nov-200502:45x86WOW
Wclbcatq.dll2001.12.4720.445490,49617-Nov-200502:45x86WOW
Wcolbact.dll2001.12.4720.44556,83217-Nov-200502:45x86WOW
Wcomadmin.dll2001.12.4720.445189,44017-Nov-200502:45x86WOW
Wcomsvcs.dll2001.12.4720.4451,209,34417-Nov-200502:45x86WOW
Wes.dll2001.12.4720.445226,81617-Nov-200502:45x86WOW
Wmsdtcprx.dll2001.12.4720.445445,95217-Nov-200502:45x86WOW
Wmsdtcuiu.dll2001.12.4720.445160,76817-Nov-200502:45x86WOW
Wmtxclu.dll2001.12.4720.44576,28817-Nov-200502:45x86WOW
Wmtxdm.dll2001.12.4720.44518,94417-Nov-200502:45x86WOW
Wmtxoci.dll2001.12.4720.445109,05617-Nov-200502:45x86WOW
Wole32.dll5.2.3790.4451,193,98417-Nov-200502:45x86WOW
Wolecli32.dll5.2.3790.44572,19217-Nov-200502:45x86WOW
Wolecnv32.dll5.2.3790.44536,35217-Nov-200502:45x86WOW
Wrpcproxy.dll5.2.3790.14126,11217-Nov-200502:45x86WOW
Wrpcrt4.dll5.2.3790.141544,25617-Nov-200502:45x86WOW
Wstclient.dll2001.12.4720.44560,41617-Nov-200502:45x86WOW
Wtxflog.dll2001.12.4720.44595,23217-Nov-200502:45x86WOW
Windows Server 2003 SP1, Itanium Architecture
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Catsrv.dll2001.12.4720.2572657,40817-Nov-200502:45IA-64SP1Not Applicable
Catsrvut.dll2001.12.4720.25721,632,25617-Nov-200502:45IA-64SP1Not Applicable
Clbcatex.dll2001.12.4720.2572279,04017-Nov-200502:45IA-64SP1Not Applicable
Clbcatq.dll2001.12.4720.25721,353,72817-Nov-200502:45IA-64SP1Not Applicable
Colbact.dll2001.12.4720.2572181,76017-Nov-200502:45IA-64SP1Not Applicable
Comadmin.dll2001.12.4720.2572420,35217-Nov-200502:45IA-64SP1Not Applicable
Comrepl.dll2001.12.4720.2572285,18417-Nov-200502:45IA-64SP1Not Applicable
Comsvcs.dll2001.12.4720.25723,366,91217-Nov-200502:45IA-64SP1Not Applicable
Comuid.dll2001.12.4720.25721,977,85617-Nov-200502:45IA-64SP1Not Applicable
Es.dll2001.12.4720.2572701,44017-Nov-200502:45IA-64SP1Not Applicable
Msdtcprx.dll2001.12.4720.25721,337,34417-Nov-200502:45IA-64SP1Not Applicable
Msdtctm.dll2001.12.4720.25723,096,06417-Nov-200502:45IA-64SP1Not Applicable
Msdtcuiu.dll2001.12.4720.2572486,40017-Nov-200502:45IA-64SP1Not Applicable
Mtxclu.dll2001.12.4720.2572207,87217-Nov-200502:45IA-64SP1Not Applicable
Mtxdm.dll2001.12.4720.257247,61617-Nov-200502:45IA-64SP1Not Applicable
Mtxoci.dll2001.12.4720.2572322,04817-Nov-200502:45IA-64SP1Not Applicable
Ole32.dll5.2.3790.25723,999,74417-Nov-200502:45IA-64SP1Not Applicable
Olecli32.dll5.2.3790.2572252,41617-Nov-200502:45IA-64SP1Not Applicable
Olecnv32.dll5.2.3790.257290,11217-Nov-200502:45IA-64SP1Not Applicable
Rpcss.dll5.2.3790.2572859,13617-Nov-200502:45IA-64SP1Not Applicable
Stclient.dll2001.12.4720.2572149,50417-Nov-200502:45IA-64SP1Not Applicable
Txflog.dll2001.12.4720.2572301,56817-Nov-200502:45IA-64SP1Not Applicable
Wcatsrv.dll2001.12.4720.2572273,92017-Nov-200502:45x86SP1WOW
Wcatsrvut.dll2001.12.4720.2572619,52017-Nov-200502:45x86SP1WOW
Wclbcatex.dll2001.12.4720.2572104,96017-Nov-200502:45x86SP1WOW
Wclbcatq.dll2001.12.4720.2572514,04817-Nov-200502:45x86SP1WOW
Wcolbact.dll2001.12.4720.257258,88017-Nov-200502:45x86SP1WOW
Wcomadmin.dll2001.12.4720.2572196,60817-Nov-200502:45x86SP1WOW
Wcomsvcs.dll2001.12.4720.25721,268,73617-Nov-200502:45x86SP1WOW
Wcomuid.dll2001.12.4720.2572596,48017-Nov-200502:45x86SP1WOW
Wes.dll2001.12.4720.2572238,59217-Nov-200502:45x86SP1WOW
Wmsdtcprx.dll2001.12.4720.2572470,52817-Nov-200502:45x86SP1WOW
Wmsdtcuiu.dll2001.12.4720.2572165,88817-Nov-200502:45x86SP1WOW
Wmtxclu.dll2001.12.4720.257278,84817-Nov-200502:45x86SP1WOW
Wmtxdm.dll2001.12.4720.257220,99217-Nov-200502:45x86SP1WOW
Wmtxoci.dll2001.12.4720.2572111,10417-Nov-200502:45x86SP1WOW
Wole32.dll5.2.3790.25721,247,23217-Nov-200502:45x86SP1WOW
Wolecli32.dll5.2.3790.257275,77617-Nov-200502:45Not ApplicableSP1WOW
Wolecnv32.dll5.2.3790.257238,91217-Nov-200502:45x86SP1WOW
Wstclient.dll2001.12.4720.257264,00017-Nov-200502:45x86SP1WOW
Wtxflog.dll2001.12.4720.257298,81617-Nov-200502:45x86SP1WOW
Windows Server 2003 SP1, x64
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Catsrv.dll2001.12.4720.2572418,30417-Nov-200502:45x64SP1Not Applicable
Catsrvut.dll2001.12.4720.25721,083,90417-Nov-200502:45x64SP1Not Applicable
Clbcatex.dll2001.12.4720.2572175,10417-Nov-200502:45x64SP1Not Applicable
Clbcatq.dll2001.12.4720.2572882,68817-Nov-200502:45x64SP1Not Applicable
Colbact.dll2001.12.4720.257297,28017-Nov-200502:45x64SP1Not Applicable
Comadmin.dll2001.12.4720.2572288,76817-Nov-200502:45x64SP1Not Applicable
Comrepl.dll2001.12.4720.2572188,92817-Nov-200502:45x64SP1Not Applicable
Comsvcs.dll2001.12.4720.25722,194,94417-Nov-200502:45x64SP1Not Applicable
Comuid.dll2001.12.4720.25721,478,14417-Nov-200502:45x64SP1Not Applicable
Es.dll2001.12.4720.2572365,56817-Nov-200502:45x64SP1Not Applicable
Msdtcprx.dll2001.12.4720.2572830,46417-Nov-200502:45x64SP1Not Applicable
Msdtctm.dll2001.12.4720.25722,073,08817-Nov-200502:45x64SP1Not Applicable
Msdtcuiu.dll2001.12.4720.2572291,32817-Nov-200502:45x64SP1Not Applicable
Mtxclu.dll2001.12.4720.2572144,89617-Nov-200502:45x64SP1Not Applicable
Mtxdm.dll2001.12.4720.257230,20817-Nov-200502:45x64SP1Not Applicable
Mtxoci.dll2001.12.4720.2572175,10417-Nov-200502:45x64SP1Not Applicable
Ole32.dll5.2.3790.25722,546,68817-Nov-200502:45x64SP1Not Applicable
Olecli32.dll5.2.3790.2572131,58417-Nov-200502:45x64SP1Not Applicable
Olecnv32.dll5.2.3790.257256,83217-Nov-200502:45x64SP1Not Applicable
Rpcss.dll5.2.3790.2572698,36817-Nov-200502:45x64SP1Not Applicable
Stclient.dll2001.12.4720.2572101,88817-Nov-200502:45x64SP1Not Applicable
Txflog.dll2001.12.4720.2572180,22417-Nov-200502:45x64SP1Not Applicable
Wcatsrv.dll2001.12.4720.2572273,92017-Nov-200502:45x86SP1WOW
Wcatsrvut.dll2001.12.4720.2572619,52017-Nov-200502:45x86SP1WOW
Wclbcatex.dll2001.12.4720.2572104,96017-Nov-200502:45x86SP1WOW
Wclbcatq.dll2001.12.4720.2572514,04817-Nov-200502:45x86SP1WOW
Wcolbact.dll2001.12.4720.257258,88017-Nov-200502:45x86SP1WOW
Wcomadmin.dll2001.12.4720.2572196,60817-Nov-200502:45x86SP1WOW
Wcomsvcs.dll2001.12.4720.25721,268,73617-Nov-200502:45x86SP1WOW
Wcomuid.dll2001.12.4720.2572596,48017-Nov-200502:45x86SP1WOW
Wes.dll2001.12.4720.2572238,59217-Nov-200502:45x86SP1WOW
Wmsdtcprx.dll2001.12.4720.2572470,52817-Nov-200502:45x86SP1WOW
Wmsdtcuiu.dll2001.12.4720.2572165,88817-Nov-200502:45x86SP1WOW
Wmtxclu.dll2001.12.4720.257278,84817-Nov-200502:45x86SP1WOW
Wmtxdm.dll2001.12.4720.257220,99217-Nov-200502:45x86SP1WOW
Wmtxoci.dll2001.12.4720.2572111,10417-Nov-200502:45x86SP1WOW
Wole32.dll5.2.3790.25721,247,23217-Nov-200502:45x86SP1WOW
Wolecli32.dll5.2.3790.257275,77617-Nov-200502:45Not ApplicableSP1WOW
Wolecnv32.dll5.2.3790.257238,91217-Nov-200502:45x86SP1WOW
Wstclient.dll2001.12.4720.257264,00017-Nov-200502:45x86SP1WOW
Wtxflog.dll2001.12.4720.257298,81617-Nov-200502:45x86SP1WOW
Windows Server 2003, x86
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Catsrv.dll2001.12.4720.445258,56017-Nov-200503:09
Catsrvut.dll2001.12.4720.445584,19217-Nov-200503:09
Clbcatex.dll2001.12.4720.44598,30417-Nov-200503:09
Clbcatq.dll2001.12.4720.445490,49617-Nov-200503:09
Colbact.dll2001.12.4720.44556,83217-Nov-200503:09
Comadmin.dll2001.12.4720.445189,44017-Nov-200503:09
Comrepl.dll2001.12.4720.44586,52817-Nov-200503:09
Comsvcs.dll2001.12.4720.4451,209,34417-Nov-200503:09
Comuid.dll2001.12.4720.445565,24817-Nov-200503:09
Es.dll2001.12.4720.445226,81617-Nov-200503:09
Msdtcprx.dll2001.12.4720.445445,95217-Nov-200503:09
Msdtctm.dll2001.12.4720.445965,12017-Nov-200503:09
Msdtcuiu.dll2001.12.4720.445160,76817-Nov-200503:09
Mtxclu.dll2001.12.4720.44576,28817-Nov-200503:09
Mtxdm.dll2001.12.4720.44518,94417-Nov-200503:09
Mtxoci.dll2001.12.4720.445109,05617-Nov-200503:09
Ole32.dll5.2.3790.4451,193,98417-Nov-200503:09
Olecli32.dll5.2.3790.44572,19217-Nov-200503:09
Olecnv32.dll5.2.3790.44536,35217-Nov-200503:09
Rpcproxy.dll5.2.3790.14126,11216-Mar-200403:17
Rpcrt4.dll5.2.3790.141659,96816-Mar-200403:17
Rpcss.dll5.2.3790.445296,96017-Nov-200503:09
Stclient.dll2001.12.4720.44560,41617-Nov-200503:09
Txflog.dll2001.12.4720.44595,23217-Nov-200503:09
Windows Server 2003 SP1, x86
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Catsrv.dll2001.12.4720.2572273,92017-Nov-200503:20x86SP1
Catsrvut.dll2001.12.4720.2572619,52017-Nov-200503:20x86SP1
Clbcatex.dll2001.12.4720.2572104,96017-Nov-200503:20x86SP1
Clbcatq.dll2001.12.4720.2572514,04817-Nov-200503:20x86SP1
Colbact.dll2001.12.4720.257258,88017-Nov-200503:20x86SP1
Comadmin.dll2001.12.4720.2572196,60817-Nov-200503:20x86SP1
Comrepl.dll2001.12.4720.257288,57617-Nov-200503:20x86SP1
Comsvcs.dll2001.12.4720.25721,268,73617-Nov-200503:20x86SP1
Comuid.dll2001.12.4720.2572596,48017-Nov-200503:20x86SP1
Es.dll2001.12.4720.2572238,59217-Nov-200503:20x86SP1
Msdtcprx.dll2001.12.4720.2572470,52817-Nov-200503:20x86SP1
Msdtctm.dll2001.12.4720.25721,009,66417-Nov-200503:20x86SP1
Msdtcuiu.dll2001.12.4720.2572165,88817-Nov-200503:20x86SP1
Mtxclu.dll2001.12.4720.257278,84817-Nov-200503:20x86SP1
Mtxdm.dll2001.12.4720.257220,99217-Nov-200503:20x86SP1
Mtxoci.dll2001.12.4720.2572111,10417-Nov-200503:20x86SP1
Ole32.dll5.2.3790.25721,247,23217-Nov-200503:20x86SP1
Olecli32.dll5.2.3790.257275,77617-Nov-200503:20Not ApplicableSP1
Olecnv32.dll5.2.3790.257238,91217-Nov-200503:20x86SP1
Rpcss.dll5.2.3790.2572421,88817-Nov-200503:20x86SP1
Stclient.dll2001.12.4720.257264,00017-Nov-200503:20x86SP1
Txflog.dll2001.12.4720.257298,81617-Nov-200503:20x86SP1

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

Properties

Article ID: 910695 - Last Review: September 28, 2011 - Revision: 9.0
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)
Keywords: 
kbwinserv2003sp2fix kbqfe kbfix kbbug KB910695

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com