Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: A DCOM static TCP endpoint is ignored when you configure the endpoint for WMI on a Windows Server 2003-based computer
Article ID: 897571 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure that you 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:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Consider the following scenario. You use the Microsoft Windows Management Instrumentation (WMI) DCOM application to configure a DCOM static TCP endpoint for WMI on a computer that is running Microsoft Windows Server 2003. When you do this, the static endpoint is ignored. This problem occurs when you connect to the remote computer through a firewall.
Note This problem does not occur on a computer that is running Microsoft Windows 2000.
This problem occurs because the Winmgmt.exe process runs in an Svchost.exe instance. The Winmgmt service must run in a separate Svchost.exe process in order to listen on a static endpoint.
Service pack informationTo 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:
(http://support.microsoft.com/kb/889100/ )How to obtain the latest service pack for Windows Server 2003
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo resolve this problem, you must have Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 installed on the computer in addition to the hotfix that is mentioned in this article. For more information about how to obtain Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/897667/ )Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6
PrerequisitesFor Windows Server 2003 SP2 and later versions, it is not required to install the Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6.
Restart informationYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix is not replaced by any later hotfix.
Registry informationYou must create registry keys to apply the hotfixes that are contained in this package.
File informationThis hotfix contains only those files that you must have to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
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.
Microsoft Windows Server 2003, Itanium architecture
Date Time Version Size File name Platform ---------------------------------------------------------------- 21-Apr-2005 08:15 5.2.3790.314 34,304 Svchost.exe IA-64 21-Apr-2005 08:15 5.2.3790.314 13,312 Wsvchost.exe x86
Microsoft Windows Server 2003, x64
Date Time Version Size File name ------------------------------------------------------- 21-Apr-2005 08:15 5.2.3790.2426 25,600 Svchost.exe 21-Apr-2005 08:15 5.2.3790.2426 14,848 Wsvchost.exe
Microsoft Windows Server 2003, x86
Date Time Version Size File name ------------------------------------------------------ 21-Apr-2005 06:52 5.2.3790.314 13,312 Svchost.exe
Installation informationWarning 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 the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To resolve this problem, follow these steps:
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows Server 2003 Service Pack 2.
Article ID: 897571 - Last Review: March 21, 2008 - Revision: 5.2