Select the product you need help with

FIX: Internal error when you run a MDX query that uses the Descendants function after you upgrade from SSAS 2005 to SSAS 2008, to SSAS 2008 R2 or to SSAS 2012

Article ID: 2605756 - View products that this article applies to.

Microsoft distributes Microsoft SQL Server 2008 Service Pack 2 (SP2) or Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 SP2 or SQL Server 2012 update release.

Back to the top | Give Feedback

Symptoms

Consider the following scenario:

You have a Multidimensional Expressions (MDX) query that uses the Descendants function.
You run the query successfully in Microsoft SQL Server 2005 Analysis Services (SSAS 2005) or in Microsoft SQL Server 2012 Analysis Services (SSAS 2012).
You upgrade from SSAS 2005 to Microsoft SQL Server 2008 Analysis Services (SSAS 2008) or to Microsoft SQL Server 2008 R2 Analysis Services (SSAS 2008 R2).
You try to run the query in SSAS 2008 or in SSAS 2008 R2.

In this scenario, the query fails. Additionally, you might receive the following error message:

Internal error: An unexpected exception occurred.

Back to the top | Give Feedback

Resolution

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 13. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:

2679366

(http://support.microsoft.com/kb/2679366/ )

Cumulative Update package 13 for SQL Server 2008 R2

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 2008 R2 fix release. We recommend 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:

981356

(http://support.microsoft.com/kb/981356/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2679368

(http://support.microsoft.com/kb/2679368/LN/ )

Cumulative update package 1 for SQL Server 2012

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 2012 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:

2692828

(http://support.microsoft.com/kb/2692828/LN/ )

The SQL Server 2012 builds that were released after SQL Server 2012 was released

You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 5 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2659694

(http://support.microsoft.com/kb/2659694/ )

Cumulative Update package 5 for SQL Server 2008 R2 Service Pack 1

2567616

(http://support.microsoft.com/kb/2567616/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2617146

(http://support.microsoft.com/kb/2617146/LN/ )

Cumulative update package 1 for SQL Server 2008 Service Pack 3

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 2008 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:

2629969

(http://support.microsoft.com/kb/2629969/LN/ )

The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Cumulative update package 6 for SQL Server 2008 SP2

The fix for this issue was first released in cumulative update package 6 for SQL Server 2008 SP2. For more information about how to obtain this cumulative update package for SQL Server 2008 SP2, click the following article number to view the article in the Microsoft Knowledge Base:

2582285

(http://support.microsoft.com/kb/2582285/ )

Cumulative update package 6 for SQL Server 2008 Service Pack 2

Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 SP2 update release. We recommend that you consider applying the most recent update release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2402659

(http://support.microsoft.com/kb/2402659/ )

The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

Back to the top | Give Feedback