BUG: DCOMCNFG Writes Ports Named Value in Incorrect Format

Article translations Article translations
Article ID: 201911 - View products that this article applies to.
This article was previously published under Q201911
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page


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


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

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.


Article ID: 201911 - Last Review: October 26, 2013 - Revision: 3.0
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 95
kbnosurvey kbarchive kbbug KB201911

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