My first guess if it's only the server that's upgraded would be that you have gone from one of the older versions that didn't need }DimensionSecurity setting for alternate hierarchies. In the latest versions you will need to explicitly provide end users access to any hierarchy they will use.
So if it is an end-user (not an admin); previously working MDX could fail if it references a hierarchy that they don't have access to. And that can be resolved by simply providing access to the DimName:HierarchyName element in the }DimensionSecurity cube.
If Admin users are experiencing the same error then it will be something else (as admins automatically have access to all hierarchies and everything else).
Seeing the full MDX for the view would be useful here, but if memory serves you may not be able to access it when this error appears as closing it just leaves an empty widget. If that is the case are you still running a parallel server on the old version? Seeing the full MDX would very likely allow any errors to be noticed. There have been cases where incorrect MDX can actually still be resolved in older versions and then stops being resolved after an upgrade that becomes a bit stricter.
------------------------------
Declan Rodger
Technical Director
Spitfire Analytics
------------------------------
Original Message:
Sent: Thu February 23, 2023 08:39 AM
From: Asgeir Thorgeirsson
Subject: MDX error after upgrading TM1
Hi
We did upgraded the TM1 (local) to the latest version BA-PAL-2.0.9.15
We did not upgrade the PAW server yet. The current PAW version is BA-PAWL-2.0.72
Now I am experiencing MDX errors when opening some tabs in PAW books
Example:
"Unable to fetch data.
Syntax error at or near. 'ELSE END, ..."
Help, ...anyone?
Thanks, Asgeir

------------------------------
Asgeir Thorgeirsson
------------------------------