Resolve miscellaneous issues after installing Anaplan XL.
Error when editing calculated members based on calculated sets
You may receive this error:
The selected calculation could not be executed: The 'NamedSetName' named set cannot be created because a set with the same name already exists. Please check the details and try again.
You may receive this error when using a named set in a calculated member created on a non-Measures hierarchy.
For example (based on Adventure Works):
Named Set 'MySet'
[Geography].[Geography].[Country].members
Calculated Member 'MyMember'
Aggregate([MySet])
Editing the above results in an error. This is because of a problem executing the necessary MDX with Analysis Services. You should instead ensure you set the solve order of the calculated member to 1 :
Named Set 'MySet'
[Geography].[Geography].[Country].members
Calculated Member 'MyMember'
Aggregate(StrToSet('[MySet]'))
In order to successfully create this once the error has been triggered, you will also have to rename the named set.
Searching in the Hierarchy Editor doesn't work
Selecting the Find Member button on the toolbar doesn't appear to do anything, even when matches are present.
This can happen if the cube doesn't support some of the functions required for case-insensitive searching. In this case, set the default Case Sensitivity to Use Database default on the Anaplan XL Options form.
Connection error when using PivotViews
The following error may be encountered when using PivotView connections (Grid connections based on Excel ranges and table-like data sources):
A connection cannot be made. Ensure that the server is running. Microsoft.AnalysisServices.AdomdClient.AdomdConnectionException: A connection cannot be made. Ensure that the server is running. ---> Microsoft.AnalysisServices.AdomdClient.XmlaStreamException: The 'C:\Users\USERNAME\AppData\Roaming\XLCubed Ltd\XLCubed Excel Edition\PivotViewCache\ID\ID.cub' local cube file cannot be opened. ---> System.ComponentModel.Win32Exception: The operation completed successfully
This indicates that the provider, Microsoft SQL Server 2012 Analysis Services 11.0 OLEDB, isn't installed or has been corrupted. To fix this:
