Microsoft KB Archive/886835

= BUG: You receive an &quot;Unable to update role in cube&quot; error message, and Analysis Manager or a DSO application indicates incorrect permissions in SQL Server 2000 Analysis Services =

Article ID: 886835

Article Last Modified on 11/21/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Analysis Services

-



Bug #: 14398 (Plato7X)



SYMPTOMS
When you try to update the cube roles in Analysis Manager, and your custom dimension security uses a Multidimensional Expressions (MDX) expression syntax that is not valid, you receive an error message that is similar to the following:

Unable to update role in cube

Note In the error message,  is a placeholder for the name of your Analysis Services cube.

After you receive this error message, the permissions that are applied on a server that is running Microsoft SQL Server 2000 Analysis Services differ from the permissions that are indicated in the following:
 * The user interface of Analysis Manager
 * An Analysis Services custom application that uses Decision Support Objects (DSO)



CAUSE
When you try to update the cube roles, including the cube role that uses an MDX expression syntax that is not valid, Analysis Manager does not update all the cube roles on the Analysis server repository. However, on the Analysis server computer, Analysis Manager updates the cube roles that use a valid MDX expression syntax. Therefore, you may notice the behavior that is mentioned in the &quot;Symptoms&quot; section.



WORKAROUND
To work around this problem, in Analysis Manager, remove the cube roles that use an MDX expression syntax that is not valid. Then update the cube roles by using Analysis Manager.



If SQL Server 2000 Analysis Services updates the cube roles in only one location, your data may be exposed. Therefore, the behavior that is mentioned in the &quot;Symptoms&quot; section may let users who have restricted permissions to access the data. The behavior may also keep users who have valid permissions from accessing data on the cube.



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

