The conversation endpoint with conversation handle '%1!s!' is in an inconsistent state. Check the SQL Server error logs and the Windows event logs for information on possible hardware problems. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data.
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!'. ...
The conversation endpoint with ID '%1!s!' and is_initiator: %2!s! is referencing the missing service contract with ID %3!s!. ...
The conversation with ID '%1!s!' and initiator: %2!s! references a missing conversation group '%3!s!'. Run DBCC CHECKDB to ...
The conversion of the result of the expression"%1!s!" from type "%2!s!" to a supported type failed with error code 3!8.8X!. ...