SQL Server Errors or Failures from Error: 9813 to Error: 9913

SQLServerF1

 

Error: 9813, Severity: 16, The timezone provided to builtin function %.*ls would cause the datetimeoffset to overflow the range of valid date range in either UTC or local time.
Error: 9814, Severity: 16, The date provided is before the start of the Hijri calendar which in Microsoft’s ‘Kuwaiti Algorithm’ is July 15th, 622 C.E. (Julian calendar) or July 18th, 622 C.E (proleptic Gregorian calendar).
Error: 9815, Severity: 16, Waitfor delay and waitfor time cannot be of type %s.
Error: 9816, Severity: 16, The number of columns in the column set exceeds 2048. Reduce the number of columns that are referenced in the column set.

Error: 9817, Severity: 16, The specified column set value causes the estimated row size to be at least %d bytes. This exceeds the maximum allowed row size of %d bytes. To reduce the row size, reduce the number of columns specified in the column set.
Error: 9818, Severity: 16, The culture parameter ‘%.*ls’ provided in the function call is not supported.
Error: 9819, Severity: 16, Error converting string value ‘%.*ls’ into data type %ls using culture ‘%.*ls’.
Error: 9901, Severity: 16, Full-text catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’) is low on disk space. Pausing all populations in progress until more space becomes available. Reason code: %d. Error: %ls. To resume populations, free up disk space.

Error: 9902, Severity: 10, Full-text catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’) is low on system resources. Any population in progress will be paused until more resources become available. Reason code: %d. Error: %ls. If this message occurs frequently, try to serialize full-text
Error: 9903, Severity: 10, The full-text catalog health monitor reported a failure for full-text catalog ‘%ls’ (%d) in database ‘%ls’ (%d). Reason code: %d. Error: %ls. The system will restart any in-progress population from the previous checkpoint. If this message occurs frequentl
Error: 9904, Severity: 10, The full-text catalog ‘%ls’ (%d) in database ‘%ls’ (%d) will be remounted to recover from a failure. Reason code: %d. Error: %ls. If this message occurs frequently, consult SQL Server Books Online for troubleshooting assistance. This is an informational m
Error: 9905, Severity: 10, Informational: Full-text indexer requested status change for catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’). New Status: %ls, Reason: %ls (%ls).
Error: 9906, Severity: 10, The full-text catalog monitor reported catalog ‘%ls’ (%d) in database ‘%ls’ (%d) in %ls state. This is an informational message only. No user action is required.
Error: 9907, Severity: 10, Error: Total number of items in full-text catalog ID ‘%d’ in database ID ‘%d’ exceeds the supported limit. See Books Online for troubleshooting assistance.
Error: 9908, Severity: 10, Changing the status to %ls for full-text catalog ‘%ls’ (%d) in database ‘%ls’ (%d). This is an informational message only. No user action is required.
Error: 9909, Severity: 10, Warning: Failed to change the status to %ls for full-text catalog ‘%ls’ (%d) in database ‘%ls’ (%d). Error: %ls.
Error: 9910, Severity: 10, Warning: Error occurred during full-text %ls population for table or indexed view ‘%ls’, database ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Error: %ls.
Error: 9911, Severity: 10, Informational: Full-text %ls population initialized for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Population sub-tasks: %d.
Error: 9912, Severity: 10, Error: Failed to initialize full-text %ls population for table or indexed view ‘%ls’, database ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Error: %d.
Error: 9913, Severity: 10, Informational: Resuming full-text population for table or indexed view ‘%ls’ in database ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Prior number of documents processed: %d, error encountered: %d.

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 *