Symptoms
Consider the following scenario:
-
You run a Multidimensional Expressions (MDX) query against a cube in Microsoft SQL Server 2012 Analysis Services (SSAS 2012).
-
The MDX query has a sub-select clause that refers to some calculated measures.
In this scenario, you may receive the following error message:
The operation has been cancelled because there is not enough memory available for the application. If using a 32-bit version of the product, consider upgrading to the 64-bit version or increasing the amount of memory available on the machine.
Resolution
Cumulative update information
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 Cumulative update package 1 for SQL Server 2012Note 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 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.
Hotfix information
After you apply this hotfix, this issue can be resolved only when the sub-select clause refers to a Data Analysis Expressions (DAX) calculated measure. If it refers to a MDX measure, this issue still occurs. A 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 this specific problem. 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, submit a request to 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 website:
http://support.microsoft.com/contactus/?ws=supportNote 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.
Prerequisites
To apply this hotfix, you must have the Microsoft SQL Server 2012 Release Candidate 1 (RC1) installed.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
File information
The global 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.For all supported x86-based versions
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
msmdsrv.exe |
11.0.2002.46 |
45,350,752 |
04-Feb-2012 |
07:22 |
x86 |
|
Msmdlocal.dll |
11.0.2002.46 |
48,244,576 |
04-Feb-2012 |
07:15 |
x86 |
|
Msmgdsrv.dll |
11.0.2002.46 |
9,618,784 |
04-Feb-2012 |
07:12 |
x86 |
For all supported x64-based versions
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
msmdsrv.exe |
11.0.2002.46 |
61,530,464 |
04-Feb-2012 |
05:52 |
x64 |
|
Msmdlocal.dll |
11.0.2002.46 |
63,411,552 |
04-Feb-2012 |
05:43 |
x64 |
|
Msmgdsrv.dll |
11.0.2002.46 |
11,433,312 |
04-Feb-2012 |
05:39 |
x64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
