SQL Server Errors or Failures from Error: 40530 to Error: 40562

Error: 40530, Severity: 16, The %.*ls statement must be the only statement in the batch.

Error: 40531, Severity: 11, Server name cannot be determined. It must appear as the first segment of the server’s dns name (servername.%.*ls). Some libraries do not send the server name, in which case the server name must be included as part of the user name (username@servername).
Error: 40532, Severity: 11, Cannot open server “%.*ls” requested by the login. The login failed.
Error: 40533, Severity: 16, Server ‘%.*ls’ already exists.
Error: 40534, Severity: 16, A valid SID is already associated with the database owner.
Error: 40535, Severity: 16, Properties for schema scope ‘%.*ls’ already exist.

Error: 40537, Severity: 16, User ‘%.*ls’ not found in the database.
Error: 40541, Severity: 16, Procedure cannot be called from inside a partition.
Error: 40542, Severity: 16, Incorrect number of parameters specified for procedure.
Error: 40543, Severity: 16, Invalid %S_MSG name specified. Length should be between 1 and %d.
Error: 40544, Severity: 20, The database has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions. Incident ID: %ls. Code: %d
Error: 40545, Severity: 20, The service is experiencing a problem that is currently under investigation. Incident ID: %ls. Code: %d

Error: 40548, Severity: 16, Granting CONNECT permission to the guest user in database ‘%.*ls’ is not permitted.
Error: 40549, Severity: 16, Session is terminated because you have a long running transaction. Try shortening your transaction.
Error: 40550, Severity: 16, The session has been terminated because it has acquired too many locks. Try reading or modifying fewer rows in a single transaction.
Error: 40551, Severity: 16, The session has been terminated because of excessive TEMPDB usage. Try modifying your query to reduce temporary table space usage.
Error: 40552, Severity: 16, The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction.
Error: 40553, Severity: 16, The session has been terminated because of excessive memory usage. Try modifying your query to process fewer rows.
Error: 40561, Severity: 16, Database copy failed. Either the source or target database does not exist.
Error: 40562, Severity: 16, Database copy failed. The source database has been dropped.

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.