The context transaction which was active before entering user defined routine, trigger or aggregate "%1!s!" has been ended inside of it, which is not allowed. Change application logic to enforce strict transaction nesting.
The contents of the attribute with Id of '%{attributeId/}', Name of '%{attributeName/}' cannot be updated because the dimension ...
The contents of the file "%1!s!" are not consistent with a transition into the restore sequence. A restore from a backup ...
The Context object cannot be used since there is no available server context. This typically occurs because the AdomdServer ...
The context of the output column could not be retrieved. To add an output column, select either an output or another output ...
The context transaction which was active before entering user defined routine, trigger or aggregate "%1!s!" has been ended ...
The continuous content type cannot be determined due to the following problem: {0} You may manually change each mining structure ...
The continuous key column reference (KEY TIME, KEY SEQUENCE) is not supported in a SELECT DISTINCT statement at line %d{Line/}, ...
The conversation endpoint with conversation handle '%1!s!' is in an inconsistent state. Check the SQL Server error logs and ...
The conversation endpoint with ID '%1!s!' and is_initiator: %2!s! is referencing the invalid conversation handle '%3!s!'. ...