FIX: Error message when you run a MDX query after you install the cumulative hotfix package for SQL Server 2005 Analysis Services for Itanium-based operating systems (build 9.0.2153): "Internal error: An unexpected exception occured" (923304)
The information in this article applies to:
- Microsoft SQL Server 2005 Analysis Services
Bug: #1036 (SQL Hotfix) Bug #: 434767 (SQLBUDT) SQL BU Defect Tracking:434767 Microsoft distributes Microsoft SQL Server 2005 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 2005 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 after you apply the
hotfix package
- The files that are contained in the hotfix
package
SYMPTOMSConsider the following scenario. You install the cumulative hotfix package for SQL Server 2005 Analysis Services for Itanium-based operating systems (build 9.0.2153). Then, you run a Multidimensional Expressions (MDX) query against an Analysis Services database. In this scenario, you may receive the following error message: Executing the query ... Internal error: An unexpected exception occured. Execution complete Note The word "occurred" is spelled incorrectly in the error message. 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 Microsoft SQL Server 2005 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 2005 SP1 installed on the computer.
For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
913089
How to obtain the latest service pack for SQL Server 2005
Restart information You do not have to restart the computer after you apply the 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.SQL Server 2005 Analysis Services, Itanium architecture version |
Cu.datawarehouse.dll | 9.0.2176.0 | 1,276,704 | 24-Jul-2006 | 23:22 | x86 | Microsoft.analysisservices.adomdclient.dll | 9.0.2176.0 | 543,520 | 24-Jul-2006 | 23:20 | x86 | Microsoft.analysisservices.deployengine.dll | 9.0.2176.0 | 138,016 | 24-Jul-2006 | 23:19 | x86 | Microsoft.analysisservices.dll | 9.0.2176.0 | 1,215,264 | 24-Jul-2006 | 23:22 | x86 | Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2176.0 | 163,104 | 24-Jul-2006 | 23:14 | IA-64 | Microsoft.sqlserver.sqlenum.dll | 9.0.2176.0 | 875,296 | 24-Jul-2006 | 23:15 | x86 | Ms.ss.mgdsqldumper.dll | 2005.90.2176.0 | 75,552 | 24-Jul-2006 | 23:18 | x86 | Msadomdx.dll | 9.0.2176.0 | 502,560 | 24-Jul-2006 | 23:20 | x86 | Msmdlocal.dll | 9.0.2176.0 | 48,778,016 | 24-Jul-2006 | 23:16 | IA-64 | Msmdredir.dll | 9.0.2176.0 | 6,155,040 | 24-Jul-2006 | 23:16 | IA-64 | Msmdsrv.exe | 9.0.2176.0 | 47,735,072 | 24-Jul-2006 | 23:16 | IA-64 | Msmgdsrv.dll | 9.0.2176.0 | 12,909,856 | 24-Jul-2006 | 23:16 | IA-64 | Msolap90.dll | 9.0.2176.0 | 7,771,424 | 24-Jul-2006 | 23:16 | IA-64 |
WORKAROUNDTo work around this problem, locate the following line of code in the Msmdsrv.ini file: <HandleIA64AlignmentFaults>0</HandleIA64AlignmentFaults> Replace this line of code with the following line of code: <HandleIA64AlignmentFaults>1</HandleIA64AlignmentFaults> Note The Msmdsrv.ini file is in the following folder: %ProgramFiles%\Microsoft SQL Server\MSSQL.X\OLAP\Config Note MSSQL.X represents the corresponding value for the system. To determine the corresponding value for the system, see the value of the MSSQLSERVER registry entry or the named instance registry entry under the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\OLAP STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 9/5/2006 |
---|
Keywords: | kbsql2005bi kbsql2005as kbQFE kbhotfixserver kbpubtypekc KB923304 kbAudDeveloper kbAudITPRO |
---|
|