Article ID: 906570 - View products that this article applies to.
After you apply Microsoft Windows Server 2003 Service Pack 1 (SP1) or install an x64-based version of Windows Server 2003, a custom program that uses the RegConnectRegistry function can no longer access the registry of a remote computer.
This problem may affect computers that are running Microsoft Systems Management Server (SMS) 2003. For example, a Windows Server 2003-based server that is running SMS 2003 may be unable to access the registry on a remote server. Additionally, the SMS 2003 server log file may contain an entry that is similar to the following: Note This problem only occurs when SMS 2003 is running in advanced security mode.
This problem occurs because the RegConnectRegistry function incorrectly uses the security context of the anonymous logon account to connect to the remote computer. The RegConnectRegistry function does not use the account that the function used before you installed Windows Server 2003 SP1.
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:
PrerequisitesTo apply this hotfix, you must have Windows Server 2003 SP1 installed on the computer.
Note If you are running an x64-based version of Windows Server 2003, Windows Server 2003 SP1 is already installed. You do not have to reinstall this service pack.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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.
Windows Server 2003, x86-based versions
Date Time Version Size File name ------------------------------------------------------------------ 25-Aug-2005 07:42 5.2.3790.2516 620,032 Advapi32.dll 05-Mar-2005 01:30 126.96.36.199 371,936 Updspapi.dll
Windows Server 2003, Itanium-based versions
Date Time Version Size File name Platform ------------------------------------------------------------------ 24-Aug-2005 21:14 5.2.3790.2516 1,483,264 Advapi32.dll IA-64 24-Aug-2005 21:14 5.2.3790.2516 620,032 Wadvapi32.dll x86 24-Aug-2005 21:14 188.8.131.52 639,712 Updspapi.dll IA-64
Windows Server 2003, x64-based versions
Date Time Version Size File name ------------------------------------------------------------------ 24-Aug-2005 21:14 5.2.3790.2516 1,051,136 Advapi32.dll 24-Aug-2005 21:14 5.2.3790.2516 620,032 Wadvapi32.dll 24-Aug-2005 21:14 184.108.40.206 462,560 Updspapi.dll
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 Windows Server 2003 Service Pack 2.
The problem that is mentioned in the "Symptoms" section allows the Kerberos protocol to be used with the Remote Registry service. After you install this hotfix, you may be able to use the Remote Registry service without using the NTLM authentication protocol. For more information about the terminology that is used in this article, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Technical support for x64-based versions of Microsoft WindowsYour hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your x64-based version of Windows. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.
For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:
http://www.microsoft.com/windowsxp/64bit/default.mspxFor product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:
Article ID: 906570 - Last Review: October 9, 2011 - Revision: 4.0