FIX: You may receive an error message when an invalid user tries to browse an Analysis Services cube that implements dynamic dimension security by defining a custom cube role

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package.
• The prerequisites for installing the hotfix package.
• Whether you must restart your computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix package.
• Whether you must make any registry changes.
• The files that are contained in the hotfix package.

If you create a custom cube role to define the dynamic dimension security to restrict the dimension members that are visible to users, and you then specify the top dimension level that can be accessed by the users in the custom cube role, you may receive one of the following error messages when you try to browse a cube by using the custom cube role:

Error message 1

Error message 2

This problem occurs when all the following conditions are true:

• The Multidimensional Expressions (MDX) expression that evaluates the topmost accessible level of the dimension uses the IsError function and the UserName function.
  
  An example is an MDX expression that is similar to the following that is used to specify the topmost accessible level of a dimension:
  
  Business Unit

  IIF(vba!IsError(StrToMember("[User].[" + UserName + "]")),[Business Unit].Levels(1),[Business Unit].Levels(2))

• The user who is trying to browse the cube does not exist in the Users dimension.

After you receive the error message, the custom cube role that you used to define the dynamic dimension security is corrupted. As a result, all the users who belong to the cube role will not be able to access the dimension until the dimension is rebuilt. Also, Analysis Manager may report the following error message:



For a list of previous hotfixes, see the "Microsoft SQL Server 2000 post-Service Pack 3 or Microsoft SQL Server 2000 post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article:

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

Prerequisites

This hotfix requires Microsoft SQL Server 2000 Analysis Services Service Pack 3 (SP3). For information about how to obtain SQL Server 2000 Analysis Services SP3, see the following article in the Microsoft Knowledge Base:

Restart information

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

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 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 tool in Control Panel.

SQL Server 2000 Analysis Services Service Pack 3

This hotfix build is designed for a server that is running Microsoft SQL Server 2000 Analysis Services Service Pack 3.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

For more information about dynamic dimension security, click the following article number to view the article in the Microsoft Knowledge Base: For more information about Analysis Services operations, visit the following Microsoft TechNet Web site and read the "Security Administration" section: For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the terminology that Microsoft uses when orrecting software after it is released, click the following article number to view the article in the Microsoft Knowledge Base: