SQL Server Errors or Failures Error: 1221 to Error: 1411

SQLServerF1

 

Error: 1221, Severity: 20,
The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. If the problem persists, contact your support provider.

Error: 1222, Severity: 16,
Lock request time out period exceeded.

Error: 1223, Severity: 16,
Cannot release the application lock (Database Principal: ‘%.*ls’, Resource: ‘%.*ls’) because it is not currently held.

Error: 1224, Severity: 16,
An invalid application lock resource was passed to %ls.

Error: 1225, Severity: 16,
An invalid application lock mode was passed to %ls.

Error: 1226, Severity: 16,
An invalid application lock owner was passed to %ls.

Error: 1227, Severity: 16,
An invalid application lock time-out was passed to %ls.

Error: 1228, Severity: 16,
An invalid parameter “%ls” was passed to the application lock function or procedure.

Error: 1230, Severity: 16,
An invalid database principal was passed to %ls.

Error: 1401, Severity: 21,
Startup of the database-mirroring master thread routine failed for the following reason: %ls. Correct the cause of this error, and restart the SQL Server service.

Error: 1402, Severity: 20,
Witness did not find an entry for database mirroring GUID {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. A configuration mismatch exists. Retry the command, or reset the witness from one of the database mirroring partners.

Error: 1403, Severity: 16,
The witness for the mirroring session received error response %d (state %d) from server instance %.*ls for database %.*ls. For more information about the error, refer to the error log on this server instance and the partner server instance.

Error: 1404, Severity: 16,
The command failed because the database mirror is busy. Reissue the command later.

Error: 1405, Severity: 16,
The database “%.*ls” is already enabled for database mirroring.

Error: 1406, Severity: 16,
Unable to force service safely. Remove database mirroring and recover database “%.*ls” to gain access.

Error: 1407, Severity: 16,
The remote copy of database “%.*ls” is not related to the local copy of the database.

Error: 1408, Severity: 16,
The remote copy of database “%.*ls” is not recovered far enough to enable database mirroring or to join it to the availability group. You need to apply missing log records to the remote database by restoring the current log backups from the principal/prim

Error: 1409, Severity: 16,
Database “%.*ls” requires database logs to be restored either on the future mirror database before you can enable database mirroring or on a secondary availability database before you can join it to the availability group. Restore current log backups from

Error: 1410, Severity: 16,
The remote copy of database “%.*ls” is already enabled for database mirroring.

Error: 1411, Severity: 16,
The remote copy of database “%.*ls” has not had enough log backups applied to roll forward all of its files to a common point in time.

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 *