Article ID: 908478 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
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:
(https://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
Consider the following scenario:
During the initial client request to populate the site hierarchy node, the server responds with the incorrect remote procedure call (RPC) port. Therefore, the data is never received by the client, and the site hierarchy node is empty. The problem occurs when the RPC port restriction is enabled by using the following registry subkey:
For more information about how to configure RPC port restrictions, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/154596/ )How to configure RPC dynamic port allocation to work with firewalls
To resolve this problem, obtain the latest service pack for Microsoft Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/889100/ )How to obtain the latest service pack for Windows Server 2003
Installation instructionsThe service pack must be installed on the server where the SMS WMI provider (Smsprov.dll) is installed. To determine which server hosts the SMS WMI provider, examine the Provider Location registry value under the following registry subkey on the SMS site server:
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 work around this problem, follows these steps:
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 Microsoft Windows Server 2003 Service Pack Service Pack 1.
Article ID: 908478 - Last Review: January 15, 2015 - Revision: 2.0