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 (916097)
The information in this article applies to:
- Microsoft SQL Server 2000 Analysis Services, when used with:
- Microsoft Windows Server 2003 SP1
Bug: #520 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2000 Analysis Services fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 Analysis Services fix release. SUMMARYThis 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
SYMPTOMSConsider 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. CAUSEThis 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 HKEY_LOCAL_MACHINE\SOFTWARE registry key on a 64-bit server. These registry read calls are redirected to the
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node registry subkey. Because this registry subkey does not exist,
the Properties dialog box in Analysis Manager displays blank values for most server
properties.RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 Analysis Services service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesTo 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 informationThis 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. |
Msdmbr.ocx | 8.0.0.2190 | 258,128 | 17-Mar-2006 | 13:25 | x86 | Msmdadin.dll | 8.0.0.2190 | 196,680 | 17-Mar-2006 | 13:25 | x86 | Msmdcb.ocx | 8.0.0.2190 | 909,394 | 17-Mar-2006 | 13:25 | x86 | Msmdctr80.dll | 8.0.2190.0 | 61,440 | 17-Mar-2006 | 13:25 | x86 | Msmddo80.dll | 8.0.0.2190 | 4,090,656 | 17-Mar-2006 | 13:27 | x86 | Msmdsgn.dll | 8.0.0.2190 | 6,344,704 | 17-Mar-2006 | 13:25 | x86 | Msmdsgn80.dll | 8.0.0.2190 | 9,650,249 | 17-Mar-2006 | 13:25 | x86 | Msmdsrv.exe | 8.0.2190.0 | 1,970,176 | 17-Mar-2006 | 03:14 | x86 | Msmdtsm.dll | 8.0.0.2190 | 446,550 | 17-Mar-2006 | 13:25 | x86 | Msmdtsp.dll | 8.0.0.2190 | 372,821 | 17-Mar-2006 | 13:25 | x86 | Msolap80.dll | 8.0.2190.0 | 2,120,408 | 17-Mar-2006 | 13:27 | x86 |
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbHotfixServer kbQFE kbpubtypekc KB916097 kbAudITPRO kbAudDeveloper |
---|
|