SQL Server Errors or Failures Error: 556 to Error: 577

SQLServerF1

 

Error: 556, Severity: 16,
INSERT EXEC failed because the stored procedure altered the schema of the target table.

Error: 557, Severity: 16,
Only functions and some extended stored procedures can be executed from within a function.

Error: 558, Severity: 16,
Remote function calls are not allowed within a function.

Error: 561, Severity: 16,
Failed to access file ‘%.*ls’

Error: 562, Severity: 16,
Failed to access file ‘%.*ls’. Files can be accessed only through shares

Error: 563, Severity: 14,
The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated.

Error: 564, Severity: 16,
Attempted to create a record with a fixed length of ‘%d’. Maximum allowable fixed length is ‘%d’.

Error: 565, Severity: 18,
A stack overflow occurred in the server while compiling the query. Please simplify the query.

Error: 566, Severity: 21,
An error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by starting the server at the command p

Error: 567, Severity: 16,
File ‘%.*ls’ is not a recognizable trace file.

Error: 568, Severity: 16,
Encountered an error or an unexpected end of trace file ‘%.*ls’.

Error: 569, Severity: 16,
The handle that was passed to %ls was invalid.

Error: 570, Severity: 15,
INSTEAD OF triggers do not support direct recursion. The trigger execution failed.

Error: 571, Severity: 16,
The specified attribute value for %ls is invalid.

Error: 572, Severity: 16,
Invalid regular expression “%.*ls” near the offset %d.

Error: 573, Severity: 16,
Evaluation of the regular expression is too complex: ‘%.*ls’.

Error: 574, Severity: 16,
%ls statement cannot be used inside a user transaction.

Error: 575, Severity: 16,
A LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets.

Error: 576, Severity: 16,
Cannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d.

Error: 577, Severity: 16,
The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *