Skip Navigation Links
Home
Articles
SQL Server 2012
SQL Server 2014
SQL Server 2016
FAQ
Practice Test
Tip of the Day : How to Create a Comma-Delimited List Without Using a Cursor
Error Messages
Home > Tips & Tricks > Error Messages 9001 to 12000
SQL Server Error Messages - Errors 9001 to 12000

A message number uniquely identifies each error message and the error message text describes the problem.  The error message text often includes placeholders for information (such as object names) to be inserted in the error message when it is displayed.  Unfortunately, the error message text does not tell you how to solve or work around the problem.  In this series of Error Messages list, we will try to provide you with ways on how to overcome or work around certain error messages.

Some error messages are self-explanatory and can easily be fixed, such as "Invalid object name".  Others are harder to fix or work around, especially by those who are new to SQL Server.  It is the intent of this page and succeeding pages (to come) to assist you in addressing or working around SQL Server error messages.

Error Severity Description
9001 10 The log for database '<Database Name>' is not available.
9002 19 The log file for database '<Database Name>' is full. Back up the transaction log for the database to free up some log space.
9003 20 The LSN <LSN Number> passed to log scan in database '<Database Name>' is invalid.
9004 21 An error occurred while processing the log for database '<Database Name>'.
9005 16 Either start LSN or end LSN specified in OpenRowset(DBLog, ...) is invalid.
9006 10 Cannot shrink log file <Log File Name> (%s) because total number of logical log files cannot be fewer than %d.
9007 10 Cannot shrink log file <Log File Name> (%s) because requested size (%dKB) is larger than the start of the last logical log file.
9008 10 Cannot shrink log file <Log File Name> (%s) because all logical log files are in use.
9009 10 Cannot shrink log file <Log File Name> (%s) because of minimum log space required.
9010 14 User does not have permission to query the virtual table, DBLog. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission.
10000 16 Unknown provider error.
10001 16 The provider reported an unexpected catastrophic failure.
10002 16 The provider did not implement the functionality.
10003 16 The provider ran out of memory.
10004 16 One or more arguments were reported invalid by the provider.
10005 16 The provider did not support an interface.
10006 16 The provider indicated an invalid pointer was used.
10007 16 The provider indicated an invalid handle was used.
10008 16 The provider terminated the operation.
10009 16 The provider did not give any information about the error.
10010 16 The data necessary to complete this operation was not yet available to the provider.
10011 16 Access denied.
10021 16 Execution terminated by the provider because a resource limit was reached.
10022 16 The provider called a method from IRowsetNotify in the consumer, and the method has not yet returned.
10023 16 The provider does not support the necessary method.
10024 16 The provider indicates that the user did not have the permission to perform the operation.
10025 16 Provider caused a server fault in an external process.
10026 16 No command text was set.
10027 16 Command was not prepared.
10028 16 Authentication failed.
10031 16 An error occurred because one or more properties could not be set.
10032 16 Cannot return multiple result sets (not supported by the provider).
10033 16 The specified index does not exist or the provider does not support an index scan on this data source.
10034 16 The specified table does not exist.
10035 16 No value was given for one or more of the required parameters.
10041 16 Could not set any property values.
10042 16 Cannot set any properties while there is an open rowset.
10051 16 An error occurred while setting the data.
10052 16 The insertion was canceled by the provider during notification.
10053 16 Could not convert the data value due to reasons other than sign mismatch or overflow.
10054 16 The data value for one or more columns overflowed the type used by the provider.
10055 16 The data violated the integrity constraints for one or more columns.
10056 16 The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
10057 16 Cannot create the row. Would exceed the total number of active rows supported by the rowset.
10058 16 The consumer cannot insert a new row before releasing previously-retrieved row handles.
10061 16 An error occurred while setting data for one or more columns.
10062 16 The change was canceled by the provider during notification.
10063 16 Could not convert the data value due to reasons other than sign mismatch or overflow.
10064 16 The data value for one or more columns overflowed the type used by the provider.
10065 16 The data violated the integrity constraints for one or more columns.
10066 16 The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
10067 16 The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
10068 16 The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source.
10069 16 The consumer could not delete the row. The insertion has been transmitted to the data source.
10075 16 An error occurred while deleting the row.
10081 16 The rowset uses integrated indexes and there is no current index.
10085 16 RestartPosition on the table was canceled during notification.
10086 16 The table was built over a live data stream and the position cannot be restarted.
10087 16 The provider did not release some of the existing rows.
10088 16 The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command to reposition the next fetch position to its initial position, and the order of the columns changed.

Error Severity Description
11000 16 Unknown status code for this column.
11001 16 Non-NULL value successfully returned.
11002 16 Deferred accessor validation occurred. Invalid binding for this column.
11003 16 Could not convert the data value due to reasons other than sign mismatch or overflow.
11004 16 Successfully returned a NULL value.
11005 16 Successfully returned a truncated value.
11006 16 Could not convert the data type because of a sign mismatch.
11007 16 Conversion failed because the data value overflowed the data type used by the provider.
11008 16 The provider cannot allocate memory or open another storage object on this column.
11009 16 The provider cannot determine the value for this column.
11010 16 The user did not have permission to write to the column.
11011 16 The data value violated the integrity constraints for the column.
11012 16 The data value violated the schema for the column.
11013 16 The column had a bad status.
11014 16 The column used the default value.
11015 16 The column was skipped when setting data.
11031 16 The row was successfully deleted.
11032 16 The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source.
11033 16 The row was released even though it had a pending change.
11034 16 Deletion of the row was canceled during notification.
11036 16 The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
11037 16 The row has a pending delete or the deletion had been transmitted to the data source.
11038 16 The row is a pending insert row.
11039 16 DBPROP_CHANGEINSERTEDROWS was VARIANT_FALSE and the insertion for the row has been transmitted to the data source.
11040 16 Deleting the row violated the integrity constraints for the column or table.
11041 16 The row handle was invalid or was a row handle to which the current thread does not have access rights.
11042 16 Deleting the row would exceed the limit for pending changes specified by the rowset property DBPROP_MAXPENDINGROWS.
11043 16 The row has a storage object open.
11044 16 The provider ran out of memory and could not fetch the row.
11045 16 User did not have sufficient permission to delete the row.
11046 16 The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution timing out.
11047 16 Updating did not meet the schema requirements.
11048 16 There was a recoverable, provider-specific error, such as an RPC failure.
11100 16 The provider indicates that conflicts occurred with other properties or requirements.
11101 16 Could not obtain an interface required for text, ntext, or image access.
11102 16 The provider could not support a required row lookup interface.
11103 16 The provider could not support an interface required for the UPDATE/DELETE/INSERT statements.
11104 16 The provider could not support insertion on this table.
11105 16 The provider could not support updates on this table.
11106 16 The provider could not support deletion on this table.
11107 16 The provider could not support a row lookup position.
11108 16 The provider could not support a required property.
11109 16 The provider does not support an index scan on this data source.

Related Articles :