BUG: DCOMCNFG Writes Ports Named Value in Incorrect Format
This article was previously published under Q201911
This article has been archived. It is offered "as is" and will no longer be updated.
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.
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
- Run the DCOMCNFG and click the Default Protocol tab.
- Select the protocol, and add a port range to it.
- Check the registry entry. You will see an incorrect port range format.
Article ID: 201911 - Last Review: 10/26/2013 06:37:00 - Revision: 3.0
Microsoft COM+ 2.0 Standard Edition
- kbnosurvey kbarchive kbbug KB201911