Assume that you have Microsoft SQL Server Analysis Services (SSAS) installed on SQL Server 2017, and a role is defined with a secured column. If a measure with the name Calculated Measure Name references that secured column and a user who belongs to that role runs a query that references Calculated Measure Name, the user may receive an error message that resembles the following:

MdxScript(model) (LineNumber,ColumnNumber) Calculation error in measure 'CalculatedmeasureName' : Column 'ColumnName' cannot be found or may not be used in this expression.

The user should instead receive an error message that states that the measure does not exist. Because the column is secured, the measure should also be automatically secured, and the user should not receive any indication in the error that the measure is a valid measure.


This issue is fixed in the following cumulative update for SQL Server:

       Cumulative Update 7 for SQL Server 2017

Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were included in the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2017


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


Learn about the terminologythat Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!