Symptoms
Consider the following scenario:
-
You implement row-level security as dynamic security in a model project in a Microsoft SQL Server 2012 Analysis Services (SSAS 2012) instance that is running in tabular mode.
-
You use an effective username or a client application to perform role testing, and then you run a Multidimensional Expressions (MDX) query in the SSAS 2012 instance. Note You are a member of the Administrators group in the SSAS 2012 instance.
-
The query is canceled because of valid errors (for example, a time-out error occurs, or the user cancels the operation).
-
You run another MDX query.
In this scenario, you receive one of the following error messages:
An error was encountered during the evaluation of the row level security expression. Role: RoleName. User: 'Domain\UserName'. Table: TableName. Error message: The operation was cancelled by the user.
An error was encountered during the evaluation of the row level security expression. Role: RoleName. User: 'Domain\UserName'. Table: TableName. Error message: The session was cancelled because it exceeded a timeout setting (session orphaned timeout or session idle timeout) or it exceeded the session memory limit.
Resolution
Cumulative update information
Cumulative Update 2 for SQL Server 2012 SP1
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 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2790947 Cumulative update package 2 for SQL Server 2012 Service Pack 1Note 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 2012 SP1 fix release. We recommend 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:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Cumulative update 5 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2777772 Cumulative update 5 for SQL Server 2012Note 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 2012 fix release. We recommend 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
