Microsoft KB Archive/201911

= BUG: DCOMCNFG Writes Ports Named Value in Incorrect Format =

Article ID: 201911

Article Last Modified on 12/17/2004

-

APPLIES TO

 Microsoft COM+ 2.0 Standard Edition, when used with:  Microsoft Windows NT Server 4.0 Standard Edition

 Microsoft Windows NT Workstation 4.0 Developer Edition

 Microsoft Windows 98 Standard Edition

 Microsoft Windows 95</li></ul> </li></ul>

-

<div class="notice_section">

This article was previously published under Q201911

<div class="symptoms_section">

SYMPTOMS
The DCOMCNFG utility writes the port range specified for a protocol in a incorrect format.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

<div class="moreinformation_section">

MORE INFORMATION
When a port range is specified for a protocol, such as 4000-4010, the value that is written to the registry key HKLM\SOFTWARE\Microsoft\RPC\Internet\Ports (named REG_MULTI_SZ) is "4000 - 4010." A space is added preceding and succeeding the "-". Remote Procedure Call (RPC) is extremly sensitive about the string format and fails the RpcServerUsePortSeq call with RPC_S_OUT_OF_RESOURCES. As a result, no client can talk to the server, and services such as Internet Information Server (IIS) do not start.

Steps to Reproduce Behavior

 * 1) Run the DCOMCNFG and click the Default Protocol tab.
 * 2) Select the protocol, and add a port range to it.
 * 3) Check the registry entry. You will see an incorrect port range format.

Keywords: kbbug KB201911

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.