EXECUTE statement failed because its WITH RESULT SETS clause specified %1!s! result set(s), and the statement tried to send more result sets than this.
Excluding object "{0}" which is referenced by articles in the specified publication from the current snapshot. The generated ...
EXECUTE AS SELF option is not supported in a data-tier application. Specify the principal name explicitly before rebuilding. ...
Execute call failed because the executable is already executing. This error occurs when the client calls Execute on a container ...
EXECUTE statement failed because its WITH RESULT SETS clause specified %1!s! column(s) for result set number %2!s!, but the ...
EXECUTE statement failed because its WITH RESULT SETS clause specified %1!s! result set(s), and the statement tried to send ...
EXECUTE statement failed because its WITH RESULT SETS clause specified %1!s! result set(s), but the statement only sent %2!s! ...
EXECUTE statement failed because its WITH RESULT SETS clause specified a non-nullable type for column #%1!s! in result set ...
EXECUTE statement failed because its WITH RESULT SETS clause specified type '%1!s!' for column #%2!s! in result set #%3!s!, ...
Execute the following statements at the Monitor to configure Log Shipping - for the database {0}].[{1}], - the script needs ...