FIX: You may not be able to use Analysis Manager to change server properties for an instance of SQL Server 2000 Analysis Services that is running on an IA-64 server computer after you install Windows Server 2003 SP1 on a client computer

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for applying the hotfix package
• Information about whether you must restart the computer after you apply the hotfix package
• Information about whether the hotfix package is replaced by any other hotfix package
• Information about whether you must make any registry changes
• The files that are contained in the hotfix package

Consider the following scenario. You run 32-bit client applications for Microsoft SQL Server 2000 Analysis Services on a client computer that is running Microsoft Windows Server 2003. You install Microsoft Windows Server 2003 Service Pack 1 (SP1) on the client computer. In this scenario, you may not be able to use Analysis Manager to change server properties for an instance of SQL Server 2000 Analysis Services that is running on a 64-bit Itanium architecture-based (IA-64) server computer.

Additionally, if you try to restore an Analysis Services database against the IA-64 SQL Server 2000 Analysis Services server by using Analysis Manager on the 32-bit client, you may receive the following error message:

This problem occurs because of a behavioral change that was implemented for remote registry read calls in Windows Server 2003 SP1.

After you install Windows Server 2003 SP1 on a 32-bit client computer, any remote registry read calls that originate from a 32-bit application target the registry key on a 64-bit server. These registry read calls are redirected to the registry subkey. Because this registry subkey does not exist, the Properties dialog box in Analysis Manager displays blank values for most server properties.

A 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.

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, submit a request to 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: Note 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.

Prerequisites

To apply this hotfix, you must have SQL Server 2000 Analysis Services Service Pack 4 (SP4) installed on the computer.

Restart information

You may be prompted to restart the computer if the installer must replace files that are being used. To avoid a restart of the computer, close all SQL Server Analysis Services tools and clients before you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of 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 has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This hotfix tests for the presence of the registry key to determine the registry hive that should be used. If you have duplicated this key as a temporary workaround, the duplicate key may prevent the hotfix from working correctly. This hotfix is only required on 32-bit computers that are running Windows Server 2003 SP1 and are used to administer a 64-bit SQL Server 2000 Analysis Services server.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: