Select the product you need help with
FIX: Error message when you run an MDX query against a database in SQL Server 2005 Service Pack 2: “An unexpected exception occured”Article ID: 937829 - View products that this article applies to. VSTS bug number: 262045 On This PageSYMPTOMSWhen you run a Multidimensional Expressions (MDX) query against a database in SQL Server 2005 Analysis Services Service Pack 1 (SP1), the query takes a long time to finish. This problem occurs if the query contains one of the following calculation operators:
An unexpected exception occured. Additionally, minidump files are generated in the SQL Server 2005 Analysis Services log folder. CAUSEThis issue occurs because of a regression in SQL Server 2005 Analysis Services SP2. RESOLUTIONCumulative update informationThe fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:936305 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/936305/LN/
)
Cumulative update package 2 for SQL Server 2005 Service Pack 2937137 Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
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 the problem described in this article. 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=support 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, your computer must be running SQL Server 2005 Service Pack 2.Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.SQL Server 2005, x86-based versionsCollapse this table
SQL Server 2005, x64-based versionsCollapse this table
SQL Server 2005, IA-64-based versionsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 937829 - Last Review: October 8, 2011 - Revision: 3.0
|
Back to the top
