This article has been archived. It is offered "as is" and will no longer be updated.
If dimension security is defined for a role on an Analysis Services cube, and the cube contains a measure that uses the Distinct Count aggregation function, the role may return #ERR for the cell values when you browse the cube. If you click on the #ERR value in the Cube Browser from Analysis Manager, you receive the following error message:
Unable to display cell properties. The operation requested failed due to security problems - unknown error Store An error occurred during attempt to get a cell value.
This error occurs because the Visual Totals option is enabled for the role where dimension security is defined; however, you cannot use the Visual Totals option with Distinct Count measures. The Visual Totals option that is on the Common tab of the Custom Dimension Security dialog box will be greyed out. As a result, you cannot change the Visual Totals option. After you apply the hotfix, the Visual Totals option that is on the Common tab of the Custom Dimension Security dialog box is enabled, and you can use it to disable the Visual Totals options for the security role from within Analysis Manager.
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:
290211 How to obtain the latest SQL Server 2000 service pack
The English version of this fix 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 Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.