FIX: Some values of measures in a cube unexpectedly appear as "#N/A" when you enable the "Enable read-contingent permissions" option for the cube in SQL Server 2005 Analysis Services Service Pack 2

Article translations Article translations
Article ID: 936080 - View products that this article applies to.
Bug #: 50001126 (SQL Hotfix)
Expand all | Collapse all

On This Page

SYMPTOMS

In Microsoft SQL Server 2005 Analysis Services Service Pack 2 (SP2), you create a database role that has the following permissions:
  • You set the Read Definition database permission for the role.
  • You set the Read access permission to a cube.
  • You enable the Enable read-contingent permissions option for the cube.
  • You specify a Multidimensional Expressions (MDX) expression for the read-contingent permissions.
When you browse the cube under the security context of this role, some values of measures unexpectedly appear as #N/A. However, in SQL Server 2005 Analysis Services Service Pack 1 (SP1), these values are displayed as the values that are derived from these measures.

CAUSE

This problem occurs because of a regression that was introduced in SQL Server 2005 SP2.

RESOLUTION

Cumulative update information

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2
Note 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 2005 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:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 936080 - Last Review: June 21, 2007 - Revision: 1.3
APPLIES TO
  • Microsoft SQL Server 2005 Analysis Services
Keywords: 
kbpubtypekc kbqfe kbfix kbsql2005as kbexpertiseadvanced KB936080

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com