Slicing for SSAS-based Reports Fails With SQLServer CU13 Update

[fifofonix]

Any advice on version incompatabilities between ReportServer and SQLServer/SSAS?

We are seeing report failures on slice events following a SQLServer upgrade but can't find this reported elsewhere.

More specifics on version info and details of error follow.

This is occuring in an on premises ReportServer installation (March 2018 - 1.4.6969.7395 test environemnt) but also (Jan 2019 -1.4.6969.7395 in our dev environment).  When we upgrade from SQLServer 14.0.2002 to SQLServer 14.0.30484 CU13 we see slice failures on our reports with a "Can't display the visual." error (see screenshot for detals of error).  This error can be reproduced easily at will on small SSAS cubes using a single table.

When running SQLServer Profiler for SSAS we do see an Exception of the following form.  Not being experts in the query language for SSAS cubes it is unclear to us what is wrong here, and what the incompatibility arises from.  Any help appreciated.

An unexpected exception occurred.

Query Text:
DEFINE VAR __DS0FilterTable =
TREATAS({"JohnDoe"}, 'RFID_TAG_NAME'[last_name])

EVALUATE
TOPN(
501,
CALCULATETABLE(
DISTINCT('RFID_TAG_NAME'[last_name]),
KEEPFILTERS(__DS0FilterTable)
),
'RFID_TAG_NAME'[last_name],
1
)

ORDER BY
'RFID_TAG_NAME'[last_name]

[fifofonix · Accepted solution]

Self-closing this item.  I guess this is a case of RTFM.  The Microsoft release notes do actually reference this regression and issue:

https://support.microsoft.com/en-us/help/4466404/cumulative-update-13-for-sql-server-2017

So, if you're thinking about CU13 and you use SSAS via PowerBI then think again...