SQL Server Errors or Failures from Error: 41191 to Error: 41211

SQLServerF1

Error: 41191, Severity: 16, The local availability replica of availability group ‘%.*ls’ cannot become the primary replica. The last-known primary availability replica is of a higher version than the local availability replica. Upgrade the local instance of SQL Server to the same

Error: 41192, Severity: 17, Creating and scheduling a worker task for AlwaysOn Availability Groups failed due to lack of resources (SQL OS error %d). Processing of new actions might be delayed or stalled until the resource limits are resolved. Reduce the memory or thread count on
Error: 41193, Severity: 10, Cannot join database ‘%.*ls’ to availability group ‘%.*ls’. The database is in the process of being removed from the availability group. When the remove-database operation completes, the database will no longer be joined to the availability group. Then

Error: 41194, Severity: 16, An error occurred while waiting for the local availability replica for availability group ‘%.*ls’ to complet post-online work. The operation encountered SQL OS error %d and has been terminated. Verify that the Windows Server Failover Clustering (WSFC) c
Error: 41195, Severity: 16, Availability group ‘%.*ls’ failed to process the WSFC lease-renewal command. The local availability replica lease is no longer valid to process the lease renewal command. Availability replica lease expired. This is an informational message only. No user a
Error: 41196, Severity: 16, Failed to create availability group ‘%.*ls’, because a Windows Server Failover Cluster (WSFC) group with the specified name already exists. An attempt to rollback the operation failed. Check the SQL Server error log for more details. To manually clean
Error: 41197, Severity: 15, The FAILOVER_MODE option has not been specified for the replica ‘%.*ls’. Reenter the command, specifying a failover mode for the replica.
Error: 41198, Severity: 15, The AVAILABILITY_MODE option has not been specified for the replica ‘%.*ls’. Reenter the command, specifying an availability mode for the replica.

Error: 41199, Severity: 16, The specified command is invalid because the AlwaysOn Availability Groups feature is not supported by this edition of SQL Server. For information about features supported by the editions of SQL Server, see SQL Server Books Online.
Error: 41201, Severity: 16, The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support remote data sources.
Error: 41202, Severity: 16, The source table ‘%.*ls’ specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function doesn’t have a full-text index that uses the STATISTICAL_SEMANTICS option. A full-text index using the STATISTICAL_SEMANT
Error: 41203, Severity: 16, The column ‘%.*ls’ specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function is not full-text indexed with the STATISTICAL_SEMANTICS option. The column must be full-text indexed using the STATISTICAL_SEMA
Error: 41204, Severity: 16, The source_key parameter is required in the SEMANTICSIMILARITYTABLE function.
Error: 41205, Severity: 10, Error %d occurred during semantic index population for table or indexed view ‘%.*ls’ (table or indexed view ID %d, database ID %d, document ID %d)
Error: 41206, Severity: 10, An ALTER FULLTEXT INDEX statement cannot remove the ‘STATISTICAL_SEMANTICS’ option from the last column in the index that has the option set when a “WITH NO POPULATION” clause is specified. Remove the “WITH NO POPULATION” clause.
Error: 41207, Severity: 10, A locale ID that is not supported was specified for a column with ‘STATISTICAL_SEMANTICS’. Please verify that the locale ID is correct and that the corresponding language statistics has been installed.
Error: 41208, Severity: 10, Warning: The population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’) encountered a document with full-text key value ‘%ls’ that specifies a language not supported for semantic indexing. Some columns of the row will not
Error: 41209, Severity: 10, A semantic language statistics database is not registered. Full-text indexes using ‘STATISTICAL_SEMANTICS’ cannot be created or populated.
Error: 41210, Severity: 10, The semantic language statistics database is not accessible or not valid. Full-text indexes using ‘STATISTICAL_SEMANTICS’ cannot be created or populated.
Error: 41211, Severity: 16, A semantic language statistics database is already registered.

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 from Error: 9979 to Error: 10008

SQLServerF1

 

