SQL Server Errors or Failures Error: 1125 to Error: 1220

SQLServerF1

 

Error: 1125, Severity: 14,
Table error: Page %S_PGID. Test (%ls) failed. Slot %d, row extends into free space at 0x%x.

Error: 1126, Severity: 14,
Table error: Page %S_PGID. Test (%ls) failed. Slot %d, offset 0x%x overlaps with the prior row.

Error: 1127, Severity: 14,
Table error: Page %S_PGID. Test (%ls) failed. Values are %ld and %ld.

Error: 1128, Severity: 14,
Table error: Page (%d:%d), row %d. Test (%.*ls) failed. Values are %ld and %ld.

Error: 1129, Severity: 16,
Could not cleanup deferred deallocations from filegroup ‘%.*ls’.

Error: 1130, Severity: 10,
Error while allocating extent for a worktable. Extent %S_PGID in TEMPDB may have been lost.

Error: 1131, Severity: 10,
Failed to truncate AppendOnlyStorageUnit 0x%p. Will retry next time. This is an informational message only. No user action is required.

Error: 1202, Severity: 16,
The database-principal ‘%.*ls’ does not exist or user is not a member.

Error: 1203, Severity: 20,
Process ID %d attempted to unlock a resource it does not own: %.*ls. Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.

Error: 1204, Severity: 19,
The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for

Error: 1205, Severity: 13,
Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Error: 1206, Severity: 18,
The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.

Error: 1207, Severity: 10,
Can’t allocate %u locks on startup, reverting to %u and turning on dynamic lock allocation. Maximum allowed memory usage at startup is %I64u KB.

Error: 1208, Severity: 21,
Could not allocate initial %u lock blocks during startup. Can not start the server.

Error: 1209, Severity: 21,
Could not allocate initial %u lock owner blocks during startup. Can not start the server.

Error: 1210, Severity: 21,
Unable to allocate lock owner block during lock migration. Server halted.

Error: 1212, Severity: 10,
Lock not logged: %-30ls Mode: %s

Error: 1213, Severity: 21,
Error spawning Lock Monitor thread: %ls

Error: 1214, Severity: 17,
Internal Error. There are too many parallel transactions.

Error: 1220, Severity: 17,
No more lock classes available from transaction.

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.

 

SQL Server Errors or Failures Error: 1087 to Error: 1124

SQLServerF1

 

Error: 1087, Severity: 15,
Must declare the table variable “%.*ls”.

Error: 1088, Severity: 15,
Cannot find the object “%.*ls” because it does not exist or you do not have permissions.

Error: 1089, Severity: 15,
The SET FMTONLY OFF statement must be the last statement in the batch.

Error: 1090, Severity: 15,
Invalid default for parameter %d.

Error: 1091, Severity: 15,
The option “%ls” is not valid for this function.

Error: 1092, Severity: 16,
In this context %d statistics name(s) cannot be specified for option ‘%ls’.

Error: 1093, Severity: 16,
%.*ls is not a valid broker name.

Error: 1094, Severity: 15,
Cannot specify a schema name as a prefix to the trigger name for database and server level triggers.

Error: 1095, Severity: 15,
%.*ls has already been specified as an event type.

Error: 1096, Severity: 15,
Default parameter values for CLR types, nvarchar(max), varbinary(max), and xml are not supported.

Error: 1097, Severity: 15,
Cannot use If UPDATE within this CREATE TRIGGER statement.

Error: 1098, Severity: 15,
The specified event type(s) is/are not valid on the specified target object.

Error: 1099, Severity: 15,
The ON clause is not valid for this statement.

Error: 1101, Severity: 17,
Could not allocate a new page for database ‘%.*ls’ because of insufficient disk space in filegroup ‘%.*ls’. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing fi

Error: 1105, Severity: 17,
Could not allocate space for object ‘%.*ls’%.*ls in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on

Error: 1119, Severity: 16,
Removing IAM page %S_PGID failed because someone else is using the object that this IAM page belongs to.

Error: 1121, Severity: 17,
Space allocator cannot allocate page in database %d.

Error: 1122, Severity: 14,
Table error: Page %S_PGID. Test (%ls) failed. Address 0x%x is not aligned.

Error: 1123, Severity: 14,
Table error: Page %S_PGID. Unexpected page type %d.

Error: 1124, Severity: 14,
Table error: Page %S_PGID. Test (%ls) failed. Slot %d, offset 0x%x is invalid.

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.