错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 4 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 5381 — Internal error during Index On Expression creation for index: '%.*s'.
- 5382 — Cannot drop index '%.*s' because it contains $expression_index column and the 'Index on Expression' feature is OFF.
- 5383 — Cannot reference Index on Expression column '%.*s' during index creation.
- 5384 — Json path column mapping is not allowed in the column definition for the column '%ls' and file format '%ls'.
- 5385 — Windowed functions can only appear in the SELECT, ORDER BY, or QUALIFY clauses.
- 5386 — This object represents a reserved namespace by one of the participating client engines under unification.
- 5387 — TABLESAMPLE supports only the PERCENT option for this data source.
- 5501 — The FILESTREAM filegroup was dropped before the table can be created.
- 5502 — The FILESTREAM container is inaccessible.
- 5503 — Unable to find entry in sys.database_files for FILESTREAM file '%.*ls'.
- 5504 — 'PRIMARY' can only be specified for FILESTREAM log filegroup in a 'CONTAINS' clause.
- 5505 — A table that has FILESTREAM columns must have a nonnull unique column with the ROWGUIDCOL property.
- 5506 — FILESTREAM data or log file cannot be named 'DEFAULT'.
- 5507 — DEFAULT cannot be specified for FILESTREAM log filegroup '%.*ls'.
- 5508 — FILESTREAM can only be declared for VARBINARY columns.
- 5509 — The properties SIZE or FILEGROWTH cannot be specified for the FILESTREAM data file '%.*ls'.
- 5510 — LOG ON cannot be used for non-FILESTREAM file group '%.*ls'.
- 5511 — FILESTREAM's file system log record '%.*ls' under log folder '%.*ls' is corrupted.
- 5512 — Error 0x%x (%ls) was encountered while directory '%.*ls' was being truncated.
- 5513 — The name that is specified for the associated log filegroup for FILESTREAM filegroup '%.*ls' is not valid.
- 5514 — Transactional replication/Change Data Capture cannot proceed because Transactional File System Resource Manager at '%.*ls' is not started.
- 5515 — Cannot open the container directory '%.*ls' of the FILESTREAM file. The operating system has returned the status code 0x%x.
- 5516 — The FILESTREAM log filegroup '%.*ls' cannot be referred to by more than one FILESTREAM data filegroup.
- 5517 — FILESTREAM container MAXSIZE must be greater than or equal to 512 KB.
- 5518 — FILESTREAM path '%.*ls' is too long.
- 5519 — A database must have primary FILESTREAM log filegroup and log file in order for it to contain other FILESTREAM filegroups.
- 5520 — Upgrade of FILESTREAM container ID %d in the database ID %d failed because of container size recalculation error. Examine the previous errorlog entrie…
- 5521 — Error 0x%x (NT status code) was encountered when SQL Server attempts to retrieve '%.*ls' from the Transaction File System Resource Manager located at …
- 5522 — FILESTREAM data file cannot be removed because its log file has not been backed up.
- 5523 — FILESTREAM data file group cannot be added to refer to an empty FILESTREAM log file group.
- 5524 — Default FILESTREAM data filegroup cannot be removed unless it's the last FILESTREAM data filegroup left.
- 5525 — The READ_ONLY and READ_WRITE property cannot be modified on a FILESTREAM log filegroup.
- 5526 — The FILESTREAM log file '%.*ls' cannot be removed because it is being referenced by a FILESTREAM data filegroup.
- 5527 — The primary FILESTREAM log file cannot be dropped because other FILESTREAM filegroups exist.
- 5528 — A database can have at most one primary FILESTREAM log filegroup and log file.
- 5529 — Failed to remove a FILESTREAM file. The database is a primary database in an availability group. Wait for the FILESTREAM data files to be hardened on …
- 5531 — Error 0x%x (NT status code) was encountered when SQL Server attempts to change the logging mode of Transaction File System Resource Manager located at…
- 5532 — SQL Server cannot obtain the Kernel Transaction Manager's transaction context to perform file system operation.
- 5533 — The FILESTREAM file system log record that has the LSN '%d:%d:%d' is missing. Log folder '%.*ls' is corrupted. Restore the database from a backup.
- 5534 — SQL log record at LSN '%d:%d:%d' for database '%.*ls' is corrupted. Database cannot recover.
- 5535 — FILESTREAM data container '%.*ls' is corrupted. Database cannot recover.
- 5536 — FILESTREAM deleted folder '%.*ls' is corrupted. Database cannot recover.
- 5537 — Function %ls is only valid on columns with the FILESTREAM attribute.
- 5538 — Partial updates are not supported on columns that have a FILESTREAM as a source.
- 5539 — The ROWGUIDCOL column associated with the FILESTREAM being used is not visible where method %ls is called.
- 5540 — The FILESTREAM column cannot be used with method %ls because the associated ROWGUIDCOL of the base table is nullable or does not have a unique constra…
- 5541 — An open mode must be used when a FILESTREAM column is opened as a file.
- 5542 — The FILESTREAM filegroup '%.*ls' has no files assigned to it. FILESTREAM data cannot be populated on this filegroup until a file is added.
- 5543 — FILESTREAM: effective level = %d (remote access disabled), configured level = %d, file system access share name = '%.*ls'.
- 5544 — FILESTREAM: effective level = %d (remote access enabled), configured level = %d, file system access share name = '%.*ls'.
- 5545 — FILESTREAM: connected to kernel driver %ls. This is an informational message. No user action is required.
- 5546 — FILESTREAM: failed to connect to kernel driver %ls.
- 5550 — Too many Filestream containers were specified for Filestream Filegroup '%.*ls'. Specifying more than one Filestream Container per Filestream Filegroup…
- 5551 — FILESTREAM file '%.*ls' cannot be added because its destination filegroup cannot have more than one file. Specifying more than one Filestream Containe…
- 5552 — FILESTREAM file named with GUID '%.*ls' that belongs to FILESTREAM data file ID 0x%x does not exist or cannot be opened.
- 5553 — SQL Server internal error. FILESTREAM manager cannot continue with current command.
- 5554 — The total number of versions for a single file has reached the maximum limit set by the file system.
- 5555 — The operation has failed because the FILESTREAM data cannot be renamed.
- 5556 — The database '%.*ls' does not exist or does not support FILESTREAM. Supply a valid database name. To see available databases, use sys.databases.
- 5557 — The FILESTREAM container '%.*ls' does not exist or cannot be processed. Supply a valid FILESTREAM container name. To see available containers, use sys…
- 5558 — Database '%.*ls' should be in single-user mode.
- 5559 — Could not open the database '%.*ls'.
- 5560 — Access to the FILESTREAM tombstone table for the database '%.*ls' cannot be performed at the moment because it conflicts with another activity, such a…
- 5561 — FILESTREAM garbage collector operation was aborted on the database '%.*ls'.
- 5570 — FILESTREAM Failed to find the garbage collection table.
- 5571 — Internal FILESTREAM error: failed to access the garbage collection table.
- 5572 — Internal FILESTREAM error: failed to perform a filesystem operation because of a potential corruption.
- 5573 — Internal FILESTREAM error: failed to access the tombstones table with HRESULT: 0x%x.
- 5574 — A database cannot be enabled for both Database Mirroring and FILESTREAM or for both Database Mirroring and MEMORY_OPTIMIZED_DATA storage.
- 5575 — Operation '%ls' failed with HRESULT: %ls in file '%hs', line %d while executing sp_filestream_configure.
- 5576 — FILESTREAM feature is enabled. This is an informational message. No user action is required.
- 5577 — FILESTREAM access level has been changed to %d. Restart the instance of SQL Server for the settings to fully take effect.
- 5578 — A failure occurred while FILESTREAM configuration was being changed or applied. For more information, see the SQL Server error log.
- 5579 — FILESTREAM: effective level = %d, configured level = %d.
- 5580 — FILESTREAM InstanceGuid is null. Registry settings might be corrupted.
- 5581 — FILESTREAM feature has been disabled. Restart the instance of SQL Server for the settings to fully take effect. If you have data in FILESTREAM columns…
- 5582 — Machine reboot is required before the FILESTREAM feature settings can take effect.
- 5583 — The specified value for the enable_level parameter of the sp_filestream_configure stored procedure is not valid. The value must be 0, 1, 2, or 3.
- 5584 — Another session is executing the sp_filestream_configure stored procedure. Check the updated configuration settings and retry the operation if necessa…
- 5585 — FILESTREAM file I/O access could not be enabled. The operating system Administrator must enable FILESTREAM file I/O access on the instance using Confi…
- 5586 — The FILESTREAM feature is already configured to the specified level. No change has been made.
- 5588 — Access to FILESTREAM data is not supported under snapshot isolation level.
- 5589 — Access to FILESTREAM data is not supported under row versioning-based read committed snapshot isolation (RCSI).
- 5590 — FILESTREAM operations are not supported on the platform.
- 5591 — FILESTREAM feature is disabled.
- 5592 — FILESTREAM feature doesn't have file system access enabled.
- 5593 — FILESTREAM feature is not supported on WoW64. The feature is disabled.
- 5594 — The value specified for the computer_name_format parameter of the .%ls() function is not valid.
- 5595 — .PhysicalPathName is disabled.
- 5596 — FILESTREAM feature configuration might be inconsistent. To reset the configuration, use the sp_configure stored procedure.
- 5597 — FILESTREAM feature could not be initialized. The operating system Administrator must enable FILESTREAM on the instance using Configuration Manager.
- 5598 — FILESTREAM feature is not supported on user instances.
- 5599 — .ContainerId is disabled.
- 5600 — The Cross Database Chaining option cannot be set to the specified value on the specified database.
- 5601 — The service master key could not be force regenerated as requested by the -F startup option. The error number is %ld.
- 5602 — The service master key regeneration was successful.
- 5603 — The password for SA could not be force regenerated as requested by the -K startup option. The error number is %ld.
- 5604 — The password regeneration attempt for SA was successful.
- 5605 — The password for SA account could not be force regenerated and/or SA account cannot be disabled as requested by the -K startup option and the -T1617 t…
- 5701 — Changed database context to '%.*ls'.
- 5702 — SQL Server is terminating this process.
- 5703 — Changed language setting to %.*ls.
- 5803 — Unknown configuration (id = %d) encountered in sys.configurations.
- 5804 — Character set, sort order, or collation cannot be changed at the server level because at least one database is not writable. Make the database writabl…
- 5805 — Too few locks specified. Minimum %d.
- 5807 — Recovery intervals above %d minutes not recommended. Use the RECONFIGURE WITH OVERRIDE statement to force this configuration.
- 5808 — Ad hoc update to system catalogs is not supported.
- 5810 — Valid values for the fill factor are 0 to 100.
- 5812 — You do not have permission to run the RECONFIGURE statement.
- 5828 — User connections are limited to %d.
- 5829 — The specified user options value is invalid.
- 5831 — Minimum server memory value (%d) must be less than or equal to the maximum value (%d).
- 5832 — The affinity mask specified does not match the CPU mask on this system.
- 5833 — The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server.
- 5834 — The affinity specified conflicts with the IO affinity mask specified. Change the affinity setting to use different CPUs than those specified in the IO…
- 5835 — Failed to start CPUs with the mask 0x%lx on the system.
- 5836 — Lightweight pooling is not supported on this platform or in this edition of SQL Server.
- 5837 — The service broker listen port cannot be dynamic. Valid port values are 1024-32767.
- 5838 — The service broker connection authentication value is invalid.
- 5839 — The service broker message forward store size cannot be set to 0.
- 5840 — The service broker message forward mode is invalid.
- 5841 — The default full-text language is not supported by the full-text search component.
- 5842 — Too few worker threads are specified. The minimum is %d.
- 5844 — User Instances are not supported in this edition of SQL Server.
- 5846 — Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" or "lightweight pooling"…
- 5848 — Physical CPU id %u has been hot added to node id %u as logical CPU id %u. This is an informational message only. No user action is required.
- 5849 — Online CPU addition is not supported in the current edition of SQL Server.
- 5850 — Online addition of CPU resources cannot be completed. A software non-uniform memory access (soft-NUMA) configuration was specified at SQL Server start…
- 5851 — The AccessCheckResult quota must be greater than or equal to the bucket count
- 5852 — The AccessCheckResult bucket count must be less than %d.
- 5853 — The affinity range is invalid. The lower bound %d must be less than the upper bound %d.
- 5854 — A %S_MSG value was specified more than one time in the range list for an ALTER SERVER CONFIGURATION SET PROCESS AFFINITY statement.
- 5855 — The affinity setting was not changed. This can be caused by low system resources.
- 5856 — The %S_MSG range that specifies %S_MSG %d includes at least one %S_MSG that is not available to the current instance. The maximum %S_MSG number that i…
- 5857 — CPU
- 5858 — NUMANODE
- 5859 — The current affinity setting specifies the use of more than 64 processors. Before you use sp_configure to change affinity settings, remove these proce…
- 5860 — Affinity changed for node %d: from 0x%0*I64x:%u to 0x%0*I64x:%u. This is an informational message only. No user action is required.
- 5861 — A %S_MSG with id %d does not exist on this system. Use sys.dm_os_schedulers to locate valid %S_MSGs for this system.
- 5862 — The number of max worker threads is set too low. On this computer, the number must be more than %u. You should increase the number of max worker threa…
- 5863 — Could not change the value of the '%.*ls' property. Operating system error %ls
- 5864 — IO affinity is not supported on this edition of sql server.
- 5865 — Dynamic configuration setting %ls%ls has been changed to %ld.
- 5866 — Max server memory specified - %I64d MB is greater than the buffer pool extension size - %I64d MB. Buffer pool extension would be disabled on restart.
- 5867 — Changing AFFINITY is not supported when the sql server is running in agnostic affinity mode.
- 5868 — File system DMVs and DMFs have been disabled.
- 5869 — Changes to server configuration option %s are not supported in SQL Database Managed Instances.
- 5870 — Changes to server configuration option %s are not supported in SQL Database Managed Instances.
- 5871 — Cannot set the column encryption enclave type to Virtualization-based security (VBS) - the operating system does not support VBS.
- 5872 — Invalid column encryption enclave type %d specified.
- 5873 — Cannot set the column encryption enclave type to Software Guard Extension (SGX)- the operating system does not support SGX.
- 5874 — Changes to server configuration options are not permitted in the connection to Contained Availability Group. Change connection to SQL Server instance …
- 5875 — Cannot configure tiered memory for this edition of SQL Server.
- 5876 — Tiered Memory is not supported on this platform or in this edition of SQL Server.
- 5901 — One or more recovery units belonging to database '%.*ls' failed to generate a checkpoint. This is typically caused by lack of system resources such as…
- 5902 — CHECKPOINT is not supported while asynchronous database recovery is in progress on database '%.*ls'. The database remains fully available for read and…
- 5904 — Unable to issue checkpoint: there are not enough locks available. Background checkpoint process will remain suspended until locks are available. To fr…
- 6001 — SHUTDOWN is waiting for %d process(es) to complete.
- 6004 — User does not have permission to perform this action.
- 6005 — SHUTDOWN is in progress.
- 6006 — Server shut down by %.*ls from login %.*ls.
- 6007 — The SHUTDOWN statement cannot be executed within a transaction or by a stored procedure.
- 6008 — Can't run the query because the workspace is temporarily unavailable. Wait for a moment, then reconnect to the workspace and try again.
- 6101 — Session ID %d is not valid.
- 6102 — User does not have permission to use the KILL statement.
- 6103 — Could not do cleanup for the killed process. Received message %d.
- 6104 — Cannot use KILL to kill your own process.
- 6106 — Process ID %d is not an active process ID.
- 6107 — Only user processes can be killed.
- 6108 — KILL SPID WITH COMMIT/ROLLBACK is not supported by Microsoft SQL Server. Use KILL UOW WITH COMMIT/ROLLBACK to resolve in-doubt distributed transaction…
- 6109 — SPID %d: transaction rollback in progress. Estimated rollback completion: %d%%. Estimated time remaining: %d seconds.
- 6110 — The distributed transaction with UOW %s does not exist.
- 6111 — Another user has decided a different outcome for the distributed transaction associated with UOW %s.
- 6112 — Distributed transaction with UOW %s is in prepared state. Only Microsoft Distributed Transaction Coordinator can resolve this transaction. KILL comman…
- 6113 — The distributed transaction associated with UOW %s is in PREPARE state. Use KILL UOW WITH COMMIT/ROLLBACK syntax to kill the transaction instead.
- 6114 — Distributed transaction with UOW %s is being used by another user. KILL command failed.
- 6115 — KILL command cannot be used inside user transactions.
- 6117 — There is a connection associated with the distributed transaction with UOW %s. First, kill the connection using KILL SPID syntax.
- 6118 — The distributed transaction associated with UOW %s is not in PREPARED state. Use KILL UOW to kill the transaction instead.
- 6119 — Distributed transaction with UOW %s is rolling back: estimated rollback completion: %d%%, estimated time left %d seconds.
- 6120 — Status report cannot be obtained. Rollback operation for Process ID %d is not in progress.
- 6121 — Status report cannot be obtained. Rollback operation for UOW %s is not in progress.
- 6200 — Method "%ls" of type "%ls" in assembly "%.*ls" is marked as a mutator. Mutators cannot be used in the read-only portion of the query.
- 6201 — Method "%ls" of type "%ls" in assembly "%.*ls" is not marked as a mutator. Only mutators can be used to update the value of a CLR type.
- 6202 — Method "%ls" of type "%ls" in assembly "%.*ls" does not return a value.
- 6203 — Method '%ls' of type '%ls' in assembly '%.*ls' cannot be marked as a mutator. A mutator method must be non-static, public, and returns void type.
- 6204 — Trying to send a record with %d columns(s) in a result set with %d column(s).
- 6205 — %s ASSEMBLY failed because assembly '%.*ls' was compiled with /UNSAFE option, but the assembly was not registered with the required PERMISSION_SET = U…
- 6206 — Request submitted with too many parameters. The maximum number is %ld.
- 6207 — Error converting %.*ls to fixed length binary type. The result would be padded and cannot be converted back.
- 6208 — %s failed because the parameter count for the FillRow method should be one more than the SQL declaration for the table valued CLR function.
- 6209 — Unsound ordering on CLR type "%.*ls": returning NULL on non-NULL inputs.
- 6210 — CLR type '%.*ls' is not fully comparable.
- 6211 — %s ASSEMBLY failed because type '%.*ls' in %.*ls assembly '%.*ls' has a static field '%.*ls'. Attributes of static fields in %.*ls assemblies must be …
- 6212 — %s ASSEMBLY failed because method '%.*ls' on type '%.*ls' in %.*ls assembly '%.*ls' is storing to a static field. Storing to a static field is not all…
- 6213 — %s ASSEMBLY failed because method "%.*ls" on type "%.*ls" in %.*ls assembly "%.*ls" has a synchronized attribute. Explicit synchronization is not allo…
- 6214 — %s ASSEMBLY failed because assembly "%.*ls" has an unmanaged entry point.
- 6215 — %s ASSEMBLY failed because method '%.*ls' on type '%.*ls' in %.*ls assembly '%.*ls' has invalid attribute 0x%x.
- 6216 — %s ASSEMBLY failed because type "%.*ls" in %.*ls assembly "%.*ls" has a finalizer. Finalizers are not allowed in %.*ls assemblies.
- 6217 — ALTER ASSEMBLY ADD FILE failed because the file, "%.*ls", being added is empty.
- 6218 — %s ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' failed verification. Check if the referenced assemblies are up-to-date and trusted (f…
- 6219 — %s ASSEMBLY failed because assembly source parameter %d has an unmanaged entry point.
- 6220 — SELECT INTO failed because CLR type "%.*ls" does not exist in the target database.
- 6221 — The cursor operation generated more than one row of different column metadata.
- 6222 — Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is not valid for native serialization.
- 6223 — Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is of type "%.*ls.%.*ls", which is not marked with "Lay…
- 6224 — Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is marked with "System.NonSerializedAttribute". Native …
- 6225 — Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is of type "%.*ls.%.*ls" which is a non-value type. Nat…
- 6226 — Type "%.*ls.%.*ls" is marked for user-defined serialization, but does not implement the "%.*ls.%.*ls" interface.
- 6227 — Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is of type "%.*ls.%.*ls", which is not blittable, or ty…
- 6228 — Type "%.*ls.%.*ls" is marked for native serialization, but it contains non-blittable fields.
- 6229 — Type "%.*ls.%.*ls" is marked for native serialization. It is not marked with "LayoutKind.Sequential". Native serialization requires the type to be mar…
- 6230 — Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" has field marshallers. Native serialization types canno…
- 6231 — Type "%.*ls.%.*ls" is marked for native serialization, but one of its base types "%.*ls.%.*ls" is not valid for native serialization.
- 6232 — Type "%.*ls.%.*ls" is marked for native serialization, but base type "%.*ls.%.*ls" is not marked with "LayoutKind.Sequential". Native serialization re…
- 6233 — In proc data access is not allowed in an impersonated state.
- 6234 — Data truncation error. Length (%d) exceeds maximum length (%d) for type '%.*ls'.
- 6235 — Data serialization error. Length (%d) is less than fixed length (%d) for type '%.*ls'.
- 6236 — %s ASSEMBLY failed because filename '%.*ls' is too long.
- 6237 — %s ASSEMBLY failed because method "%.*ls" on type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls".
- 6238 — %s ASSEMBLY failed because field "%.*ls" in type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls".
- 6239 — %s ASSEMBLY failed because type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls".
- 6240 — ALTER ASSEMBLY failed because the function '%s' of type '%s' no longer satisfies indexability requirements, and is used for the indexed view '%s'.
- 6241 — Trying to send a record with type or name of column %d differing from the type or name of the corresponding column of the result set.
- 6242 — CREATE ASSEMBLY failed because the user "%.*ls" specified in the authorization clause does not exist.
- 6243 — '%.*ls.%.*ls' is marked for native serialization, and has the MaxByteSize property specified in the '%.*ls' attribute. Native serialization objects ca…
- 6244 — The size (%d) for "%.*ls.%.*ls" is not in the valid range. Size must be -1 or a number between 1 and 8000.
- 6245 — Invalid serialization format (%d) for type "%.*ls.%.*ls".
- 6246 — Assembly "%.*ls" already exists in database "%.*ls".
- 6247 — Cannot create type because '%.*ls.%.*ls' cannot have fixed length if it has MaxByteSize set to -1.
- 6248 — %s failed because the type '%s' contains a method '%s' specified by SqlUserDefinedType.ValidateMethodName that does not conform to the required specif…
- 6249 — The associated file "%.*ls" already exists for assembly "%.*ls".
- 6250 — Assembly "%.*ls" does not have an associated file "%.*ls".
- 6251 — ALTER ASSEMBLY failed because the assembly file parameter %d is not a valid expression.
- 6252 — ALTER ASSEMBLY failed because a file name was not specified for the inline assembly file parameter %d.
- 6253 — Common language runtime (CLR) functionality initialized using CLR version %ls from %ls.
- 6254 — Common language runtime (CLR) functionality initialized.
- 6255 — %s failed because type "%s" does not conform to the %s specification: missing custom attribute "%.*ls".
- 6256 — SqlPipe request submitted with too many columns. The maximum number is %d.
- 6257 — CREATE ASSEMBLY for assembly '%.*ls' failed because the assembly is built for an unsupported version of the Common Language Runtime.
- 6258 — Function signature of "FillRow" method (as designated by SqlFunctionAttribute.FillRowMethodName) does not match SQL declaration for table valued CLR f…
- 6259 — Assembly '%.*ls' could not be loaded because it failed verification. %.*ls
- 6260 — An error occurred while getting new row from user defined Table Valued Function : %.*ls.
- 6261 — The CLR type referenced by column "%.*ls" of table variable "%.*ls" has been dropped during the execution of the batch. Run the batch again.
- 6262 — Assembly was not found in current database or version did not match.
- 6263 — Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option.
- 6264 — Data access failed because the .NET Framework routine is not marked with "DataAccessKind.Read" or "SystemDataAccessKind.Read".
- 6265 — %s ASSEMBLY failed because type "%.*ls" in %.*ls assembly "%.*ls" has a pinvokeimpl method. P/Invoke is not allowed in %.*ls assemblies.
- 6266 — Warning: Assembly "%.*ls" was built using version %.*ls of the .NET Framework. SQL Server currently uses version %s.
- 6267 — Assembly "%.*ls" does not exist, or the user does not have permission to reference it.
- 6268 — Attempt to perform native server operation (%ls) outside of its valid scope.
- 6269 — ALTER ASSEMBLY failed because the user-defined aggregate "%s" does not exist or is not correctly defined in the updated assembly.
- 6270 — ALTER ASSEMBLY failed because the required method "%s" in type "%s" was not found with the same signature in the updated assembly.
- 6271 — ALTER ASSEMBLY failed because the required field "%s" in type "%s" was not found with the same signature in the updated assembly.
- 6272 — ALTER ASSEMBLY failed because required property '%s' in type '%s' was not found with the same signature in the updated assembly.
- 6273 — ALTER ASSEMBLY failed because required type '%s' does not exist or is not correctly defined in the updated assembly.
- 6274 — ALTER ASSEMBLY failed because the serialization format of type '%s' would change in the updated assembly. Persisted types are not allowed to change se…
- 6275 — ALTER ASSEMBLY failed because the IsByteOrdered attribute of type '%s' would change in the updated assembly.
- 6276 — ALTER ASSEMBLY failed because serialization data of type '%s' would change in the updated assembly. Persisted types are not allowed to change serializ…
- 6277 — ALTER ASSEMBLY failed because the MaxLen attribute of type '%s' would change in the updated assembly. Persisted types are not allowed to change MaxLen…
- 6278 — ALTER ASSEMBLY failed because the IsFixedLen attribute of type '%s' would change in the updated assembly. Persisted types are not allowed to change Is…
- 6279 — ALTER ASSEMBLY failed because the mutator attribute of method '%s' in type '%s' would change in the updated assembly, and the method is in use by the …
- 6280 — ALTER ASSEMBLY failed because table, view or constraint '%s' depends on this assembly. Use WITH UNCHECKED DATA to skip checking for persisted data.
- 6281 — ALTER ASSEMBLY failed because only users with ALTER ANY SCHEMA permissions can use WITH UNCHECKED DATA.
- 6282 — ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same.
- 6283 — ALTER ASSEMBLY failed because only the assembly revision version number is allowed to change.
- 6284 — ALTER ASSEMBLY failed because it is referenced by object '%.*ls'. Assemblies that are referenced by SQL objects cannot be made invisible.
- 6285 — %s ASSEMBLY failed because the source assembly is, according to MVID, identical to an assembly that is already registered under the name "%.*ls".
- 6286 — '%s' ASSEMBLY failed because a different version of assembly '%s', referenced by assembly '%s', is already in the database.
- 6287 — ALTER ASSEMBLY failed because the function '%s' of type '%s' no longer satisfies indexability requirements, and is used for the persisted computed col…
- 6288 — ALTER ASSEMBLY has marked data as unchecked in one or more objects in database "%.*ls". Refer to column "has_unchecked_assembly_data" from system view…
- 6289 — Failed to allocate memory for common language runtime (CLR) functionality.
- 6290 — AppDomain %i (%.*ls) unloaded.
- 6291 — AppDomain %i (%.*ls) failed to unload with error code 0x%x.
- 6292 — The transaction that is associated with this operation has been committed or rolled back. Retry with a different transaction.
- 6293 — %.*ls.%.*ls.%.*ls: SqlFacetAttribute is invalid on a non-public member.
- 6294 — %.*ls.%.*ls.%.*ls: %.*ls property of SqlFacetAttribute cannot be used in this context.
- 6295 — %.*ls.%.*ls.%.*ls: %.*ls property of SqlFacetAttribute has an invalid value.
- 6296 — %.*ls.%.*ls.%.*ls : SqlFacetAttribute cannot be applied to a property getter or a property setter. It should be applied to the property itself.
- 6297 — %.*ls.%.*ls.%.*ls: The SqlFacetAttribute property IsFixedLength cannot be set to true when MaxSize is set to -1.
- 6298 — %.*ls.%.*ls.%.*ls: The SqlFacetAttribute properties Precision and Scale have to be used together.
- 6299 — AppDomain %i (%.*ls) created.
- 6302 — The argument of CREATE or ALTER XML SCHEMA COLLECTION statement must be a string expression.
- 6303 — XML parsing: Document parsing required too much memory
- 6304 — XML parsing: An unexpected error has occurred in the XML parser.
- 6305 — XQuery data manipulation expression required in XML data type method.
- 6306 — Invalid XQuery expression passed to XML data type method.
- 6307 — XML well-formedness check: Attribute cannot appear outside of element declaration. Rewrite your XQuery so it returns well-formed XML.
- 6308 — XML well-formedness check: Duplicate attribute '%.*ls'. Rewrite your XQuery so it returns well-formed XML.
- 6309 — XML well-formedness check: the data for node '%.*ls' contains a character (0x%04X) which is not allowed in XML.
- 6310 — Altering existing schema components is not allowed. There was an attempt to modify an existing XML Schema component, component namespace: '%.*ls' comp…
- 6311 — An internal XMLDB schema processor error occurred. Contact Technical Support for assistance.
- 6312 — Could not find schema components with target namespace '%.*ls' in collection '%.*ls'.
- 6314 — Collection specified does not exist in metadata : '%.*ls'
- 6315 — XQuery: Cannot update with value '%.*ls' as the canonical form of type '{%.*ls}%.*ls' violates the required pattern. It is recommended that you not us…
- 6316 — Specified component '%s' can not be dropped because it is used by component:'%s'
- 6317 — XQuery: Cannot update with value '%.*ls' because it failed validation against type '{%.*ls}%.*ls'
- 6318 — XQuery: String conversion failed during UPDATE validation
- 6320 — XQuery: Only nillable elements or text nodes can be updated with empty sequence
- 6321 — xml:space attribute must have a value of 'preserve' or 'default'. '%.*ls' is not valid.
- 6322 — XML Parser ran out of memory. This could be caused by too many attributes or namespace declarations.
- 6323 — The xml schema collection for variable '%.*ls' has been altered while the batch was being executed. Remove all XML schema collection DDL operations it…
- 6324 — DROP XML INDEX does not support any options.
- 6325 — XQuery: Replacing the value of a node with an empty sequence is allowed only if '()' is used as the new value expression. The new value expression eva…
- 6326 — XML well-formedness check: XML namespace declaration cannot appear outside of element declaration. Rewrite your XQuery so it returns well-formed XML.
- 6327 — The specified xml schema collection ID is not valid: %d
- 6328 — Specified collection '%.*ls' cannot be dropped because it is used by %S_MSG '%ls'.
- 6329 — Unsupported usage of a QName typed value in node '%.*ls'
- 6330 — Column '%.*ls' on table '%.*ls' is not of type XML, which is required to create an XML index on it.
- 6331 — Primary XML Index '%.*ls' already exists on column '%.*ls' on table '%.*ls', and multiple Primary XML Indexes per column are not allowed.
- 6332 — Table '%.*ls' needs to have a clustered primary key with less than %d columns in it in order to create a primary XML index on it.
- 6333 — Could not find%ls XML index named '%.*ls' on table '%.*ls'
- 6334 — Could not create the XML or spatial index on object '%.*ls' because that object is not a table. Create the index on the base table column.
- 6335 — XML datatype instance has too many levels of nested nodes. Maximum allowed depth is %d levels.
- 6336 — Maximum size of primary index of table '%.*ls' is %d bytes. CREATE XML INDEX requires that such size should be limited to %d bytes
- 6337 — '%.*ls' is not a valid XML Index name because it starts with '%c' character. XML Index name should not start with '#' or '@'
- 6338 — XML DTD has been stripped from one or more XML fragments. External subsets, if any, have been ignored.
- 6339 — Specified collection '%.*ls' cannot be modified because it is SQL Server built-in XML Schema Collection.
- 6340 — Xml schema collection '%.*ls' referenced by table variable '%.*ls' has been dropped or altered during the execution of the batch. Please re-run the ba…
- 6341 — Xml schema collection referenced by column '%.*ls' of table variable '%.*ls' has been dropped or altered during the execution of the batch. Please re-…
- 6342 — Cannot create primary xml, selective xml or spatial index '%.*ls' on table '%.*ls', column '%.*ls', because the column is computed.
- 6343 — Cannot create secondary xml or secondary selective xml index '%.*ls' without a USING XML INDEX clause.
- 6344 — The primary xml index '%.*ls' does not exist on table '%.*ls' column '%.*ls'.
- 6345 — The sparse column set '%.*ls' in the table '%.*ls' cannot be indexed by an XML index.
- 6346 — Cannot convert a primary XML index to a secondary XML index using the DROP_EXISTING option. '%.*ls' is a primary XML index.
- 6347 — Specified collection '%.*ls' cannot be altered because it does not exist or you do not have permission.
- 6348 — Specified collection '%.*ls' cannot be created because it already exists or you do not have permission.
- 6350 — The definition for xml schema collection '%.*ls' has changed.
- 6351 — The xml schema collection for return parameter of module '%.*ls' has been altered while the batch was being executed. Please re-run the batch.
- 6352 — Invalid parameter specified. XML Schema Collections can only be created from a string literal, or from a variable typed as a string or untyped XML.
- 6353 — Serialization of built-in schemata is not supported.
- 6354 — Target string size is too small to represent the XML instance
- 6355 — Conversion of one or more characters from XML to target collation impossible
- 6356 — Failed to load DLL. Make sure xmlrw.dll exists in the SQL Server installation.
- 6357 — Internal error: cannot locate CreateInfoSetReaderEx in xmlrw.dll. You may have an incorrect version of xmlrw.dll.
- 6358 — %d is not a valid style number when converting to XML.
- 6359 — Parsing XML with internal subset DTDs not allowed. Use CONVERT with style option 2 to enable limited internal subset DTD support.
- 6360 — %d is not a valid style number when converting from XML.
- 6361 — Invalid null parameter specified. XML Schema Collections can only be created from a non-null value.
- 6362 — Alter schema collection cannot be performed because the current schema has a lax wildcard or an element of type xs:anyType.
- 6363 — ALTER SCHEMA COLLECTION failed. It cannot be performed on a schema collection that allows laxly validated content and is schema bound. Remove the sche…
- 6364 — ALTER SCHEMA COLLECTION failed. Revalidation of XML columns in table '%.*ls' did not succeed due to the following reason: '%.*ls'. Either the schema o…
- 6365 — An XML operation resulted an XML data type exceeding 2GB in size. Operation aborted.
- 6366 — Invalid type for element '%s'. SQL Server does not permit the built-in XML Schema types 'ID' and 'IDREF' or types derived from them to be used as the …
- 6367 — XSD data type '%.*ls' is not allowed for selective XML index '%.*ls'.
- 6368 — It is not allowed to specify an XSD type for selective XML index '%.*ls' because the column '%.*ls' of table '%.*ls' is associated with an XML Schema …
- 6369 — MAX_LENGTH option for selective XML index '%.*ls' can be specified only for the types that support maxLength facet.
- 6370 — MAX_LENGTH option is not allowed in combination with 'node()' for selective XML index '%.*ls'.
- 6371 — The same name cannot be assigned to more than one path for selective XML index '%.*ls'.
- 6372 — The same path expression cannot be mapped twice using SQL data types for selective XML index '%.*ls'.
- 6373 — The expression specified for path '%.*ls' is not allowed for selective XML index '%.*ls'. It is only allowed to index simple path expressions without …
- 6374 — Specifying path which contains '%.*ls' is not allowed for selective XML index '%.*ls'.
- 6375 — The data type '%.*ls' is not allowed for selective XML index '%.*ls'.
- 6376 — For selective XML index '%.*ls', MAX_LENGTH optimization hint cannot be specified if length or maxLength facet is specified in schema for an element.
- 6377 — Specifying a path which contains '*' in the last step is not allowed for selective XML index '%.*ls'.
- 6378 — Table '%.*ls' needs to have a clustered primary key with less than %d columns in it in order to create a selective XML index on it.
- 6379 — selective XML index '%.*ls' already exists on column '%.*ls' in table '%.*ls'. Multiple selective XML indexes per column are not allowed.
- 6380 — Path '%.*ls'. Multiple values found when SINGLETON option is specified for selective XML index '%.*ls'.
- 6381 — Could not find path '%.*ls' in selective XML index '%.*ls'.
- 6382 — Could not find selective XML index named '%.*ls' on table '%.*ls'
- 6383 — For selective XML index '%.*ls', SINGLETON option can be specified only for untyped XML.
- 6384 — It is not allowed to specify a path which contains '*' only for the URI or only for the name of the node for selective XML index '%.*ls'.
- 6385 — The selective XML index '%.*ls' does not exist on table '%.*ls' column '%.*ls'.
- 6386 — Cannot convert a selective XML index to a secondary selective XML index using the DROP_EXISTING option. '%.*ls' is a selective XML index.
- 6387 — You cannot remove all paths for selective XML index '%.*ls'. A selective XML index must have at least one path specified.
- 6388 — Version of Selective DG stored in database is different than version of Selective DG on server for index '%.*ls'.
- 6389 — Inserted value exceeded maxlength %d for path '%.*ls' for selective XML index '%.*ls'.
- 6390 — ALTER SCHEMA COLLECTION failed because path '%.*ls' indexed with selective XML index '%.*ls' on table '%.*ls' would be invalidated. Either the schema …
- 6391 — Path '%.*ls' is promoted to a type that is invalid for use as a key column in a secondary selective XML index.
- 6392 — It is not allowed to create secondary selective XML index on the path '%.*ls' because 'node()' is specified.
- 6393 — The same path expression cannot be mapped twice with same XSD types for selective XML index '%.*ls'.
- 6394 — Found non leaf element indexed for the value with path '%.*ls' for selective XML index '%.*ls'.
- 6395 — The maximum key length is %d bytes. The secondary selective XML index '%.*ls' over path '%.*ls' has maximum length of %d bytes. For some combination o…
- 6396 — The number of promoted paths for selective XML index '%.*ls' exceeds the maximum of %d.
- 6397 — Path '%.*ls' specified for selective XML index '%.*ls' is too deep. The maximum allowed depth is %d levels.
- 6398 — The MAXLENGTH option value specified for the path '%.*ls' for Selective XML Index '%.*ls' is not allowed. The value should be in the range %d - %d.
- 6399 — The XML path '%.*ls' of selective XML index '%.*ls' cannot be dropped because it is used by secondary selective XML Index '%.*ls'.
- 6401 — Cannot roll back %.*ls. No transaction or savepoint of that name was found.
- 6500 — %ls failed because method '%ls' of class '%ls' in assembly '%ls' returns %ls, but CLR Triggers must return void.
- 6501 — %s ASSEMBLY failed because it could not open the physical file '%.*ls': %ls.
- 6502 — %s ASSEMBLY failed because it could not read from the physical file '%.*ls': %ls.
- 6503 — Assembly '%.*ls' was not found in the SQL catalog.
- 6504 — The value returned from %.*ls.%.*ls is not allowed to be NULL.
- 6505 — Could not find Type '%s' in assembly '%s'.
- 6506 — Could not find method '%s' for type '%s' in assembly '%s'
- 6507 — Failed to open malformed assembly '%ls' with HRESULT 0x%x.
- 6508 — Could not find field '%s' for type '%s' in assembly '%s'.
- 6509 — An error occurred while gathering metadata from assembly '%ls' with HRESULT 0x%x.
- 6510 — This functionality requires .NET Framework 4. Please install .NET Framework 4 to use this functionality.
- 6511 — Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You may fix the problem and try again later.
- 6512 — Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You need to restart SQL Server to use CLR integration features.
- 6513 — Failed to initialize the Common Language Runtime (CLR) %ls due to memory pressure. This is probably due to memory pressure in the MemToLeave region of…
- 6514 — Cannot use '%s' column in the result table of a streaming user-defined function (column '%.*ls').
- 6515 — Schema collection database '%.*ls' does not exist or you do not have permission.
- 6516 — There is no collection '%.*ls' in metadata '%.*ls'.
- 6517 — Failed to create AppDomain "%.*ls". %.*ls
- 6518 — Could not open system assembly ''%.*ls'': %ls.
- 6519 — Type '%.*ls' is not yet supported for CLR operations.
- 6520 — A .NET Framework error occurred during statement execution.
- 6521 — A .NET Framework error occurred during statement execution: %.*ls.
- 6522 — A .NET Framework error occurred during execution of user-defined routine or aggregate "%.*ls": %ls.
- 6523 — Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is static.
- 6524 — Cannot use computed column in the result table of a streaming user-defined function (column '%.*ls').
- 6525 — Cannot use '%s' constraint in the result table of a streaming user-defined function.
- 6526 — Cannot use '%s' constraint in the result table of a streaming user-defined function (column '%.*ls').
- 6527 — .NET Framework runtime has been stopped.
- 6528 — Assembly '%.*ls' was not found in the SQL catalog of database '%.*ls'.
- 6529 — ALTER ASSEMBLY failed because the identity of referenced assembly '%.*ls' has changed. Make sure the version, name, and public key have not changed.
- 6530 — Cannot perform alter on '%.*ls' because it is an incompatible object type.
- 6531 — %ls failed because the function '%ls' of class '%ls' of assembly '%.*ls' takes one or more parameters but CLR Triggers do not accept parameters.
- 6532 — .NET Framework execution was aborted by escalation policy because of out of memory. %.*ls
- 6533 — AppDomain %.*ls was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while accessing a critical res…
- 6534 — AppDomain %.*ls was unloaded by escalation policy to ensure the consistency of your application. Application failed to release a managed lock. %.*ls
- 6535 — .NET Framework execution was aborted. Another query caused the AppDomain %.*ls to be unloaded. %.*ls
- 6536 — A fatal error occurred in the .NET Framework common language runtime. SQL Server is shutting down. If the error recurs after the server is restarted, …
- 6537 — The .NET Framework common language runtime was shut down by user code, such as in a user-defined function or CLR type. SQL Server is shutting down. En…
- 6538 — .NET Framework execution was aborted because of stack overflow. %.*ls
- 6539 — Invalid serialization format (Format.Unknown) for type '%.*ls.%.*ls'.
- 6540 — The assembly name '%.*ls' being registered has an illegal name that duplicates the name of a system assembly.
- 6541 — ALTER ASSEMBLY failed because assembly '%.*ls' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to remove extra files.
- 6542 — Can not create object because %ls is a generic type.
- 6543 — .NET Framework execution was aborted. The UDP/UDF/CLR type did not end thread affinity.
- 6544 — %s ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' is malformed or not a pure .NET assembly. %.*ls
- 6545 — Enabling of execution statistics SET options is not allowed from within CLR procedure or function.
- 6546 — Could not impersonate the execution context during the execution of '%.*ls'.
- 6547 — An error occurred while getting method, property or field information for "%ls" of class "%ls" in assembly "%.*ls".
- 6548 — CREATE ASSEMBLY failed because the assembly references assembly '%.*ls', which is owned by another user.
- 6549 — A .NET Framework error occurred during execution of user defined routine or aggregate '%.*ls': %ls. User transaction, if any, will be rolled back.
- 6550 — %s failed because parameter counts do not match.
- 6551 — %s for "%.*ls" failed because T-SQL and CLR types for return value do not match.
- 6552 — %s for "%.*ls" failed because T-SQL and CLR types for parameter "%.*ls" do not match.
- 6553 — %s failed because of an invalid .NET Framework calling convention. Use the default .NET Framework calling convention.
- 6554 — SQL assembly name '%.*ls', and .NET Framework assembly name '%.*ls' do not match. Assembly names must match.
- 6555 — Assembly '%.*ls' already exists for owner '%.*ls' in database '%.*ls'.
- 6556 — %s failed because it could not find type '%s' in assembly '%s'.
- 6557 — %s failed because type '%s' does not conform to %s specification due to field '%s'.
- 6558 — %s failed because type '%s' does not conform to %s specification due to method '%s'.
- 6559 — Could not find type ID %d in database %.*ls. This is due to a schema inconsistency.
- 6560 — Assembly "%.*ls" is a system assembly. This operation is permitted only with user assemblies.
- 6561 — Could not find file '%s' in directory '%s%s'.
- 6562 — Version mismatch between files '%ls' (%d.%d.%d) and '%ls' (%d.%d.%d).
- 6563 — Method, property or field '%ls' in class '%ls' in assembly '%.*ls' has invalid return type.
- 6564 — The method '%ls' in class '%ls' in assembly '%.*ls' has some invalid parameter declaration for parameter number %d.
- 6565 — %s ASSEMBLY failed because the assembly source parameter %d is not a valid assembly.
- 6566 — %s ASSEMBLY failed because the assembly source parameter %d is not a valid expression.
- 6567 — %s failed because a CLR Procedure may only be defined on CLR methods that return either SqlInt32, System.Int32, System.Nullable<System.Int32>, void.
- 6568 — A .NET Framework error occurred while getting information from class "%.*ls" in assembly "%.*ls": %ls.
- 6569 — '%.*ls' failed because parameter %d is not allowed to be null.
- 6570 — Method '%ls' of class '%ls' in assembly '%.*ls' is generic. Generic methods are not supported.
- 6571 — Class '%ls' in assembly '%.*ls' is generic. Generic types are not supported.
- 6572 — More than one method, property or field was found with name '%ls' in class '%ls' in assembly '%.*ls'. Overloaded methods, properties or fields are not…
- 6573 — Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is not static.
- 6574 — Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is not public.
- 6575 — Assembly names should be less than %d characters. Assembly name '%.*ls' is too long.
- 6576 — Type '%ls' in assembly '%ls' is not public.
- 6577 — CREATE TYPE failed because type '%s' does not conform to CLR type specification due to interface '%s'.
- 6578 — Invalid attempt to continue operation after a severe error.
- 6579 — Alter assembly from '%ls' to '%ls' is not a compatible upgrade.
- 6580 — Declarations do not match for parameter %d. .NET Framework reference and T-SQL OUTPUT parameter declarations must match.
- 6581 — Could not find assembly '%.*ls' in directory '%.*ls'.
- 6582 — Assembly '%.*s' is not visible for creating SQL objects. Use ALTER ASSEMBLY to change the assembly visibility.
- 6583 — Assembly '%.*s' cannot be used for creating SQL objects because it is a system assembly.
- 6584 — Property or field '%ls' for type '%ls' in assembly '%ls' is not static
- 6585 — Could not impersonate the client during assembly file operation.
- 6586 — Assembly '%.*ls' could not be installed because existing policy would keep it from being used.
- 6587 — Assembly reference '%ls' was redirected by external policy to '%ls'
- 6588 — Assembly file operations are not allowed for logins that use integration authentication activated by SETUSER.
- 6589 — DROP ASSEMBLY failed because the specified assemblies are referenced by assembly '%ls'.
- 6590 — DROP ASSEMBLY failed because '%ls' is referenced by object '%ls'.
- 6591 — %s for "%.*ls" failed because first parameter of "%.*ls" method must be of type System.Object.
- 6592 — Could not find property or field '%ls' for type '%ls' in assembly '%ls'.
- 6593 — Property or field '%ls' for type '%ls' in assembly '%ls' is static.
- 6594 — Could not read from property '%ls' for type '%ls' in assembly '%ls' because it does not have a get accessor.
- 6595 — Could not assign to property '%ls' for type '%ls' in assembly '%ls' because it is read only.
- 6596 — %s ASSEMBLY failed because assembly '%ls' is a system assembly. Consider creating a user assembly to wrap desired functionality.
- 6597 — CREATE %s failed.
- 6598 — DROP ASSEMBLY failed because '%ls' is referenced by CLR type '%ls'.
- 6599 — Found an empty native serialization class '%.*ls'. Empty native serialization classes are not allowed.
- 6600 — XML error: %.*ls
- 6601 — The XML parse error 0x%x occurred on line number %d, near the XML text "%.*ls".
- 6602 — The error description is '%.*ls'.
- 6603 — XML parsing error: %.*ls
- 6605 — %.*ls: Failed to obtain an IPersistStream interface on the XML text.
- 6607 — %.*ls: The value supplied for parameter number %d is invalid.
- 6608 — Failed to instantiate class "%ls". Verify that Msxmlsql.dll exists in the SQL Server installation.
- 6609 — Invalid data type for the column "%ls". Allowed data types are CHAR/VARCHAR, NCHAR/NVARCHAR, TEXT/NTEXT, and XML.
- 6610 — Failed to load Msxmlsql.dll.
- 6611 — The XML data type is damaged.
- 6613 — Specified value '%ls' already exists.
- 6621 — XML encoding or decoding error occurred with object name '%.*ls'.
- 6622 — Invalid data type for column "%ls". The data type cannot be text, ntext, image, binary, varchar(max), nvarchar(max), varbinary(max), or xml.
- 6623 — Column '%ls' contains an invalid data type. Valid data types are char, varchar, nchar, and nvarchar.
- 6624 — XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents.
- 6625 — Could not convert the value for OPENXML column '%ls' to sql_variant data type. The value is too long. Change the data type of this column to text, nte…
- 6626 — Unexpected end of data stream.
- 6627 — The size of the data chunk that was requested from the stream exceeds the allowed limit.
- 6628 — %.*ls can only process untyped XML. Cast the input value to XML or to a string type.
- 6629 — The result of the column expression for column "%ls" is not compatible with the requested type "XML". The result must be an element, text node, commen…
- 6630 — Element-centric mapping must be used with OPENXML when one of the columns is of type XML.
- 6631 — The requested OpenXML document is currently in use by another thread, and cannot be used.
- 6632 — Invalid data type for the column "%ls". CLR types cannot be used in an OpenXML WITH clause.
- 6633 — The version of MSXMLSQL.DLL that was found is older than the minimum required version. Found version "%d.%d.%d". Require version "%d.%d.%d".
- 6634 — OpenXML cannot be used as the target of a DML or OUTPUT INTO operation.
- 6635 — The compressed showplan xml stream is corrupted.
- 6636 — Unable to read the compressed showplan xml because it was made with a newer version of SQL server.
- 6637 — The compressed xml stream is corrupted.
- 6700 — XQuery: The ' %ls' operation is not supported.
- 6701 — The version of the XML index that you are trying to use is not supported anymore. Please drop and recreate the XML index.
- 6716 — XML Node ID is invalid. Re-build the database if the problem persists.
- 6717 — XQuery: The document tree is too deep. If the problem persists you must simplify the XML hierarchy.
- 6718 — XQuery: Invalid ordpath string: "%s"
- 6739 — XQuery: SQL type '%s' is not supported in XQuery.
- 6743 — XQuery: The maximum allowed depth in XML instances is %d levels. One of the paths in the query tries to access nodes at a lower level.
- 6744 — XQuery: One of the paths specified in the query is too deep. The maximum allowed depth is %d levels.
- 6745 — XQuery: Internal compiler error.
- 6800 — FOR XML AUTO requires at least one table for generating XML tags. Use FOR XML RAW or add a FROM clause with a table name.
- 6801 — FOR XML EXPLICIT requires at least three columns, including the tag column, the parent column, and at least one data column.
- 6802 — FOR XML EXPLICIT query contains the invalid column name '%.*ls'. Use the TAGNAME!TAGID!ATTRIBUTENAME[!..] format where TAGID is a positive integer.
- 6803 — FOR XML EXPLICIT requires the first column to hold positive integers that represent XML tag IDs.
- 6804 — FOR XML EXPLICIT requires the second column to hold NULL or nonnegative integers that represent XML parent tag IDs.
- 6805 — FOR XML EXPLICIT stack overflow occurred. Circular parent tag relationships are not allowed.
- 6806 — Undeclared tag ID %d is used in a FOR XML EXPLICIT query.
- 6807 — Undeclared parent tag ID %d is used in a FOR XML EXPLICIT query.
- 6808 — XML tag ID %d could not be added. The server memory resources may be low.
- 6809 — Unnamed tables cannot be used as XML identifiers as well as unnamed columns cannot be used for attribute names. Name unnamed columns/tables using AS i…
- 6810 — Column name '%.*ls' is repeated. The same attribute cannot be generated more than once on the same XML tag.
- 6811 — FOR XML is incompatible with COMPUTE expressions. Remove the COMPUTE expression.
- 6812 — XML tag ID %d that was originally declared as '%.*ls' is being redeclared as '%.*ls'.
- 6813 — FOR XML EXPLICIT cannot combine multiple occurrences of ID, IDREF, IDREFS, NMTOKEN, and/or NMTOKENS in column name '%.*ls'.
- 6814 — In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS require attribute names in '%.*ls'.
- 6815 — In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be hidden in '%.*ls'.
- 6816 — In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be generated as CDATA, XML, or XMLTEXT in '%.*ls'.
- 6817 — FOR XML EXPLICIT cannot combine multiple occurrences of ELEMENT, XML, XMLTEXT, and CDATA in column name '%.*ls'.
- 6819 — The FOR XML clause is not allowed in a %ls statement.
- 6820 — FOR XML EXPLICIT requires column %d to be named '%ls' instead of '%.*ls'.
- 6821 — GROUP BY and aggregate functions are currently not supported with FOR XML AUTO.
- 6824 — In the FOR XML EXPLICIT clause, mode '%.*ls' in a column name is invalid.
- 6825 — ELEMENTS option is only allowed in RAW, AUTO, and PATH modes of FOR XML.
- 6826 — Every IDREFS or NMTOKENS column in a FOR XML EXPLICIT query must appear in a separate SELECT clause, and the instances must be ordered directly after …
- 6827 — FOR XML EXPLICIT queries allow only one XMLTEXT column per tag. Column '%.*ls' declares another XMLTEXT column that is not permitted.
- 6828 — XMLTEXT column '%.*ls' must be of a string data type or of type XML.
- 6829 — FOR XML EXPLICIT and RAW modes currently do not support addressing binary data as URLs in column '%.*ls'. Remove the column, or use the BINARY BASE64 …
- 6830 — FOR XML AUTO could not find the table owning the following column '%.*ls' to create a URL address for it. Remove the column, or use the BINARY BASE64 …
- 6831 — FOR XML AUTO requires primary keys to create references for '%.*ls'. Select primary keys, or use BINARY BASE64 to obtain binary data in encoded form i…
- 6832 — FOR XML AUTO cannot generate a URL address for binary data if a primary key is also binary.
- 6833 — Parent tag ID %d is not among the open tags. FOR XML EXPLICIT requires parent tags to be opened first. Check the ordering of the result set.
- 6834 — XMLTEXT field '%.*ls' contains an invalid XML document. Check the root tag and its attributes.
- 6835 — FOR XML EXPLICIT field '%.*ls' can specify the directive HIDE only once.
- 6836 — FOR XML EXPLICIT requires attribute-centric IDREFS or NMTOKENS field '%.*ls' to precede element-centric IDREFS/NMTOKEN fields.
- 6838 — Attribute-centric IDREFS or NMTOKENS field not supported on tags having element-centric field '%.*ls' of type TEXT/NTEXT or IMAGE. Either specify ELEM…
- 6839 — FOR XML EXPLICIT does not support XMLTEXT field on tag '%.*ls' that has IDREFS or NMTOKENS fields.
- 6840 — Neither XMLDATA nor XMLSCHEMA supports namespace elements or attributes such as '%.*ls'. Run the SELECT FOR XML statement without it or remove the nam…
- 6841 — FOR XML could not serialize the data for node '%.*ls' because it contains a character (0x%04X) which is not allowed in XML. To retrieve this data usin…
- 6842 — Could not serialize the data for node '%.*ls' because it contains a character (0x%04X) which is not allowed in XML. To retrieve this data convert it t…
- 6843 — FOR XML EXPLICIT: XML data types and CLR types cannot be processed as CDATA in column name '%.*ls'. Consider converting XML to a string type. Consider…
- 6844 — Two (or more) elements named '%.*ls' are of different types and not direct siblings in the same level.
- 6845 — Two (or more) elements named '%.*ls' are optional in the same level. Consider making them direct siblings or map NULL to xsi:nil
- 6846 — XML name space prefix '%.*ls' declaration is missing for FOR XML %.*ls name '%.*ls'.
- 6847 — The column '%.*ls' is of type sql_variant, which is not supported in attribute-centric FOR XML, with XML Schema.
- 6848 — XMLDATA does not support the mapping of the type of column '%.*ls' to an XDR type. Please use XMLSCHEMA instead for AUTO and RAW mode.
- 6849 — FOR XML PATH error in column '%.*ls' - '//' and leading and trailing '/' are not allowed in simple path expressions.
- 6850 — %.*ls name '%.*ls' contains an invalid XML identifier as required by FOR XML; '%c'(0x%04X) is the first character at fault.
- 6851 — Column '%.*ls' has invalid data type for attribute-centric XML serialization in FOR XML PATH.
- 6852 — Attribute-centric column '%.*ls' must not come after a non-attribute-centric sibling in XML hierarchy in FOR XML PATH.
- 6853 — Column '%.*ls': the last step in the path can't be applied to XML data type or CLR type in FOR XML PATH.
- 6854 — Invalid column alias '%.*ls' for formatting column as XML processing instruction in FOR XML PATH - it must be in 'processing-instruction(target)' form…
- 6855 — Inline schema is not supported with FOR XML PATH.
- 6856 — FOR XML row XML tag name contains an invalid XML identifier; '%c'(0x%04X) is the first character at fault.
- 6857 — FOR XML root XML tag name contains an invalid XML identifier; '%c'(0x%04X) is the first character at fault.
- 6858 — XML schema URI contains character '%c'(0x%04X) which is not allowed in XML.
- 6859 — Row tag name is only allowed with RAW or PATH mode of FOR XML.
- 6860 — FOR XML directive XMLDATA is not allowed with ROOT directive or row tag name specified.
- 6861 — Empty root tag name can't be specified with FOR XML.
- 6862 — Empty FOR XML target inline schema URI is not allowed.
- 6863 — Row tag omission (empty row tag name) is not compatible with XMLSCHEMA FOR XML directive.
- 6864 — Row tag omission (empty row tag name) cannot be used with attribute-centric FOR XML serialization.
- 6865 — FOR XML does not support CLR types - cast CLR types explicitly into one of the supported types in FOR XML queries.
- 6866 — Use of a system reserved XML schema URI is not allowed.
- 6867 — 'xmlns' is invalid in XML tag name in FOR XML PATH, or when WITH XMLNAMESPACES is used with FOR XML.
- 6868 — The following FOR XML features are not supported with WITH XMLNAMESPACES list: EXPLICIT mode, XMLSCHEMA and XMLDATA directives.
- 6869 — Attempt to redefine namespace prefix '%.*ls'
- 6870 — Prefix '%.*ls' used in WITH XMLNAMESPACES clause contains an invalid XML identifier. '%c'(0x%04X) is the first character at fault.
- 6871 — Prefix '%.*ls' used in WITH XMLNAMESPACES is reserved and cannot be used as a user-defined prefix.
- 6872 — XML namespace prefix 'xml' can only be associated with the URI http://www.w3.org/XML/1998/namespace . This URI cannot be used with other prefixes.
- 6873 — Redefinition of 'xsi' XML namespace prefix is not supported with ELEMENTS XSINIL option of FOR XML.
- 6874 — Empty URI is not allowed in WITH XMLNAMESPACES clause.
- 6875 — URI '%.*ls' used in WITH XMLNAMESPACES is invalid. '%c'(0x%04X) is the first character at fault.
- 6876 — URI used in WITH XMLNAMESPACES is too long. The maximum length is %d characters.
- 6877 — Empty namespace prefix is not allowed in WITH XMLNAMESPACES clause.
- 6878 — FORXML XMLSCHEMA cannot be used with a typed XML column whose schema collection is empty.
- 6879 — 'xml' is an invalid XML processing instruction target. Possible attempt to construct XML declaration using XML processing instruction constructor. XML…
- 6901 — XML Validation: XML instance must be a document.
- 6902 — XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support the use of the pattern or enumeration facet on lists of type …
- 6903 — XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support inclusion of ID, QName, or list of QName among the member typ…
- 6904 — XML Validation: Found duplicate attribute '%s'. %S_MSG %s
- 6905 — XML Validation: Attribute '%s' is not permitted in this context. %S_MSG %s
- 6906 — XML Validation: Required attribute '%s' is missing. %S_MSG %s
- 6907 — Namespace URI too long: '%.*ls'.
- 6908 — XML Validation: Invalid content. Expected element(s): %s. %S_MSG %s
- 6909 — XML Validation: Text node is not allowed at this location, the type was defined with element only content or with simple content. %S_MSG %s
- 6910 — XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support restriction of union types.
- 6911 — XML Validation: Found duplicate element '%s' in all content model. %S_MSG %s
- 6912 — XML Validation: Element '%s' found in text only content model. %S_MSG %s
- 6913 — XML Validation: Declaration not found for element '%s'. %S_MSG %s
- 6914 — XML Validation: Type definition for type '%s' was not found, type definition is required before use in a type cast. %S_MSG %s
- 6915 — Element or attribute name too long: '%.*ls'.
- 6916 — XML Validation: The content model of type or model group '%s' is ambiguous and thus violates the unique particle attribution constraint. Consult SQL S…
- 6917 — XML Validation: Element '%ls' may not have xsi:nil="true" because it was not defined as nillable or because it has a fixed value constraint. %S_MSG %l…
- 6918 — XML Validation: Element '%s' must not have character or element children, because xsi:nil was set to true. %S_MSG %s
- 6919 — XML Validation: The type of element '%s' is abstract. Instantiation requires the use of xsi:type to specify a non-abstract type. %S_MSG %s
- 6920 — Invalid definition for type '%ls'. Cannot specify use="prohibited" for attribute '%ls' because there is no corresponding attribute in the base type.
- 6921 — XML Validation: Element or attribute '%s' was defined as fixed, the element value has to be equal to value of 'fixed' attribute specified in definitio…
- 6922 — XML Validation: Not able to resolve namespace for prefix:'%.*ls'
- 6923 — XML Validation: Unexpected element(s): %s. %S_MSG %s
- 6924 — XML Validation: Text '%.*ls' found in attribute-only content model. %S_MSG %s
- 6925 — Invalid definition for element '%ls'. SQL Server does not currently permit additions to existing substitution groups via ALTER XML SCHEMA COLLECTION.
- 6926 — XML Validation: Invalid simple type value: '%s'. %S_MSG %s
- 6927 — XML Validation: Invalid simple type value: '%ls'.
- 6928 — XML Validation: XML instances of the content model of type or model group '%ls' can be validated in multiple ways and are not supported.
- 6929 — XML Validation: Invalid QName for xsi:type attribute '%.*ls'.
- 6930 — XML Validation: ID constraint check failed. Found attribute named '%.*ls' with duplicate ID value '%.*ls'. %S_MSG %s
- 6931 — XML Validation: IDREF constraint check failed. Found attribute named '%.*ls' with reference to ID value '%.*ls', which does not exist
- 6932 — Invalid definition for element or attribute '%s'. Value constraints on components of type ID are not allowed.
- 6933 — XML Validation: Invalid simple type operation, inserting into simple type is not permitted. %S_MSG %s
- 6934 — XML Validation: Element '%s' requires substitution, because it was defined as abstract. %S_MSG %s
- 6935 — XML Validation: ID or IDREF attribute exceeded the allowed maximum length. %S_MSG %s
- 6936 — XML Validation: Invalid cast for element '%s' from type '%s' to type '%s'. %S_MSG %s
- 6937 — XML Validation: The canonical form of the value '%ls' is not valid according to the specified type. This can result from the use of pattern facets on …
- 6938 — XML Validation: The canonical form of the value '%ls' is not valid according to the specified type. This can result from the use of pattern facets on …
- 6939 — XML Validation: The element '%ls' is mixed content with a fixed value and therefore not allowed to have element content. %S_MSG %ls
- 6940 — Invalid component named '%s' found in global scope. Only elements, attributes, types and groups can be defined in global context
- 6941 — Invalid type definition for type '%s', types with complex content can only be derived from base types which have complex content
- 6942 — Invalid type definition for type '%s', types with simple content can only be derived from base types which have simple content
- 6943 — Invalid type definition for type '%s', the derivation was illegal because 'final' attribute was specified on the base type
- 6944 — Invalid type definition for type '%s', '%s' facet is not restricting the value space
- 6945 — Invalid facet value for facet '%s' in type definition '%s'
- 6946 — Invalid type definition for type '%s', 'minLength' can not be greater than 'maxLength'
- 6947 — XML Validation: Multiple ID attributes found on a single element. %S_MSG %s
- 6948 — Invalid type definition for type '%s', 'minLength' can not be greater than 'Length'
- 6949 — Invalid type definition for type '%s', 'Length' can not be greater than 'maxLength'
- 6950 — Invalid type definition for type '%s', 'fractionDigits' can not be greater than 'totalDigits'
- 6951 — Invalid type definition for type '%s', 'minInclusive' must be less than or equal to 'maxInclusive' and less than 'maxExclusive'
- 6952 — Invalid type definition for type '%s', 'minExclusive' must be less than or equal to 'maxExclusive' and less than 'maxInclusive'
- 6953 — Invalid type definition for type '%s', recursive type definitions are not allowed
- 6954 — Invalid group definition for group '%s', recursive group definitions are not allowed
- 6955 — Invalid attribute definition for attribute '%s', attributes type has to be simple type
- 6956 — Invalid type definition for type '%s', fixed facet '%s' can not be redefined to a different value.
- 6957 — Invalid element definition, element '%s' is not valid derivation of element '%s'
- 6958 — Invalid definition for type '%s'. An 'all' group may not appear as the child or parent of any other model group, it must have minOccurs = maxOccurs = …
- 6959 — Invalid definition, top level group definitions can not have model groups as siblings
- 6960 — Component '%s' is outside of allowed range. Maximum for 'fractionDigits' is 10 and maximum number of digits for non fractional part is 28
- 6961 — The system limit on the number of XML types has been reached. Redesign your database to use fewer XML types.
- 6962 — 'default' and 'fixed' values are not allowed on element of this type: '%s'
- 6963 — 'Default' or 'Fixed' value is longer than allowed, maximum length allowed is 4000 characters : '%s'
- 6964 — Facet value is longer than allowed, maximum length allowed is 4000 characters : '%s'
- 6965 — XML Validation: Invalid content. Expected element(s): %s. Found: element '%s' instead. %S_MSG %s.
- 6966 — Warning: Type '%s' is restricted by a facet '%s' that may impede full round-tripping of instances of this type
- 6967 — Invalid type definition for type '%s'. The base and derived types must have the same value for 'mixed' unless deriving by restriction, in which case '…
- 6968 — Invalid type definition for type '%s'. Complex types cannot restrict simple types
- 6969 — ID/IDREF validation consumed too much memory. Try reducing the number of ID and IDREF attributes. Rearranging the file so that elements with IDREF att…
- 6970 — Invalid type definition for type '%s'. No type may have more than one attribute of any type derived from ID.
- 6971 — Invalid type definition for type '%s'. Type contains attribute '%s' which is not allowed in base type.
- 6972 — Invalid redefinition of attribute '%s' in type '%s'. Must be of a type which is a valid restriction of the corresponding attribute in the base type.
- 6973 — Invalid redefinition of attribute '%s' in type '%s'. Must be required in the derived type if it is required in the base type.
- 6974 — Invalid redefinition of attribute '%s' in type '%s'. Must be prohibited in the derived type if it is prohibited in the base type.
- 6975 — Invalid redefinition of attribute '%s' in type '%s'. Must be fixed to the same value as in the derived type.
- 6976 — Invalid redefinition of attribute '%s' in type '%s'. Derivation by extension may not redefine attributes.
- 6977 — Invalid member type '%s' in union type '%s'. Unions may not have complex member types.
- 6978 — Invalid item type for list type '%s'. The item type of a list may not itself be a list, and types derived from ID may not be used as item types in thi…
- 6979 — Invalid restriction for type '%s'. The element in the restricted type must have the same name as and a more restrictive type than the corresponding el…
- 6980 — Invalid restriction for type '%s'. The particle in the restricted type may not have an occurrence range more permissive than that of the corresponding…
- 6981 — Invalid restriction for type '%s'. The element in the restricted type may not be nillable if the corresponding element in the base type is not.
- 6982 — Invalid restriction for type '%s'. The element in the restricted type must be fixed to the same value as the corresponding element in the derived type…
- 6983 — Invalid restriction for type '%s'. The element in the restricted type may not have a 'block' value more permissive than the corresponding element in t…
- 6984 — Invalid restriction for type '%s'. The element in the restricted type must be in one of the namespaces allowed by the base type's wildcard.
- 6985 — Invalid restriction for type '%s'. The Wildcard in the restricted type must be a valid subset of the corresponding wildcard in the base type, and the …
- 6986 — Invalid restriction for type '%s'. The effective total range of the model group in the restricted type must be a valid restriction of the occurrence r…
- 6987 — Invalid restriction for type '%s'. An 'all' particle may be restricted only by 'all', 'element', or 'sequence'.
- 6988 — Invalid restriction for type '%s'. A 'choice' particle may be restricted only by 'element', 'choice', or 'sequence'.
- 6989 — Invalid restriction for type '%s'. A 'sequence' particle may be restricted only by 'element' or 'sequence'.
- 6990 — Invalid restriction for type '%s'. Invalid model group restriction.
- 6991 — Invalid restriction for type '%s'. If the base type has empty content, then the derived type must as well, and if the derived type has empty content, …
- 6992 — The content model of type '%s' contains two elements with the same name '%s' and different types, nullability, or value constraints.
- 6993 — Value constraint on use of attribute '%s' must be consistent with value constraint on its declaration.
- 6994 — Invalid restriction for type '%s'. The attribute wildcard in the restricted type must be a valid subset of the corresponding attribute wildcard in the…
- 6995 — Invalid definition for type '%s'. SQL Server does not permit the built-in XML Schema types 'ID' and 'IDREF' or types derived from them to be used as t…
- 6996 — Invalid type definition for type '%s'. A type may not have both 'minInclusive' and 'minExclusive' or 'maxInclusive' and 'maxExclusive' facets.
- 6997 — Invalid definition for element '%s'. An element which has a fixed value may not also be nillable.
- 6998 — Invalid type definition: Type or content model '%s' is too complicated. It may be necessary to reduce the number of enumerations or the size of the co…
- 6999 — Invalid definition for element or attribute '%s'. Value constraints on components of type QName are not supported in this release.
- 7000 — OPENXML document handle parameter must be of data type int.
- 7001 — OPENXML flags parameter must be of data type int.
- 7002 — OPENXML XPath must be of a string data type, such as nvarchar.
- 7003 — Only one OPENXML column can be of type %ls.
- 7004 — OPENXML does not support retrieving schema from remote tables, as in '%.*ls'.
- 7005 — OPENXML requires a metaproperty namespace to be declared if 'mp' is used for another namespace in sp_xml_preparedocument.
- 7006 — OPENXML encountered a problem identifying the metaproperty namespace prefix. Consider removing the namespace parameter from the corresponding sp_xml_p…
- 7007 — OPENXML encountered unknown metaproperty '%.*ls'.
- 7008 — The OPENXML EDGETABLE is incompatible with the XMLTEXT OVERFLOW flag.
- 7009 — OPENXML allows only one metaproperty namespace prefix declaration in sp_xml_preparedocument.
- 7101 — You need an active user transaction in order to use text pointers for a table with the option "text in row" set to ON.
- 7102 — Internal Error: Text manager cannot continue with current statement. Run DBCC CHECKTABLE.
- 7104 — Offset or size of data type is not valid. Data type must be of type int or smallint.
- 7105 — 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…
- 7106 — Internal error: An attempt was made to update a LOB data type using a read-only text pointer.
- 7107 — You can have only 1,024 in-row text pointers in one transaction
- 7108 — Database ID %d, page %S_PGID, slot %d, link number %d is invalid. Run DBCC CHECKTABLE.
- 7109 — 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…
- 7116 — Offset %d is not in the range of available LOB data.
- 7117 — Error reading large object (LOB) data from the tabular data stream (TDS).
- 7118 — Only complete replacement is supported when assigning a large object (LOB) to itself.
- 7119 — Attempting to grow LOB beyond maximum allowed size of %I64d bytes.
- 7122 — Invalid text, ntext, or image pointer type. Must be binary(16).
- 7123 — Invalid text, ntext, or image pointer value %hs.
- 7124 — The offset and length specified in the READTEXT statement is greater than the actual data length of %ld.
- 7125 — The text, ntext, or image pointer value conflicts with the column name specified.
- 7133 — NULL textptr (text, ntext, or image pointer) passed to %ls function.
- 7134 — LOB Locator is not supported as text pointer when using UPDATETEXT/WRITETEXT to update/write a text column.
- 7135 — Deletion length %ld is not in the range of available text, ntext, or image data.
- 7137 — %s is not allowed because the column is being processed by a concurrent snapshot or is being replicated to a non-SQL Server Subscriber or Published in…
- 7138 — The WRITETEXT statement is not allowed because the column is being replicated with Data Transformation Services (DTS) or tracked by Change Data Captur…
- 7139 — Length of LOB data (%I64d) to be replicated exceeds configured maximum %ld. Use the stored procedure sp_configure to increase the configured maximum v…
- 7140 — Cannot create additional orphans with the stored procedure sp_createorphan. Free up some of the orphan handles that you have created by inserting or d…
- 7141 — Must create orphaned text inside a user transaction.
- 7143 — Invalid locator de-referenced.
- 7144 — A text/ntext/image column referenced by a persisted or indexed computed column cannot be updated
- 7151 — Insufficient buffer space to perform write operation.
- 7152 — READEXT, WRITETEXT, and UPDATETEXT statements cannot be used on tables that are referenced by an enabled security policy.
- 7201 — Could not execute procedure on remote server '%.*ls' because SQL Server is not configured for remote access. Ask your system administrator to reconfig…
- 7202 — Could not find server '%.*ls' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlink…
- 7212 — Could not execute procedure '%.*ls' on remote server '%.*ls'.
- 7213 — The attempt by the provider to pass remote stored procedure parameters to remote server '%.*ls' failed. Verify that the number of parameters, the orde…
- 7214 — Remote procedure time out of %d seconds exceeded. Remote procedure '%.*ls' is canceled.
- 7215 — Could not execute statement on remote server '%.*ls'.
- 7221 — Could not relay results of procedure '%.*ls' from remote server '%.*ls'.
- 7222 — Only a SQL Server provider is allowed on this instance.
- 7223 — Warning: Enabling 'remote proc trans' is not supported on this instance. Defaulting to disabled.
- 7224 — Enabling 'remote proc trans' is not supported on this instance.
- 7225 — The current user does not have permission to execute queries against linked server '%.*ls'.
- 7301 — Cannot obtain the required interface ("%ls") from OLE DB provider "%ls" for linked server "%ls".
- 7302 — Cannot create an instance of OLE DB provider "%ls" for linked server "%ls".
- 7303 — Cannot initialize the data source object of OLE DB provider "%ls" for linked server "%ls".
- 7304 — Cannot connect using OLE DB provider "%ls" to linked server "%ls". Verify the connection parameters or login credentials associated with this linked s…
- 7305 — Cannot create a statement object using OLE DB provider "%ls" for linked server "%ls".
- 7306 — Cannot open the table "%ls" from OLE DB provider "%ls" for linked server "%ls". %ls
- 7307 — Cannot obtain the data source of a session from OLE DB provider "%ls" for linked server "%ls". This action must be supported by the provider.
- 7308 — OLE DB provider '%ls' cannot be used for distributed queries because the provider is configured to run in single-threaded apartment mode.
- 7310 — Cannot obtain the set of schema rowsets supported by OLE DB provider "%ls" for linked server "%ls". The provider supports the interface, but returns a…
- 7311 — Cannot obtain the schema rowset "%ls" for OLE DB provider "%ls" for linked server "%ls". The provider supports the interface, but returns a failure co…
- 7312 — Invalid use of schema or catalog for OLE DB provider "%ls" for linked server "%ls". A four-part name was supplied, but the provider does not expose th…
- 7313 — An invalid schema or catalog was specified for the provider "%ls" for linked server "%ls".
- 7314 — The OLE DB provider "%ls" for linked server "%ls" does not contain the table "%ls". The table either does not exist or the current user does not have …
- 7315 — The OLE DB provider "%ls" for linked server "%ls" contains multiple tables that match the name "%ls".
- 7316 — Cannot use qualified table names (schema or catalog) with the OLE DB provider "%ls" for linked server "%ls" because it does not implement required fun…
- 7317 — The OLE DB provider "%ls" for linked server "%ls" returned an invalid schema definition.
- 7318 — The OLE DB provider "%ls" for linked server "%ls" returned an invalid column definition for table "%ls".
- 7319 — The OLE DB provider "%ls" for linked server "%ls" returned a "%ls" index "%ls" with the incorrect bookmark ordinal %d.
- 7320 — Cannot execute the query "%ls" against OLE DB provider "%ls" for linked server "%ls". %ls
- 7321 — An error occurred while preparing the query "%ls" for execution against OLE DB provider "%ls" for linked server "%ls". %ls
- 7322 — A failure occurred while giving parameter information to OLE DB provider "%ls" for linked server "%ls".
- 7323 — An error occurred while submitting the query text to OLE DB provider "%ls" for linked server "%ls".
- 7324 — A failure occurred while setting parameter properties with OLE DB provider "%ls" for linked server "%ls".
- 7325 — Objects exposing columns with CLR types are not allowed in distributed queries. Please use a pass-through query to access remote object '%ls'.
- 7326 — An error occurred while retrieving the query text from OLE DB provider "%ls" for linked server "%ls".
- 7327 — A failure occurred while retrieving parameter information to OLE DB provider "%ls" for linked server "%ls".
- 7330 — Cannot fetch a row from OLE DB provider "%ls" for linked server "%ls".
- 7331 — Rows from OLE DB provider "%ls" for linked server "%ls" cannot be released.
- 7332 — Cannot rescan the result set from OLE DB provider "%ls" for linked server "%ls". %ls
- 7333 — Cannot fetch a row using a bookmark from OLE DB provider "%ls" for linked server "%ls".
- 7339 — OLE DB provider '%ls' for linked server '%ls' returned invalid data for column '%ls.%ls'.
- 7340 — Cannot create a column accessor for OLE DB provider "%ls" for linked server "%ls".
- 7341 — Cannot get the current row value of column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". %ls
- 7342 — An unexpected NULL value was returned for column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". This column cannot be NULL.
- 7343 — The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls". %ls
- 7344 — The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls" because of column "%ls". %ls
- 7345 — The OLE DB provider "%ls" for linked server "%ls" could not delete from table "%ls". %ls
- 7346 — Cannot get the data of the row from the OLE DB provider "%ls" for linked server "%ls". %ls
- 7347 — OLE DB provider '%ls' for linked server '%ls' returned data that does not match expected data length for column '%ls.%ls'. The (maximum) expected data…
- 7348 — The OLE DB provider "%ls" for linked server "%ls" could not set the range for table "%ls". %ls. For possible cause of this issue, see the extended err…
- 7349 — The OLE DB provider "%ls" for linked server "%ls" could not set the range for table "%ls" because of column "%ls". %ls
- 7350 — Cannot get the column information from OLE DB provider "%ls" for linked server "%ls".
- 7351 — The OLE DB provider "%ls" for linked server "%ls" could not map ordinals for one or more columns of object "%ls".
- 7352 — The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata. The object "%ls" was missing the expected column "%ls".
- 7353 — The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata. An extra column was supplied during execution that was not found at …
- 7354 — The OLE DB provider "%ls" for linked server "%ls" supplied invalid metadata for column "%ls". %ls
- 7355 — The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata for a column. The name was changed at execution time.
- 7356 — The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata for a column. The column "%ls" (compile-time ordinal %ld) of object "…
- 7357 — Cannot process the object "%ls". The OLE DB provider "%ls" for linked server "%ls" indicates that either the object has no columns or the current user…
- 7358 — Cannot execute the query. The OLE DB provider "%ls" for linked server "%ls" did not provide an appropriate interface to access the text, ntext, or ima…
- 7359 — The OLE DB provider "%ls" for linked server "%ls" reported a change in schema version between compile time ("%ls") and run time ("%ls") for table "%ls…
- 7360 — Cannot get the length of a storage object from OLE DB provider "%ls" for linked server "%ls" for table "%ls", column "%ls".
- 7361 — Cannot read a storage object from OLE DB provider "%ls" for linked server "%ls", for table "%ls", column "%ls".
- 7362 — The OLE DB provider "%ls" for linked server "%ls" reported different metadata at run time for table "%ls", column "%ls".
- 7365 — Cannot obtain optional metadata columns of columns rowset from OLE DB provider "%ls" for linked server "%ls".
- 7366 — Cannot obtain columns rowset from OLE DB provider "%ls" for linked server "%ls".
- 7367 — The OLE DB provider "%ls" for linked server "%ls" supports column level collation, but failed to provide the metadata column "%ls" at run time.
- 7368 — The OLE DB provider "%ls" for linked server "%ls" supports column level collation, but failed to provide collation data for column "%ls".
- 7369 — The OLE DB provider '%ls' for linked server '%ls' provided invalid collation. LCID = %08x, Compflags = %08x, SortOrder = '%.*ls'.
- 7370 — One or more properties could not be set on the query for OLE DB provider "%ls" for linked server "%ls". %ls
- 7371 — The server option 'collation name' in linked server '%ls' for OLE DB provider '%ls' has collation id %08x which is not supported by SQL Server.
- 7372 — Cannot get properties from OLE DB provider "%ls" for linked server "%ls".
- 7373 — Cannot set the initialization properties for OLE DB provider "%ls" for linked server "%ls".
- 7374 — Cannot set the session properties for OLE DB provider "%ls" for linked server "%ls".
- 7375 — Cannot open index "%ls" on table "%ls" from OLE DB provider "%ls" for linked server "%ls". %ls
- 7376 — Could not enforce the remote join hint for this query.
- 7377 — Cannot specify an index hint for a remote data source.
- 7380 — Table-valued parameters are not allowed in remote calls between servers.
- 7390 — The requested operation could not be performed because OLE DB provider "%ls" for linked server "%ls" does not support the required transaction interfa…
- 7391 — The operation could not be performed because OLE DB provider "%ls" for linked server "%ls" was unable to begin a distributed transaction.
- 7392 — Cannot start a transaction for OLE DB provider "%ls" for linked server "%ls".
- 7393 — The OLE DB provider "%ls" for linked server "%ls" reported an error 0x%08X aborting the current transaction.
- 7394 — The OLE DB provider "%ls" for linked server "%ls" reported an error committing the current transaction.
- 7395 — Unable to start a nested transaction for OLE DB provider "%ls" for linked server "%ls". A nested transaction was required because the XACT_ABORT optio…
- 7396 — Varchar(max), nvarchar(max), varbinary(max) and large CLR type data types are not supported as return value or output parameter to remote queries.
- 7397 — Remote function returned varchar(max), nvarchar(max), varbinary(max) or large CLR type value which is not supported.
- 7398 — The OLE DB provider '%ls' for linked server '%ls' reported an error committing the current inserts.
- 7399 — The OLE DB provider "%ls" for linked server "%ls" reported an error. %ls
- 7401 — The OLE DB provider "%ls" returned invalid literal prefix/suffix string.
- 7403 — The OLE DB provider "%ls" has not been registered.
- 7404 — The server could not load DCOM.
- 7405 — Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection. This ensures consistent query semantics. Enable t…
- 7409 — Could not start distributed query using integrated login because the user is logged in using SQL Server authentication. Provide remote server login us…
- 7410 — Remote access is not allowed for impersonated security context.
- 7411 — Server '%.*ls' is not configured for %ls.
- 7412 — OLE DB provider "%ls" for linked server "%ls" returned message "%ls".
- 7413 — Could not connect to linked server '%ls' (OLE DB Provider '%ls'). Enable delegation or use a remote SQL Server login for the current user.
- 7414 — Invalid number of parameters. Rowset '%ls' expects %d parameter(s).
- 7415 — Ad hoc access to OLE DB provider '%ls' has been denied. You must access this provider through a linked server.
- 7416 — Access to the remote server is denied because no login-mapping exists.
- 7417 — GROUP BY ALL is not supported in queries that access remote tables if there is also a WHERE clause in the query.
- 7418 — Text, image, or ntext column was too large to send to the remote data source due to the storage interface used by the provider.
- 7419 — Lazy schema validation error. Linked server schema version has changed. Re-run the query.
- 7420 — Remote access is not supported for transaction isolation level "%ls".
- 7421 — Cannot fetch the rowset from OLE DB provider "%ls" for linked server "%ls". %ls.
- 7422 — OLE DB provider "%ls" for linked server "%ls" returned an invalid index definition for table "%ls".
- 7423 — The '%ls' OLE DB provider for the '%ls' linked server returned an invalid CLR type definition for the '%ls' table.
- 7424 — OLE DB provider "%ls" for linked server "%ls" returned "%ls" with data type "%ls", which should be type "%ls".
- 7425 — OLE DB provider "%ls" for linked server "%ls" returned an incorrect value for "%ls", which should be "%ls".
- 7426 — OLE DB provider "%ls" for linked server "%ls" returned "%ls" without "%ls" being supported.
- 7427 — OLE DB provider "%ls" for linked server "%ls" returned "%ls" for "%ls" during statistics gathering.
- 7428 — OLE DB provider "%ls" for linked server "%ls" supported the schema lock interface, but returned "%ls" for "%ls".
- 7429 — %hs SQL Server Remote Metadata Gather Time for Table %s.%s:%hs, CPU time = %lu ms, elapsed time = %lu ms.
- 7430 — Out-of-process use of OLE DB provider "%ls" with SQL Server is not supported.
- 7431 — Unable to delete OLE DB parameter properties.
- 7432 — Heterogeneous queries and use of OLEDB providers are not supported in fiber mode.
- 7433 — OLE DB provider '%ls' for linked server '%ls' returned truncated data for column '%ls.%ls'. The actual data length is %ls and truncated data length is…
- 7435 — The OLE DB provider "%ls" for linked server "%ls" returned unexpected NULL pointer for string column "%ls.%ls".
- 7436 — The query processor could not produce a query plan because FORCESEEK or FORCESCAN hints on table or view '%.*ls' cannot be used with remote data sourc…
- 7437 — Linked servers cannot be used under impersonation without a mapping for the impersonated login.
- 7438 — The 32-bit OLE DB provider "%ls" cannot be loaded in-process on a 64-bit SQL Server.
- 7439 — Failed to read required information about %S_MSG pool %S_MSG.
- 7440 — Remote execution status: "%ls" .
- 7441 — Linked server query execution failed due to an internal error related to AAD authentication.
- 7442 — Linked Server use self mode AAD authentication functionality is disabled on the service side and therefore cannot be used.
- 7443 — AAD use-self authentication to Linked Server "%ls" failed because it is not part of any Server trust group that contains current server. Use documenta…
- 7444 — Linked Server access token mode AAD authentication functionality is disabled on the service side and therefore cannot be used.
- 7445 — AAD token for accessing linked server cannot be obtained. Error message: '%ls'.
- 7446 — Linked Server use MSI mode AAD authentication functionality is disabled on the service side and therefore cannot be used.
- 7447 — Linked Server AAD authentication using username and password is disabled on the service side and therefore cannot be used.
- 7448 — Linked Server login mapping with "useself" property set is not allowed when using AAD '%ls' authentication mode.
- 7449 — Linked Server User-assigned MSI mode AAD authentication functionality is not supported on the service side. Use system-assigned identity instead.
- 7450 — Querying linked server '%ls' failed. Either login for Linked Server AAD '%ls' authentication mode does not exist or login's 'useself' attribute is set…
- 7451 — Retrieval of the MWC Token for Onelake/DFS access failed with error '%ls'.
- 7452 — Initialization of the MWC Token Cache failed. Lock Mode: %.*ls.
- 7453 — Sending of statistics request failed with error '%lu'.
- 7454 — SQL internal communication failed with error '%ls'.
- 7455 — Service Master Key is not generated or access is lost so encryption/decryption of linked server passwords cannot be done.
- 7456 — Retrieval of the MwcResolvePrincipalSpecifierCallback failed with error '%ls'.
- 7457 — Retrieval of the MwcUserSecuritySyncCallback failed with error '%ls'.
- 7601 — Cannot use a CONTAINS or FREETEXT predicate on %S_MSG '%.*ls' because it is not full-text indexed.
- 7602 — The full-text service (msftesql%ls%ls) is not available. The system administrator must start this service.
- 7603 — Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID '%d', database ID '%d' is reset.
- 7604 — Full-text operation failed due to a time out.
- 7605 — Failed to finish full-text operation. Filegroup '%.*ls' is empty, read-only, or not online.
- 7606 — Could not find full-text index for database ID %d, table or indexed view ID %d.
- 7607 — Search on full-text catalog '%ls' for database ID %d, table or indexed view ID %d with search condition '%ls' failed with unknown result (0x%x).
- 7608 — An unknown full-text failure (0x%x) occurred during "%hs".
- 7609 — Full-Text Search is not installed, or a full-text component cannot be loaded.
- 7610 — Access is denied to "%.*ls", or the path is invalid.
- 7611 — Warning: Request to start a population in full-text catalog '%ls' ignored because a population is currently active for this full-text catalog.
- 7612 — NULL or Invalid type of value specified for '%ls' parameter.
- 7613 — Cannot drop index '%.*ls' because it enforces the full-text key for table or indexed view '%.*ls'.
- 7614 — Cannot alter or drop column '%.*ls' because it is enabled for Full-Text Search.
- 7615 — A CONTAINS or FREETEXT predicate can only operate on one table or indexed view. Qualify the use of * with a table or indexed view name.
- 7616 — Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable full-text search for the database. The functionality to d…
- 7617 — Query does not reference the full-text indexed table or indexed view, or user does not have permission to perform this action.
- 7618 — Cannot use full-text search in master, tempdb, or model database.
- 7619 — The execution of a full-text query failed. "%ls"
- 7620 — The conversion to data type %ls failed for the full-text search key.
- 7621 — Invalid use of full-text predicate in the HAVING clause.
- 7622 — There is not sufficient disk space to complete this operation for the full-text catalog "%ls".
- 7623 — A default full-text catalog does not exist in database '%.*ls' or user does not have permission to perform this action.
- 7624 — Full-text catalog '%ls' is in an unusable state. Drop and re-create this full-text catalog.
- 7625 — Full-text table or indexed view has more than one LCID among its full-text indexed columns.
- 7626 — The top_n_by_rank argument ('%d') must be greater than or equal to zero.
- 7627 — Cannot create the full-text catalog in the directory "%.*ls" for the clustered server. Only directories on a disk in the cluster group of the server c…
- 7628 — 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…
- 7629 — Cannot open or query the full-text default path registry key. The full-text default catalog path is invalid.
- 7630 — Syntax error near '%.*ls' in the full-text search condition '%.*ls'.
- 7631 — Warning: No appropriate wordbreaker was found during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', databa…
- 7632 — The value of the Weight argument must be between 0.0 and 1.0.
- 7633 — Couldn't complete full-text operation because full-text key for table or indexed view '%.*ls' is offline.
- 7634 — 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 ke…
- 7635 — Warning: No appropriate filter for embedded object was found during full-text index population for table or indexed view '%ls' (table or indexed view …
- 7636 — Warning: Request to start a full-text index population on table or indexed view '%.*ls' is ignored because a population is currently active for this t…
- 7637 — 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.
- 7638 — Warning: Request to stop change tracking has deleted all changes tracked on table or indexed view '%ls'.
- 7639 — Cannot use a full-text predicate on %S_MSG '%.*ls' because it is not located on the local server.
- 7640 — Warning: Request to stop tracking changes on table or indexed view '%.*ls' will not stop population currently in progress on the table or indexed view…
- 7641 — Full-Text catalog '%ls' does not exist in database '%.*ls' or user does not have permission to perform this action.
- 7642 — A full-text catalog named '%ls' already exists in this database. Use a different name.
- 7643 — Cannot use a CONTAINS or FREETEXT predicate on %S_MSG '%.*ls' because none of its columns are full-text indexed.
- 7644 — Full-text crawl manager has not been initialized. Any crawl started before the crawl manager was fully initialized will need to be restarted. Please r…
- 7645 — Null or empty full-text predicate.
- 7646 — Fulltext predicate references columns from two different tables or indexed views '%.*ls' and '%.*ls' which is not allowed.
- 7647 — Warning: Configuration of full-text catalog at '%ls' could not be saved during detach database.
- 7648 — Warning: Failed to attach full-text catalog '%ls'.
- 7649 — Warning: Failed to dismount full-text catalog at '%ls'.
- 7650 — Warning: Failed to drop full-text catalog at '%ls'.
- 7651 — Warning: The ongoing population is necessary to ensure an up-to-date index. If needed, stop change tracking first, and then deactivate the full-text i…
- 7652 — A full-text index for table or indexed view '%.*ls' has already been created.
- 7653 — '%ls' is not a valid index to enforce a full-text search key. A full-text search key must be a unique, non-nullable, single-column index which is not …
- 7654 — Unable to obtain the population status of the table or indexed view '%.*ls'.
- 7655 — TYPE COLUMN option must be specified with column of image or varbinary(max) type.
- 7656 — Full-text index for table or indexed view '%.*ls' cannot be populated because the database is in single-user access mode.
- 7657 — Warning: Table or indexed view '%.*ls' has full-text indexed columns that are of type image, text, or ntext. Full-text change tracking cannot track WR…
- 7658 — Table or indexed view '%.*ls' does not have a full-text index or user does not have permission to perform this action.
- 7659 — Cannot activate full-text search for table or indexed view '%.*ls' because no columns have been enabled for full-text search.
- 7660 — Full-text search must be activated on table or indexed view '%.*ls' before this operation can be performed.
- 7661 — Warning: Full-text change tracking is currently enabled for table or indexed view '%.*ls'.
- 7662 — Warning: Full-text auto propagation is currently enabled for table or indexed view '%.*ls'.
- 7663 — Option 'WITH NO POPULATION' should not be used when change tracking is enabled.
- 7664 — Full-text change tracking must be started on table or indexed view '%.*ls' before the changes can be flushed.
- 7665 — 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 populat…
- 7666 — User does not have permission to perform this action.
- 7667 — Failed to create full-text catalog '%ls'.
- 7668 — Cannot drop full-text catalog '%ls' because it contains a full-text index.
- 7669 — 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 …
- 7670 — Column '%.*ls' cannot be used for full-text search because it is not a character-based, XML, image or varbinary(max) type column or it is encrypted.
- 7671 — 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 charact…
- 7672 — A full-text index cannot be created on the table or indexed view because duplicate column '%.*ls' is specified.
- 7673 — Warning: Full-text change tracking is currently disabled for table or indexed view '%.*ls'.
- 7674 — Warning: The fulltext catalog '%.*ls' is being dropped and is currently set as default.
- 7676 — Warning: Full-text auto propagation is on. Stop crawl request is ignored.
- 7677 — Column "%.*ls" is not full-text indexed.
- 7678 — The following string is not defined as a language alias in syslanguages: %.*ls.
- 7679 — Full-text index language of column "%.*ls" is not a language supported by full-text search.
- 7680 — Default full-text index language is not a language supported by full-text search.
- 7681 — 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. T…
- 7682 — The component '%ls' reported error while indexing. Component path '%ls'.
- 7683 — Errors were encountered during full-text index population for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID …
- 7684 — 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 ke…
- 7685 — 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 ke…
- 7686 — Cannot use a CONTAINS, FREETEXT, CONTAINSTABLE or FREETEXTTABLE construct on table or indexed view '%.*ls' because none of its columns are full-text i…
- 7687 — ALTER TABLE SWITCH statement failed because table '%.*ls' and table '%.*ls' have non-matching fulltext indexes.
- 7688 — ALTER TABLE SWITCH statement failed because there are active crawls on the fulltext index, wait until crawl completed or disable fulltext index.
- 7689 — Execution of a full-text operation failed. '%ls'
- 7690 — Full-text operation failed because database is read only.
- 7691 — Access is denied to full-text log path. Full-text logging is disabled for database '%ls', catalog '%ls' (database ID '%d', catalog ID '%d').
- 7692 — Full-text catalog path '%.*ls' exceeded %d character limit.
- 7693 — Full-text initialization failed to create a memory clerk.
- 7694 — Failed to pause catalog for backup. Backup was aborted.
- 7695 — Operation failed. Full-text catalog backup in progress. Retry after backup operation has completed.
- 7696 — Invalid locale ID was specified. Please verify that the locale ID is correct and corresponding language resource has been installed.
- 7697 — Warning: Full-text index on table or indexed view '%.*ls' in database '%.*ls' has been changed after full-text catalog files backup. A full population…
- 7698 — GROUP BY ALL cannot be used in full text search queries.
- 7699 — TYPE COLUMN option is not allowed for column types other than image or varbinary(max).
- 7702 — Empty Partition function type-parameter-list is not allowed when defining a partition function.
- 7703 — Can not create RANGE partition function with multiple parameter types.
- 7704 — The type '%.*ls' is not valid for this operation.
- 7705 — Could not implicitly convert range values type specified at ordinal %d to partition function parameter type.
- 7706 — Partition function '%ls' is being used by one or more partition schemes.
- 7707 — The associated partition function '%ls' generates more partitions than there are file groups mentioned in the scheme '%ls'.
- 7708 — Duplicate range boundary values are not allowed in partition function boundary values list. Partition boundary values at ordinal %d and %d are equal.
- 7709 — Warning: Range value list for partition function '%.*ls' is not sorted by value. Mapping of partitions to filegroups during CREATE PARTITION SCHEME wi…
- 7710 — Warning: The partition scheme '%.*ls' does not have any next used filegroup. Partition scheme has not been changed.
- 7711 — The %ls option was specified more than once for the table, or for at least one of its partitions if the table is partitioned.
- 7712 — Partition scheme '%.*ls' has been created successfully. '%.*ls' is marked as the next used filegroup in partition scheme '%.*ls'.
- 7713 — %d filegroups specified after the next used filegroup are ignored.
- 7714 — Partition range value is missing.
- 7715 — The specified partition range value could not be found.
- 7716 — Can not create or alter a partition function to have zero partitions.
- 7717 — The partition scheme "%.*ls" is currently being used to partition one or more tables.
- 7718 — Partition range value cannot be specified for hash partitioning.
- 7719 — CREATE/ALTER partition function failed as only a maximum of %d partitions can be created.
- 7720 — Data truncated when converting range values to the partition function parameter type. The range value at ordinal %d requires data truncation.
- 7721 — Duplicate range boundary values are not allowed in partition function boundary values list. The boundary value being added is already present at ordin…
- 7722 — Invalid partition number %I64d specified for %S_MSG '%.*ls', partition number can range from 1 to %d.
- 7723 — Only a single filegroup can be specified while creating partition scheme using option ALL to specify all the filegroups.
- 7724 — Computed column cannot be used as a partition key if it is not persisted. Partition key column '%.*ls' in table '%.*ls' is not persisted.
- 7725 — Alter partition function statement failed. Cannot repartition table '%.*ls' by altering partition function '%.*ls' because its clustered index '%.*ls'…
- 7726 — Partition column '%.*ls' has data type %s which is different from the partition function '%.*ls' parameter data type %s.
- 7727 — Collation of partition column '%.*ls' does not match collation of corresponding parameter in partition function '%.*ls'.
- 7728 — Invalid partition range: %d TO %d. Lower bound must not be greater than upper bound.
- 7729 — Cannot specify partition number in the %S_MSG %S_MSG statement as the %S_MSG '%.*ls' is not partitioned.
- 7730 — Alter %S_MSG statement failed because partition number %d does not exist in %S_MSG '%.*ls'.
- 7731 — Cannot specify partition number in Alter %S_MSG statement to rebuild or reorganize a partition of %S_MSG '%.*ls'.
- 7732 — Cannot specify partition number in Alter index statement along with keyword ALL to rebuild partitions of table '%.*ls' when the table does not have an…
- 7733 — '%ls' statement failed. The %S_MSG '%.*ls' is partitioned while %S_MSG '%.*ls' is not partitioned.
- 7734 — The %S_MSG '%.*ls' specified for the clustered index '%.*ls' was used for table '%.*ls' even though %S_MSG '%.*ls' is specified for it.