Error: 9979, Severity: 10, Warning: During upgrade full-text catalog ‘%ls’ in database ‘%ls’ is set as offline because it failed to be created at path ‘%ls’. Please fix the full-text catalog path and rebuild the full-text catalog after upgrade.
Error: 9980, Severity: 16, Variable parameters can not be passed to fulltext predicates: contains, freetext and functions: containstable, freetexttable applied to remote table.
Error: 9982, Severity: 16, Cannot use full-text search in user instance.

Error: 9983, Severity: 16, The value ‘%ls’ for the full-text component ‘%ls’ is longer than the maximum permitted (%d characters). Please reduce the length of the value.
Error: 9984, Severity: 10, Informational: Full-text %ls population paused for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’).
Error: 9985, Severity: 16, There is not enough memory to generate a search property list cache. Rerun your full-text indexing statement when more resources are available.
Error: 9986, Severity: 16, A search property list cache cannot be generated during full-text indexing. Attempting to query the registered search properties caused an internal error as indicated by the HRESULT error code, ((HRESULT = ‘0x%08x’).

Error: 9987, Severity: 15, The max gap argument in NEAR clause must be either the word MAX or an integer greater than or equal to 0.
Error: 9988, Severity: 15, The number of query terms in NEAR clause must be less than or equal to 64.
Error: 9998, Severity: 16, The column ‘%.*ls’ cannot be added to a full-text index. Full-text indexes are limited to 1024 columns. When you create a full-text index, add fewer columns.
Error: 9999, Severity: 16, The column ‘%.*ls’ in the table ‘%.*ls’ cannot be used for full-text search because it is a sparse column set.
Error: 10000, Severity: 16, Unknown provider error.
Error: 10001, Severity: 16, The provider reported an unexpected catastrophic failure.
Error: 10002, Severity: 16, The provider did not implement the functionality.
Error: 10003, Severity: 16, The provider ran out of memory.
Error: 10004, Severity: 16, One or more arguments were reported invalid by the provider.
Error: 10005, Severity: 16, The provider did not support an interface.
Error: 10006, Severity: 16, The provider indicated an invalid pointer was used.
Error: 10007, Severity: 16, The provider indicated an invalid handle was used.
Error: 10008, Severity: 16, The provider terminated the operation.

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 from Error: 9955 to Error: 9978

SQLServerF1

 

Error: 9955, Severity: 16, SQL Server failed to create named pipe ‘%ls’ to communicate with the full-text filter daemon (Windows error: %d). Either a named pipe already exists for a filter daemon host process, the system is low on resources, or the security identification number (S
Error: 9959, Severity: 16, Cannot perform requested task because full-text memory manager is not initialized.
Error: 9960, Severity: 16, View ‘%.*ls’ is not an indexed view. Full-text index is not allowed to be created on it.
Error: 9961, Severity: 16, Logical name, size, maxsize, filegrowth, and offline properties of full-text catalog cannot be modified.

Error: 9962, Severity: 16, Failed to move full-text catalog from ‘%ls’ to ‘%ls’. OS error ‘%ls’.
Error: 9963, Severity: 10, Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID ‘%d’, database ID ‘%d’ is reset.
Error: 9964, Severity: 16, Failed to finish full-text operation. Filegroup ‘%.*ls’ is empty, read-only, or not online.
Error: 9965, Severity: 16, NULL or Invalid type of value specified for ‘%ls’ parameter.
Error: 9966, Severity: 16, Cannot use full-text search in master, tempdb, or model database.

Error: 9967, Severity: 10, A default full-text catalog does not exist in database ‘%.*ls’ or user does not have permission to perform this action.
Error: 9968, Severity: 10, Warning: No appropriate filter was found during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value ‘%ls’. Some columns of the row were not indexed.
Error: 9969, Severity: 10, Warning: No appropriate wordbreaker was found during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value ‘%ls’. Neutral wordbreaker was used for some columns of the row.
Error: 9970, Severity: 16, Couldn’t complete full-text operation because full-text key for table or indexed view ‘%.*ls’ is offline.
Error: 9971, Severity: 10, Warning: No appropriate filter for embedded object was found during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value ‘%ls’. Some embedded objects in the row could not be inde
Error: 9972, Severity: 16, Database is not fully started up or it is not in an ONLINE state. Try the full-text DDL command again after database is started up and becomes ONLINE.
Error: 9973, Severity: 10, Informational: Full-text %ls population paused for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Number of documents processed: %d. Number of documents failed: %d.
Error: 9974, Severity: 10, Warning: Only running full population can be paused. The command is ignored. Other type of population can just be stopped and it will continue when your start the same type of crawl again.
Error: 9975, Severity: 10, Warning: Only paused full population can be resumed. The command is ignored.
Error: 9977, Severity: 10, Warning: Last population complete time of full-text catalog in directory ‘%ls’ does not match database ‘%.*ls’. The full-text catalog is attached and it may need to be repopulated.
Error: 9978, Severity: 10, Warning: During upgrade full-text index on table ‘%ls’ is disabled because at least one of full-text key column, full-text columns, or type columns is a non-deterministic or imprecise nonpersisted computed column.

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 from Error: 7927 to Error: 7947

SQLServerF1

 

Error: 7927, Severity: 10, Total number of extents is %I64d.
Error: 7928, Severity: 16, The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
Error: 7929, Severity: 16, Check statement aborted. Database contains deferred transactions.
Error: 7930, Severity: 16, Mirroring must be removed from the database for this DBCC command.

Error: 7931, Severity: 16, Database error: The FILESTREAM directory ID %.*ls for a partition was seen two times.
Error: 7932, Severity: 16, Table error: The FILESTREAM directory ID %.*ls for object ID %d, index ID %d, partition ID %I64d is in filegroup %d, but should be in filegroup %d.
Error: 7933, Severity: 16, Table error: A FILESTREAM directory ID %.*ls exists for a partition, but the corresponding partition does not exist in the database.
Error: 7934, Severity: 16, DBCC CHECK cannot proceed on database %.*ls because it is a Secondary Replica and either Snapshot creation failed or the WITH TABLOCK option was specified. Secondary Replica databases cannot be exclusively locked for DBCC CHECK. Reason may have been given
Error: 7935, Severity: 16, Table error: A FILESTREAM directory ID %.*ls exists for a column of object ID %d, index ID %d, partition ID %I64d, but that column does not exist in the partition.

Error: 7936, Severity: 16, Table error: The FILESTREAM directory ID %.*ls exists for column ID %d of object ID %d, index ID %d, partition ID %I64d, but that column is not a FILESTREAM column.
Error: 7938, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d processing encountered file name “%.*ls” twice in the column directory %d container ID %d (for column ID %d).
Error: 7939, Severity: 16, Cannot detach database ‘%.*ls’ because it does not exist.
Error: 7940, Severity: 16, System databases master, model, msdb, and tempdb cannot be detached.
Error: 7941, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d processing encountered file name “%.*ls” twice in the column ID %d (for column directory %d container ID %d).
Error: 7942, Severity: 10, DBCC %ls scanning ‘%.*ls’ table…
Error: 7943, Severity: 10, Table: ‘%.*ls’ (%d); index ID: %d, database ID: %d
Error: 7944, Severity: 10, %ls level scan performed.
Error: 7945, Severity: 10, – Pages Scanned…………………………..: %I64d
Error: 7946, Severity: 10, – Extents Scanned…………………………: %I64d
Error: 7947, Severity: 10, – Extent Switches…………………………: %I64d

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 from Error: 7664 to Error: 7685

SQLServerF1

 

Error: 7664, Severity: 16, Full-text change tracking must be started on table or indexed view ‘%.*ls’ before the changes can be flushed.
Error: 7665, Severity: 16, Full Crawl must be executed on table or indexed view ‘%.*ls’. Columns affecting the index have been added or dropped since the last index full population.
Error: 7666, Severity: 16, User does not have permission to perform this action.
Error: 7668, Severity: 16, Cannot drop full-text catalog ‘%ls’ because it contains a full-text index.
Error: 7669, Severity: 10, Warning: Full-text index for table or indexed view ‘%.*ls’ cannot be populated because the database is in single-user access mode. Change tracking is stopped for this table or indexed view.

Error: 7670, Severity: 16, Column ‘%.*ls’ cannot be used for full-text search because it is not a character-based, XML, image or varbinary(max) type column.
Error: 7671, Severity: 16, Column ‘%.*ls’ cannot be used as full-text type column for image column. It must be a character-based column with a size less or equal than %d characters.
Error: 7672, Severity: 16, A full-text index cannot be created on the table or indexed view because duplicate column ‘%.*ls’ is specified.
Error: 7673, Severity: 10, Warning: Full-text change tracking is currently disabled for table or indexed view ‘%.*ls’.
Error: 7674, Severity: 10, Warning: The fulltext catalog ‘%.*ls’ is being dropped and is currently set as default.
Error: 7676, Severity: 10, Warning: Full-text auto propagation is on. Stop crawl request is ignored.

Error: 7677, Severity: 16, Column “%.*ls” is not full-text indexed.
Error: 7678, Severity: 16, The following string is not defined as a language alias in syslanguages: %.*ls.
Error: 7679, Severity: 16, Full-text index language of column “%.*ls” is not a language supported by full-text search.
Error: 7680, Severity: 16, Default full-text index language is not a language supported by full-text search.
Error: 7681, Severity: 10, Warning: Directory ‘%ls’ does not have a valid full-text catalog. Full-text catalog header file or attach state file either is missing or corrupted. The full-text catalog cannot be attached.
Error: 7682, Severity: 10, The component ‘%ls’ reported error while indexing. Component path ‘%ls’.
Error: 7683, Severity: 16, Errors were encountered during full-text index population for table or indexed view ‘%ls’, database ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Please see full-text crawl logs for details.
Error: 7684, Severity: 10, Error ‘%ls’ occurred during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value ‘%ls’. Failed to index the row.
Error: 7685, Severity: 10, Error ‘%ls’ occurred during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value ‘%ls’. Attempt will be made to reindex it.

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 from Error: 7001 to Error: 7119

SQLServerF1

 

Error: 7001, Severity: 16, OPENXML flags parameter must be of data type int.
Error: 7002, Severity: 16, OPENXML XPath must be of a string data type, such as nvarchar.
Error: 7003, Severity: 16, Only one OPENXML column can be of type %ls.
Error: 7004, Severity: 16, OPENXML does not support retrieving schema from remote tables, as in ‘%.*ls’.
Error: 7005, Severity: 16, OPENXML requires a metaproperty namespace to be declared if ‘mp’ is used for another namespace in sp_xml_preparedocument.
Error: 7006, Severity: 16, OPENXML encountered a problem identifying the metaproperty namespace prefix. Consider removing the namespace parameter from the corresponding sp_xml_preparedocument statement.

Error: 7007, Severity: 16, OPENXML encountered unknown metaproperty ‘%.*ls’.
Error: 7008, Severity: 16, The OPENXML EDGETABLE is incompatible with the XMLTEXT OVERFLOW flag.
Error: 7009, Severity: 16, OPENXML allows only one metaproperty namespace prefix declaration in sp_xml_preparedocument.
Error: 7101, Severity: 16, You need an active user transaction in order to use text pointers for a table with the option “text in row” set to ON.
Error: 7102, Severity: 20, Internal Error: Text manager cannot continue with current statement. Run DBCC CHECKTABLE.
Error: 7104, Severity: 16, Offset or size of data type is not valid. Data type must be of type int or smallint.
Error: 7105, Severity: 22, The Database ID %d, Page %S_PGID, slot %d for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE.

Error: 7106, Severity: 16, Internal error: An attempt was made to update a LOB data type using a read-only text pointer.
Error: 7107, Severity: 16, You can have only 1,024 in-row text pointers in one transaction
Error: 7108, Severity: 22, Database ID %d, page %S_PGID, slot %d, link number %d is invalid. Run DBCC CHECKTABLE.
Error: 7116, Severity: 16, Offset %d is not in the range of available LOB data.
Error: 7117, Severity: 16, Error reading large object (LOB) data from the tabular data stream (TDS).
Error: 7118, Severity: 16, Only complete replacement is supported when assigning a large object (LOB) to itself.
Error: 7119, Severity: 16, Attempting to grow LOB beyond maximum allowed size of %I64d bytes.

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: 825 to Error: 856

SQLServerF1

 

Error: 825, Severity: 10,
A read of the file ‘%ls’ at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be co

Error: 826, Severity: 10,
incorrect pageid (expected %d:%d; actual %d:%d)

Error: 829, Severity: 21,
Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.

Error: 830, Severity: 10,
stale page (a page read returned a log sequence number (LSN) (%u:%u:%u) that is older than the last one that was written (%u:%u:%u))

Error: 831, Severity: 20,
Unable to deallocate a kept page.

Error: 832, Severity: 24,
A page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file ‘%ls’, page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption.

Error: 833, Severity: 10,
SQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file [%ls] in database [%ls] (%d). The OS file handle is 0x%p. The offset of the latest long I/O is: %#016I64x

Error: 844, Severity: 10,
Time out occurred while waiting for buffer latch — type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit id: %I64d%ls, task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Continuing to wait.

Error: 845, Severity: 17,
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.

Error: 846, Severity: 10,
A time-out occurred while waiting for buffer latch — type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit Id: %I64d%ls, task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Not continuing to wait.

Error: 847, Severity: 10,
Timeout occurred while waiting for latch: class ‘%ls’, id %p, type %d, Task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Continuing to wait.

Error: 848, Severity: 10,
Using large pages in the memory manager.

Error: 849, Severity: 10,
Using locked pages in the memory manager.

Error: 850, Severity: 10,
%I64u MB of large page memory allocated.

Error: 851, Severity: 10,
the page is in an OFFLINE file which cannot be read

Error: 852, Severity: 10,
Using conventional memory in the memory manager.

Error: 853, Severity: 10,
Latch acquire failed due to too many concurrent latches. type %d, Task 0x%p : %d

Error: 854, Severity: 10,
Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.

Error: 855, Severity: 10,
Uncorrectable hardware memory corruption detected. Your system may become unstable. Please check the Windows event log for more details.

Error: 856, Severity: 10,
SQL Server has detected hardware memory corruption in database ‘%ls’, file ID: %u, page ID; %u, memory address: 0x%I64x and has successfully recovered the page.

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: 226 to Error: 246

SQLServerF1

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 226 to Error: 246

Error: 226, severity: 16,
%ls statement not allowed within multi-statement transaction.

Error: 227, severity: 15,
“%.*ls” is not a valid function, property, or field.

Error: 228, severity: 15,
Method ‘%.*ls’ of type ‘%.*ls’ in assembly ‘%.*ls’ does not return any value.

Error: 229, severity: 14,
The %ls permission was denied on the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’.

Error: 230, severity: 14,
The %ls permission was denied on the column ‘%.*ls’ of the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’.

Error: 231, severity: 11,
No such default. ID = %ld, database ID = %d.

Error: 232, severity: 16,
Arithmetic overflow error for type %ls, value = %f.

Error: 233, severity: 16,
The column ‘%.*ls’ in table ‘%.*ls’ cannot be null.

Error: 234, severity: 16,
There is insufficient result space to convert a money value to %ls.

Error: 235, severity: 16,
Cannot convert a char value to money. The char value has incorrect syntax.

Error: 236, severity: 16,
The conversion from char data type to money resulted in a money overflow error.

Error: 237, severity: 16,
There is insufficient result space to convert a money value to %ls.

Error: 239, severity: 16,
Duplicate common table expression name ‘%.*ls’ was specified.

Error: 240, severity: 16,
Types don’t match between the anchor and the recursive part in column “%.*ls” of recursive query “%.*ls”.

Error: 241, severity: 16,
Conversion failed when converting date and/or time from character string.

Error: 242, severity: 16,
The conversion of a %ls data type to a %ls data type resulted in an out-of-range value.

Error: 243, severity: 16,
Type %.*ls is not a defined system type.

Error: 244, severity: 16,
The conversion of the %ls value ‘%.*ls’ overflowed an %hs column. Use a larger integer column.

Error: 245, severity: 16,
Conversion failed when converting the %ls value ‘%.*ls’ to data type %ls.

Error: 246, severity: 16,
No anchor member was specified for recursive query “%.*ls”.

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.