Message : Changes to the cube via a cube update has failed due to a deadlock. This is most likely because the cube was processing at the time of the update. This is an intermittent problem and will resolve on its own as the DWMaintenance jobs continue to run. However, to work around this issue, administrators can manually restart the DWMaintenance job when cubes are not processing. Message: %1 Stack trace: %2
Matched property {0} of class {1} in format file with class property name having different casing: {2}. Consider using exact ...
MemberModule ID={0}, TypeID={1} has the Stateful flag set to 'true'. ProbeActionModuleType cannot have a stateful ConditionDetection ...
Message : A Connection Exception was encountered while trying to connect to Analysis Server. Ensure the Analysis Server Service ...
Message : An Exception was encountered while trying to process a cube. Cube Name: %1 Exception Message: %2 Stack Trace: %3. ...
Message : Changes to the cube via a cube update has failed due to a deadlock. This is most likely because the cube was processing ...
Message : Cube %1 was not found and not returned from SDK Instance Space or Management Pack. Ensure that SDK services is ...
Message : Cube %1 was not initialized correctly and returned from the OlapCubeFactory. Check cube syntax to ensure cube is ...
Message : Cube Partitions were not managed in the DWMaintenance run for the cube %1. This is most likely because a cube was ...
Message : Cube Processing workitem has failed. This is most likely caused by the DWDataMart (primary datamart) being out ...