Microsoft KB Archive/883485

= FIX: Incorrect Multidimensional Expressions (MDX) expressions are generated in the Custom Security Dimension dialog box if you choose the ragged dimension members that has hidden parent members =

Article ID: 883485

Article Last Modified on 2/13/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Analysis Services

-



Bug #: 14408 (Plato7x)

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
When one or more dimensions in your Microsoft SQL Server 2000 Analysis Services cube support ragged hierarchies and then you try to create a cube role to define custom dimension security to restrict the members of the ragged dimension that are visible to users, you may not be able to create the cube role successfully.

This problem occurs when all the following conditions are true:
 * You create a custom rule for dimension security by selecting the dimension members from the dimension member tree under the Members section in the Basic tab of the Custom Dimension Security :  dialog box.
 * The dimension members that you select are the ragged dimension members that have hidden parent members.

You may notice that the Multidimensional Expressions (MDX) expressions that are automatically generated in the Allowed Members box and the Denied Members box in the Advanced tab of the Custom Dimension Security :  dialog box are not correct.

Additionally, you may receive the following error message:

Unable to update role in cube.

Error occurred during update of Cube  on the server: 'Error occurred while processing security for cube ' ' (Error in the definition of the dimension security for the dimension ' ' and role ' '. Cannot evaluate the expression

Note In this error message,  is a placeholder for the name of your Analysis Services cube,   is a placeholder for the name of your Analysis Services ragged dimension,   is a placeholder for the name of the cube role that you are trying to create with custom dimension security, and   is a placeholder for the incorrect MDX expression that is generated in the Custom Dimension Security :   dialog box.



CAUSE
To retrieve the dimension members and to display the dimension member tree in the Members box, the Custom Dimension Security dialog box connects to the Analysis Manager with the MDX Compatibility connection property set to 2. Therefore, hidden dimension members are not displayed in the dimension member tree. Because the MDX Compatibility connection property also affects the unique representation of the dimension member names, the format that is used by the Custom Dimension Security dialog box to generate the dimension member names is different from the format that is used by the Analysis Services server. Therefore, Analysis Services server cannot evaluate the custom dimension security definition successfully and you receive the error message that is mentioned in the &quot;Symptoms&quot; section.



Prerequisites
This hotfix requires Microsoft SQL Server 2000 Analysis Services Service Pack 3 (SP3).

Restart information
You do not have to restart your computer after you apply this hotfix.

Registry information
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

After you apply this hotfix, a new String registry value  is created in the following registry key:

The  registry value helps the Analysis Manager control the values of the MDX Compatibility connection property and the Member Names Unique dimension member property.

You can use the following values for the  registry value:
 * True
 * False

Note After you change the registry settings, you must close and then reopen the Custom Dimension Security dialog box for the change in the registry settings to take effect.

File information
A 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 SQL Server 2000 Analysis Services 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:

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

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.

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.

Note This hotfix build is designed to be applied on a server that is running SQL Server 2000 Analysis Services Service Pack 3:   Date         Time   Version    Size       File name ---  06-Apr-2004  07:56                18,800  Msmd.h   06-Aug-2004  11:36  8.0.968.0    221,760  Msmdcb80.dll 06-Aug-2004 11:36  8.0.0.968  4,063,808  Msmddo80.dll 06-Aug-2004 11:36  8.0.968.0  1,036,864  Msmdgd80.dll 06-Aug-2004 11:36  8.0.968.0    172,608  Msmdpump.dll 06-Aug-2004 10:47  8.0.968.0    446,524  Msmdsgn.rll 06-Aug-2004 11:36  8.0.0.968  9,642,564  Msmdsgn80.dll 06-Aug-2004 11:36  8.0.968.0  1,843,780  Msmdsrv.exe 06-Aug-2004 11:36  8.0.968.0  2,089,552  Msolap80.dll 06-Aug-2004 10:23  8.0.968.0    213,068  Msolap80.rll Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.



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

