Microsoft KB Archive/925278

= FIX: A query may crash, and you may receive an error message when an MDX query uses the Filter function at the start to slice a partition in SQL Server 2005 Analysis Services: &quot;An unexpected exception occurred&quot; =

Article ID: 925278

Article Last Modified on 7/24/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Analysis Services

-



Bug: #1233 (SQL Hotfix)



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.



SUMMARY
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 after you apply the hotfix package
 * The files that are contained in the hotfix package



SYMPTOMS
When a Multidimensional Expressions (MDX) query uses the Filter function in SQL Server 2005 Analysis Services, the query may crash, and you may receive the following error message:

An unexpected exception occured

Note The word &quot;occurred&quot; is spelled incorrectly in the error message.

You experience this problem when you use the Filter function at the start to slice a partition. For example, the query may be as the following: SET SlicerAxisTuple AS ([Customer].[Default].DefaultMember, [Organization Unit].[Default].DefaultMember, filter([Business Plan].[Default].[Business Plan Segment], [Business Plan].[Default].Properties('Active', TYPED) = true), [Promotion].[Default].DefaultMember)



RESOLUTION
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
You must be running Microsoft SQL Server 2005 Service Pack 1 (SP1) to apply this hotfix.

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

SQL Server 2005, Itanium architecture version


WORKAROUND
To work around this problem, rewrite the query to use the filter function in the end. The new query may resemble the following: SET SlicerAxisTuple AS ([Customer].[Default].DefaultMember, [Organization Unit].[Default].DefaultMember, [Promotion].[Default].DefaultMember, filter([Business Plan].[Default].[Business Plan Segment], [Business Plan].[Default].Properties('Active', TYPED) = true))



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



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

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbsql2005as kbhotfixserver kbqfe kbpubtypekc KB925278

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.