SQL Server Error Messages 30001 to 35000

In this post, we’ll list out the SQL Server Error Messages from the error codes 30001 to 35000 and references to the detailed post to know more about the errors and how to fix them when using SQL Server as database in your application.

SQL Server Error Messages 30001 to 35000

ErrorCodeSeverityErrorMessage
3000316A fulltext system view or stvf cannot open database id %d.
3000416A fulltext system view or stvf cannot open user table object id %d.
3000516The name specified for full-text index fragment %.*ls is not valid.
3000616A fulltext system view or stvf cannot open fulltext index for user table object id %d.
3000716Parameters of dm_fts_index_keywords, dm_fts_index_keywords_by_document, dm_fts_index_keywords_by_property, and dm_fts_index_keywords_position_by_document cannot be null.
3000816This is an internal error when invoking the TVF to access the full-text index. The level number specified for the TVF is not valid. Valid level numbers start from 0 and must be less than the number of levels of the compressed index.
3000916The argument data type ‘%ls’ specified for the full-text query is not valid. Allowed data types are char, varchar, nchar, nvarchar.
3002016The full-text query parameter for %S_MSG is not valid.
3002210Warning: The configuration of a full-text stoplist was modified using the WITH NO POPULATION clause. This put the full-text index into an inconsistent state. To bring the full-text index into a consistent state, start a full population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name START FULL POPULATION.
3002316The fulltext stoplist ‘%.*ls’ does not exist or the current user does not have permission to perform this action. Verify that the correct stoplist name is specified and that the user had the permission required by the Transact-SQL statement.
3002416The fulltext stoplist ‘%.*ls’ already exists in the current database. Duplicate stoplist names are not allowed. Rerun the statement and specify a unique stoplist name.
3002516The search property list ‘%.*ls’ does not exist or you do not have permission to perform this action. Verify that the correct search property list name is specified and that you have the permission required by the Transact-SQL statement. For a list of the search property lists on the current database, use the sys.registered_search_property_lists catalog view. For information about permissions required by a Transact-SQL statement, see the Transact-SQL reference topic for the statement in SQL Server Books Online.
3002616The search property list ‘%.*ls’ already exists in the current database. Duplicate search property list names are not allowed. Rerun the statement and specify a unique name for the search property list. For a list of the search property lists on the current database, use the sys.registered_search_property_lists catalog view.
3002710The full-text index is in an inconsistent state because the search property list of the full-text index was reconfigured using the WITH NO POPULATION clause. To bring the full-text index into a consistent state, start a full population using the statement ALTER FULLTEXT INDEX ON <table_name> START FULL POPULATION;. This is a warning. No user action is necessary.
3002817Failed to get pipeline interface for ‘%ls’, resulting in error: 0x%X. There is a problem communicating with the host controller or filter daemon host.
3002917The full-text host controller failed to start. Error: 0x%X.
3003016The search property ‘%.*ls’ does not exist, or you do not have permission to perform this action. Verify that the correct search property is specified and that you have the permission required by the Transact-SQL statement. For a list of the search properties on the current database, use the sys.registered_search_properties catalog view. For information about the permissions required by a Transact-SQL statement, see the Transact-SQL reference topic for the statement in SQL Server Books Online.
3003117A full-text master merge failed on full-text catalog ‘%ls’ in database ‘%.*ls’ with error 0x%08X.
3003216The stoplist ‘%.*ls’ does not contain fulltext stopword ‘%.*ls’ with locale ID %d. Specify a valid stopword and locale identifier (LCID) in the Transact-SQL statement.
3003316The stoplist ‘%.*ls’ already contains full-text stopword ‘%.*ls’ with locale ID %d. Specify a unique stopword and locale identifier (LCID) in the Transact-SQL statement.
3003416Full-text stoplist ‘%.*ls’ cannot be dropped because it is being used by at least one full-text index. To identify which full-text index is using a stoplist: obtain the stoplist ID from the stoplist_id column of the sys.fulltext_indexes catalog view, and then look up that stoplist ID in the stoplist_id column of the sys.fulltext_stoplists catalog view. Either drop the full-text index by using DROP FULLTEXT INDEX or change its stoplist setting by using ALTER FULLTEXT INDEX. Then retry dropping the stoplist.
3003516The search property ‘%.*ls’ already exists in the search property list. Specify a search property name that is unique within the specified search property list. For a list of the search properties on the current database, use the sys.registered_search_properties catalog view.
3003616Search property list ‘%.*ls’ cannot be dropped because it is being used by at least one full-text index. To identify the full-text indexes that are using the search property list, obtain the search property list id from the property_list_id column of the sys.registered_search_property_lists catalog view, and then obtain the object ID of every table or indexed view whose full-text index is associated with this search property list from the object_id and property_list_id columns of the sys.fulltext_indexes catalog view . For each full-text index, either remove the search property list or drop the full-text index, if it is no longer needed. To remove the search property list, use ALTER FULLTEXT INDEX ON <table_name> SET SEARCH PROPERTY LIST OFF;. To drop a full-text index, use DROP FULLTEXT INDEX ON <table_name>;.
3003716An argument passed to a fulltext function is not valid.
3003817Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
3003917Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size.
3004010During a full-text crawl of table or indexed view ‘%ls’, an unregistered property, ‘%ls’, was found in batch ID %d. This property will be indexed as part of the generic content and will be unavailable for property-scoped full-text queries. Table or indexed view ID is ‘%d’. Database ID is ‘%d’. For information about registering properties and updating the full-text index of a table or indexed view, see the full-text search documentation in SQL Server Books Online. This is an informational message. No user action is necessary.
3004110The master merge started at the end of the full crawl of table or indexed view ‘%ls’ failed with HRESULT = ‘0x%08x’. Database ID is ‘%d’, table id is %d, catalog ID: %d.
3004316Stopwords of zero length cannot be added to a full-text stoplist. Specify a unique stopword that contains at least one character.
3004416The user does not have permission to alter the current default stoplist ‘%.*ls’. To change the default stoplist of the database, ALTER permission is required on both new and old default stoplists.
3004517Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
3004616SQL Server encountered error 0x%x while communicating with full-text filter daemon host (FDHost) process. Make sure that the FDHost process is running. To re-start the FDHost process, run the sp_fulltext_service ‘restart_all_fdhosts’ command or restart the SQL Server instance.
3004716The user does not have permission to %.*ls stoplist ‘%.*ls’.
3004810Informational: Ignoring duplicate thesaurus rule ‘%ls’ while loading thesaurus file for LCID %d. A duplicate thesaurus phrase was encountered in either the <sub> section of an expansion rule or the <pat> section of a replacement rule. This causes an ambiguity and hence this phrase will be ignored.
3004917Fulltext thesaurus internal error (HRESULT = ‘0x%08x’)
3005016Both the thesaurus file for lcid ‘%d’ and the global thesaurus could not be loaded.
3005116Phrases longer than 512 unicode characters are not allowed in a thesaurus file. Phrase: ‘%ls’.
3005216The full-text query has a very complex NEAR clause in the CONTAINS predicate or CONTAINSTABLE function. To ensure that a NEAR clause runs successfully, use only six or fewer terms. Modify the query to simplify the condition by removing prefixes or repeated terms.
3005316An error has occurred during the full-text query. Common causes include: word-breaking errors or timeout, FDHOST permissions/ACL issues, service account missing privileges, malfunctioning IFilters, communication channel issues with FDHost and sqlservr.exe, etc.
3005510Full-text catalog import has started for full-text catalog ‘%ls’ in database ‘%ls’.
3005610Full-text catalog import has finished for full-text catalog ‘%ls’ in database ‘%ls’. %d fragments and %d keywords were processed.
3005710Upgrade option ‘%ls’ is being used for full-text catalog ‘%ls’ in database ‘%ls’.
3005816Properties of zero length cannot be added to a search property list. Specify a search property name that contains at least one character and that is unique to the specified search property list. For a list of the search properties on the current database, use the sys.registered_search_properties catalog view.
3005916A fatal error occurred during a full-text population and caused the population to be cancelled. Population type is: %s; database name is %s (id: %d); catalog name is %s (id: %d); table name %s (id: %d). Fix the errors that are logged in the full-text crawl log. Then, resume the population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name RESUME POPULATION.
3006016The import population for database %ls (id: %d), catalog %ls (id: %d) is being cancelled because of a fatal error (‘%ls’). Fix the errors that are logged in the full-text crawl log. Then resume the import either by detaching the database and re-attaching it, or by taking the database offline and bringing it back online. If the error is not recoverable, rebuild the full-text catalog.
3006117The SQL Server failed to create full-text filterdata directory. This might be because FulltextDefaultPath is invalid or SQL Server service account does not have permission. Full-text blob indexing will fail until this issue is resolved. Restart SQL Server after the issue is fixed.
3006217The SQL Server failed to load FDHost service group sid. This might be because installation is corrupted.
3006310Warning: SQL Server could not set fdhost.exe processor affinity to %d because the value is not valid.
3006417SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of documents may fail until this issue is resolved. You will need to repair the SQL Server installation.
3006510Filegroup ‘%ls’ is offline, readonly, or no data file. Full-text population on table ‘%ls’ is not resumed. Resume full-text population after fixing the filegroup status.
3006710Warning: The detach operation cannot delete a full-text index created on table ‘%ls’ in database ‘%ls’ because the index is on a read-only filegroup. To drop the full-text index, re-attach the database, change the read-only filegroup to read/write access and then detach it. This warning will not fail the database detach operation.
3006810During the database upgrade, the full-text filter component ‘%ls’ that is used by catalog ‘%ls’ was successfully verified. Component version is ‘%ls’; Full path is ‘%.*ls’.
3006911The full-text filter component ‘%ls’ used to populate catalog ‘%ls’ in a previous SQL Server release is not the current version (component version is ‘%ls’, full path is ‘%.*ls’). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the filter component.
3007010During the database upgrade, the full-text word-breaker component ‘%ls’ that is used by catalog ‘%ls’ was successfully verified. Component version is ‘%ls’. Full path is ‘%.*ls’. Language requested is %d. Language used is %d.
3007111The full-text word-breaker component ‘%ls’ used to populate catalog ‘%ls’ in a previous SQL Server release is not the current version (component version is ‘%ls’, full path is ‘%.*ls’, language requested is %d, language used is %d). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the word-breaker component.
3007210During the database upgrade, the full-text protocol handler component ‘%ls’ that is used by catalog ‘%ls’ was successfully verified. Component version is ‘%ls’. Full path is ‘%.*ls’. Program ID is ‘%.*ls’.
3007311The full-text protocol handler component ‘%ls’ used to populate catalog ‘%ls’ in a previous SQL Server release is not the current version (component version is ‘%ls’, full path is ‘%.*ls’, program ID is ‘%.*ls’). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the protocol handler component.
3007417The master merge of full-text catalog ‘%ls’ in database ‘%.*ls’ was cancelled.
3007510Full-text crawls for database ID: %d, table ID: %d, catalog ID: %d will be stopped since the clustered index on the table has been altered or dropped. Crawl will need to re-start from the beginning.
3007610Full-text crawl forward progress information for database ID: %d, table ID: %d, catalog ID: %d has been reset due to the modification of the clustered index. Crawl will re-start from the beginning when it is unpaused.
3007716The full-text query did not use the value specified for the OPTIMIZE FOR query hint. Only single terms are allowed as values for full-text queries that contain an OPTIMIZE FOR query hint. Modify the OPTIMIZE FOR query hint value to be a single, non-empty term.
3007810The fulltext query did not use the value specified for the OPTIMIZE FOR hint because the query contained more than one type of full-text logical operator.
3007910The full text query ignored UNKNOWN in the OPTIMIZE FOR hint.
3008016The full-text population on table ‘%ls’ cannot be started because the full-text catalog is importing data from existing catalogs. After the import operation finishes, rerun the command.
3008110A cached plan was compiled using trace flags that are incompatible with the current values. Consider recompiling the query with the new trace flag settings.
3008216Full-text predicates cannot appear in an aggregate expression. Place the aggregate expression in a subquery.
3008316Full-text predicates cannot appear in the GROUP BY clause. Place a GROUP BY clause expression in a subquery.
3008416The full-text index cannot be created because filegroup ‘%.*ls’ does not exist or the filegroup name is incorrectly specified. Specify a valid filegroup name.
3008516A stoplist cache cannot be generated while processing a full-text query or performing full-text indexing. There is not enough memory to load the stoplist cache. Rerun the query or indexing command when more resources are available.
3008616The system ran out of memory while building a full-text index. The batch for the full-text indexing operation will automatically be retried using a smaller batch size.
3008717Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size.
3008810The full-text filter daemon host process has stopped normally. The process will be automatically restarted if necessary.
3008917The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning linguistic component, such as a wordbreaker, stemmer or filter has caused an irrecoverable error during full-text indexing or query processing. The process will be restarted automatically.
3009010A new instance of the full-text filter daemon host process has been successfully started.
3009110A request to start a full-text index population on table or indexed view ‘%.*ls’ is ignored because a population is currently paused. Either resume or stop the paused population. To resume it, use the following Transact-SQL statement: ALTER FULLTEXT INDEX ON %.*ls RESUME POPULATION. To stop it, use the following statement: ALTER FULLTEXT INDEX ON %.*ls STOP POPULATION.
3009216Full-text stoplist ID ‘%d’ does not exist.
3009317The SQL Server word-breaking client failed to initialize. This might be because a filter daemon host process is not in a valid state. This can prevent SQL Server from initializing critical system objects. Full-text queries will fail until this issue is resolved. Try stopping SQL Server and any filter daemon host processes and then restarting the instance of SQL Server.
3009417The full-text indexing pipeline could not be initialized. This might be because the resources on the system are too low to allocate memory or create tasks. Try restarting the instance of SQL Server.
3009510The version of the language components used by full-text catalog ‘%ls’ in database ‘%ls’ is different from the version of the language components included this version of SQL Server. The full-text catalog will still be imported as part of database upgrade. To avoid any possible inconsistencies of query results, consider rebuilding the full-text catalog.
3009610A full-text retry pass of %ls population started for table or indexed view ‘%ls’. Table or indexed view ID is ‘%d’. Database ID is ‘%d’.
3009710The fulltext catalog upgrade failed because of an inconsistency in metadata between sys.master_files and sys.fulltext_catalogs for the catalog ID %d in database ID %d. Try to reattach this database. If this fails, then the catalog will need to be dropped or recreated before attach.
3009810An internal query to load data for a crawl on database ‘%.*ls’ and table ‘%.*ls’ failed with error code %d. Check the sql error code for more information about the condition causing this failure. The crawl needs to be restarted after this condition is removed.
3009917Fulltext internal error
3010316Invalid CM instance name.
3010416Invalid matrix name.
3010516Invalid TCP port number: %s.
3010616Invalid network security level.
3010716Invalid network isolation level.
3010816Invalid matrix guid.
3010916Invalid or duplicated brick ID was used: %s
3011016Invalid parameter.
3011116Matrix setup stored procedure ‘%s’ failed with HRESULT 0x%x.
3011216Insert brick into metadata operation failed during execution of stored procedure ‘%s’.
3011316Insert manager into metadata operation failed during execution of stored procedure ‘%s’.
3011416Insert parameter into metadata operation failed during execution of stored procedure ‘%s’.
3011516No more bricks can be reserved. The maximum amount of %lu bricks is reached.
3011816Invalid server name provided to configure a matrix brick.
3011916Invalid CM brick GUID.
3012016Invalid brick GUID.
3012116‘%s’ in only allowed in standalone (non matrix) mode.
3012216‘%s’ in only allowed in single user (-m) mode.
3012316Drop existing matrix configuration failed during execution of stored procedure ‘%s’.
3012416An error occurred while updating the CM metadata to remove a brick.
3012516Configuration manager could not write the WMI offline configuration file during the execution of stored procedure ‘%s’.
3012616Could not complete the last operation with the brick_id %u due a metadata failure
3012716Attempt to cancel the reservation of a brick that is not reserved: %u
3012816The stored procedure ‘%s’ failed with the error code %d
3012916‘%s’ in only allowed in matrix mode.
3013016The brick with server name ‘%s’ already exists in the configuration.
3100116The session ‘%s’ already exists. Use a different session name.
3100216This operation can be performed only by the owner of the session.
3100316User does not have enough permissions to tune one or more of the databases specified.
3100416Could not create DTA directory for saving tuning option file when invoking DTA for auto indexing.
3100516Could not create DTA tuning option file when invoking DTA for auto indexing.
3100616Could not write DTA tuning option to file when invoking DTA for auto indexing.
3100716Could not create a DTA job when invoking DTA for auto indexing.
3100816Could not retrieve limit and job state information from DTA job object when invoking DTA for auto indexing.
3100916Could not set limits on DTA job object when invoking DTA for auto indexing.
3101016Could not create a DTA process when invoking DTA for auto indexing.
3101116Could not terminate DTA process after it fails to be assigned to DTA job object when invoking DTA for auto indexing.
3101216Could not resume DTA process to start tuning when invoking DTA for auto indexing.
3101316Invalid tuning option specified for auto indexing.
3101416Could not terminate DTA job when cancelling DTA tuning for auto indexing.
3101516Could not delete DTA tuning options file when cancelling DTA tuning for auto indexing.
3101616Could not cleanup hypothetical indexes and statistics when cancelling DTA tuning for auto indexing.
3101716DTA tuning for auto indexing is only supported on Azure DB.
3101816Could not get winfab temp directory when performing DTA tuning related task.
3101916Could not create GUID when performing DTA tuning related task.
3102016String operation failed.
3102116Could not get winfab log directory when performing DTA tuning related task.
3102216Could not get winfab data package directory when performing DTA tuning related task.
3120116Property-scoped full-text queries cannot be specified on the specified table because its full-text index is not configured for property searching. To support property-scoped searches, the full-text index must be associated with a search property list and repopulated. The Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON <table_name> SET SEARCH PROPERTY LIST <property_list_name>;.
3120210Reconfiguring the search property list of the full-text index has truncated the existing data in the index. Until the full-text index has been fully repopulated, full-text queries will return partial results. The ALTER FULLTEXT INDEX <table_name> SET SEARCH PROPERTY LIST …; statement automatically issues a full population, but if the ALTER FULLTEXT INDEX statement specified the WITH NO POPULATION clause, you must run a full population on the full-text index using ALTER FULLTEXT INDEX ON <table_name> START FULL POPULATION;. This is a warning.
3120310Warning Master Merge operation was not done for dbid %d, objid %d, so querying index will be slow. Please run alter fulltext catalog reorganize.
3120416Operation %ls is not supported on the %ls platform.
3120516The import population for database %ls (id: %d), catalog id: %d is being cancelled because of a fatal error (‘%ls’). Fix the errors that are logged in the full-text crawl log. Then resume the import either by detaching the database and re-attaching it, or by taking the database offline and bringing it back online. If the error is not recoverable, rebuild the full-text catalog.
3200110Log shipping backup log job for %s.
3200210Log shipping copy job for %s:%s.
3200310Log shipping restore log job for %s:%s.
3200410Log shipping backup log job step.
3200510Log shipping copy job step.
3200610Log shipping restore log job step.
3200716Database %s is not ONLINE.
3200810Database %s is not ONLINE. The backup job will not be performed until this database is brought online.
3200916A log shipping primary entry already exists for database %s.
3201016Database %s does not exist as log shipping primary.
3201116Primary Database %s has active log shipping secondary database(s). Drop the secondary database(s) first.
3201216Secondary %s.%s already exists for primary %s.
3201316A log shipping entry already exists for secondary database %s.
3201416Database %s does not exist as log shipping secondary.
3201516The primary database %s cannot have SIMPLE recovery for log shipping to work properly.
3201616The specified agent_id %s or agent_type %d do not form a valid pair for log shipping monitoring processing.
3201716Log shipping is supported on Enterprise, Developer and Standard editions of SQL Server. This instance has %s and is not supported.
3201816Log shipping is not installed on this instance.
3201910Log shipping alert job.
3202010Log shipping alert job step.
3202110Log shipping alert job schedule.
3202216Cannot add a log shipping job with name %s. A job with same name already exists in the system and this job does not belong to log shipping category.
3202316An entry for primary server %s, primary database %s does not exist on this secondary. Register the primary first.
3202416An entry for primary server %s, primary database %s already exists.
3202516Primary Server %s, Database %s has active log shipping secondary database(s) on the secondary. Drop the secondary database(s) first.
3202610Log shipping Primary Server Alert.
3202710Log shipping Secondary Server Alert.
3202816Invalid value = %d for parameter @threshold_alert was specified.
3202910Log shipping backup agent [%s] has verified log backup file ‘%s.wrk’ and renamed it as ‘%s.trn’. This is an informational message only. No user action is required.
3203010Could not query monitor information for log shipping primary %s.%s from monitor server %s.
3203110Could not query monitor information for log shipping secondary %s.%s from monitor server %s.
3203216Invalid value ‘%d’ for update period. Update period should be between 1 and 120 minutes.
3203316The update job for the database mirroring monitor already exists.  To change the update period, use sys.sp_dbmmonitorchangemonitoring
3203416An internal error occurred when setting up the database mirroring monitoring job.
3203516An internal error occurred when modifying the database mirroring monitoring job.
3203616Parameter(s) out of range.
3203716The units for the update period for the database mirroring monitor job have been changed.
3203816An internal error has occurred in the database mirroring monitor.
3203916The database ‘%s’ is not being mirrored. No update of the base table was done.
3204016The alert for ‘oldest unsent transaction’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
3204116The database mirroring monitor base tables have not been created. Please run sys.sp_dbmmonitorupdate to create them.
3204216The alert for ‘unsent log’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
3204316The alert for ‘unrestored log’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
3204416The alert for ‘mirror commit overhead’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
3204516‘%s’ must be executed in msdb.
3204616Only members of the sysadmin fixed server role or the ‘dbm_monitor’ role in msdb can perform this operation.
3204715Database Mirroring Monitor Job
3204815Database Mirroring Monitor Schedule
3204916The database mirroring monitoring job does not exist. Run sp_dbmmonitoraddmonitoring to setup the job.
3205016Alerts cannot be created on the system databases, master, msdb, model or tempdb.
3205110System administrator privilege is required to update the base table. The base table was not updated.
3205216Parameter ‘%s’ cannot be null or empty. Specify a value for the named parameter and retry the operation.
3205316The server name, given by ‘@@servername’, is currently null.
3205416There was an error establishing a link to the remote monitor server.
3205516There was an error configuring the remote monitor server.
3205617The SQL Server failed to create full-text FTData directory. This might be because FulltextDefaultPath is invalid or SQL Server service account does not have permission. Full-text may fail until this issue is resolved. Restart SQL Server after the issue is fixed.
3300116Cannot drop the option because the option is not specified on %S_MSG.
3300216Access to %ls %ls is blocked because the signature is not valid.
3300316DDL statement is not allowed.
3300416The password of login ‘%.*ls’ is invalid. A new password should be set for this login without specifying the old password.
3300516Cannot find the certificate or asymmetric key from the file %.*ls. ErrorCode: 0x%x.
3300616WITH SIGNATURE option cannot be specified on database.
3300716Cannot encrypt symmetric key with itself.
3300816Cannot grant, deny, or revoke %.*ls permission on INFORMATION_SCHEMA or SYS %S_MSG.
3300916The database owner SID recorded in the master database differs from the database owner SID recorded in database ‘%.*ls’. You should correct this situation by resetting the owner of database ‘%.*ls’ using the ALTER AUTHORIZATION statement.
3301016The MUST_CHANGE option cannot be specified together with the HASHED option.
3301116The %S_MSG private key cannot be dropped because one or more entities are encrypted by it.
3301210Cannot %S_MSG signature %S_MSG %S_MSG ‘%.*ls’. Signature already exists or cannot be added.
3301316A %S_MSG by %S_MSG ‘%.*s’ does not exist.
3301416Cannot countersign ‘%.*s’. Only modules can be countersigned.
3301516The database principal is referenced by a %S_MSG in the database, and cannot be dropped.
3301616The user cannot be remapped to a login. Remapping can only be done for users that were mapped to Windows or SQL logins.
3301716Cannot remap a user of one type to a login of a different type. For example, a SQL user must be mapped to a SQL login; it cannot be remapped to a Windows login.
3301816Cannot remap user to login ‘%.*s’, because the login is already mapped to a user in the database.
3301916Cannot create implicit user for the special login ‘%.*s’.
3302016A HASHED password cannot be set for a login that has CHECK_POLICY turned on.
3302116Failed to generate a user instance of SQL Server. Only local user accounts, interactive users accounts, service accounts, or batch accounts can generate a user instance. The connection will be closed.%.*ls
3302216Cannot obtain cryptographic provider properties. Provider error code: %d.
3302316The %S_MSG is too long. Maximum allowed length is %d bytes.
3302416Cryptographic provider %S_MSG ‘%ls’ in dll is different from the guid recorded in system catalog for provider with id %d.
3302516Invalid cryptograpihic provider property: %S_MSG.
3302616Cryptographic provider with guid ‘%ls’ already exists.
3302716Cannot load library ‘%.*ls’. See errorlog for more information.
3302816Cannot open session for %S_MSG ‘%.*ls’. Provider error code: %d. (%S_MSG)
3302916Cannot initialize cryptographic provider. Provider error code: %d.  (%S_MSG)
3303016Cryptographic provider is not available.
3303116Cryptographic provider ‘%.*ls’ is in disabled.
3303216SQL Crypto API version ‘%02d.%02d’ implemented by provider is not supported. Supported version is ‘%02d.%02d’.
3303316Specified key type or option ‘%S_MSG’ is not supported by the provider.
3303416Cannot specify algorithm for existing key.
3303516Cannot create key ‘%.*ls’ in the provider. Provider error code: %d.  (%S_MSG)
3303610Cannot drop the key with thumbprint ‘%.*ls’ in the provider.
3303716Cannot export %S_MSG from the provider. Provider error code: %d.  (%S_MSG)
3303816Operation is not supported by cryptographic provider key.
3303916Invalid algorithm ‘%.*ls’. Provider error code: %d.  (%S_MSG)
3304016Cryptographic provider key cannot be encrypted by password or other key.
3304116Cannot create login token for existing authenticators. If dbo is a windows user make sure that its windows account information is accessible to SQL Server.
3304216Cannot add %S_MSG because it is already mapped to a login.
3304316Cannot add %S_MSG ‘%.*ls’ because there is already %S_MSG specified for the login.
3304416Cannot drop %S_MSG because there is %S_MSG referencing this provider.
3304516Cannot drop %S_MSG because it is not mapped to this login.
3304616Server principal ‘%.*ls’ has no credential associated with %S_MSG ‘%.*ls’.
3304716Fail to obtain or decrypt secret for %S_MSG ‘%.*ls’.
3304816Cannot use %S_MSG under non-primary security context.
3304916Key with %S_MSG ‘%.*ls’ does not exist in the provider or access is denied. Provider error code: %d.  (%S_MSG)
3305016Cannot create key ‘%.*ls’ in the provider. Provider does not allow specifying key names.
3305116Invalid algorithm id: %d. Provider error code: %d.  (%S_MSG)
3305216Cryptographic provider key cannot be a temporary key.
3305316Extensible Key Management is disabled or not supported on this edition of SQL Server.  Use sp_configure ‘EKM provider enabled’ to enable it.
3305416Extensible key management is not supported in this edition of SQL Server.
3305516Exception happened when calling cryptographic provider ‘%.*ls’ in the API ‘%.*ls’. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx.
3305616Cannnot impersonate login ‘%.*ls’ to access %S_MSG ‘%.*ls’.
3305710Cryptographic provider is now disabled. However users who have an open cryptographic session with the provider can still use it. Restart the server to disable the provider for all users.
3305810Cryptographic provider is now dropped. However users who have an open cryptographic session with the provider can still use it. Restart the server to drop the provider for all users.
3305916An error occurred while trying to flush all running audit sessions.  Some events may be lost.
3306016The format of supplied parameter sid is invalid. The sid might be incorrect or the sid might describe the wrong type of user.
3306116The specified RETENTION_DAYS value is greater than the maximum value allowed. The retenton days value must be less than %d days.
3306216Password validation failed. The password does not meet SQL Server password policy requirements because it is too short. The password must be at least %d characters.
3306316Password validation failed. The password does not meet SQL Server password policy requirements because it is too long. The password must be at most %d characters.
3306416Password validation failed. The password does not meet SQL Server password policy requirements because it is not complex enough. The password must be at least %d characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols.
3306610An error occurred while configuring the password policy: NTSTATUS 0x%x, state %d. To skip configuring the password policy, use trace flag -T4634 during startup. This will cause SQL Server to run using a minimal password policy.
3306916CREATE CERTIFICATE statement cannot mix file and binary modes. Rewrite the statement using only the FILE or the BINARY keyword.
3307016The specified maximum size limit for the audit log file is less than the minimum value allowed. The maximum size limit must be at least 2 MB.
3307116This command requires %S_MSG to be disabled. Disable the %S_MSG and rerun this command.
3307216The audit log file path is invalid.
3307316Cannot find %S_MSG ‘%.*ls’ or you do not have the required permissions.
3307416Cannot %S_MSG a %S_MSG %S_MSG from a user database. This operation must be performed in the master database.
3307516Granular auditing is not available in this edition of SQL Server. For more information about feature support in the editions of SQL Server, see SQL Server Books Online.
3307616The specified maximum size limit is greater than the maximum value allowed. The maximum size limit must be less than 16777215 TB.
3307716RESERVE_DISK_SPACE cannot be specified when setting MAXSIZE = UNLIMITED. Either reduce MAXSIZE or do not specify RESERVE_DISK_SPACE.
3307816The containment setting in the master database does not match the property of the database files. Use ALTER DATABASE to reset the containment property.
3307916Cannot bind a default or rule to the CLR type ‘%s’ because an existing sparse column uses this data type. Modify the data type of the sparse column or remove the sparse designation of the column.
3308010Cryptographic provider library ‘%.*ls’ loaded into memory. This is an informational message only. No user action is required.
3308110Failed to verify Authenticode signature on DLL ‘%.*ls’.
3308216Cannot find Cryptographic provider library with guid ‘%ls’.
3308316Cannot create %S_MSG for %S_MSG ‘%ls’ because it is not supported by the extensible key management provider ‘%ls’.
3308416The OPEN SYMMETRIC KEY statement cannot reference a symmetric key created from an Extensible Key Management (EKM) provider. Symmetric keys created from an EKM provider are opened automatically for principals who can successfully authenticate with the cryptographic provider.
3308510One or more methods cannot be found in cryptographic provider library ‘%.*ls’.
3308610SQL Server Audit failed to record %ls action.
3308716%S_MSG property of the key returned by EKM provider doesn’t match the expected value
3308816The algorithm: %.*ls is not supported for EKM operations by SQL Server
3308916Key validation failed since an attempt to get algorithm info for that key failed. Provider error code: %d.  (%S_MSG)
3309010Attempting to load library ‘%.*ls’ into memory. This is an informational message only. No user action is required.
3309110Warning: The certificate used for encrypting the database encryption key has not been backed up. You should immediately back up the certificate and the private key associated with the certificate. If the certificate ever becomes unavailable or if you must restore or attach the database on another server, you must have backups of both the certificate and the private key or you will not be able to open the database.
3309210Failed to verify the Authenticode signature of ‘%.*ls’. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
3309316The Windows user or group ‘%s’ is local or built-in. Use a Windows domain user or domain group.
3309410An error occurred during Service Master Key %S_MSG
3309510Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
3309610A generic failure occurred during Service Master Key encryption or decryption.
3309710Processing BrickId: %d with MasterDb.PrimaryPru.FragId %d
3309810Initializing SMK for brickId: %d
3309916You cannot add server-scoped catalog views, system stored procedures, or extended stored procedures to a database audit specification in a user database. Instead add them to a database audit specification in the master database.
3310116Cannot use %S_MSG ‘%.*ls’, because its private key is not present or it is not protected by the database master key. SQL Server requires the ability to automatically access the private key of the %S_MSG used for this operation.
3310216Cannot encrypt a system database. Database encryption operations cannot be performed for ‘master’, ‘model’, ‘tempdb’, ‘msdb’, or ‘resource’ databases.
3310316A database encryption key already exists for this database.
3310416A database encryption key does not exist for this database.
3310516Cannot drop the database encryption key because it is currently in use. Database encryption needs to be turned off to be able to drop the database encryption key.
3310616Cannot change database encryption state because no database encryption key is set.
3310716Cannot enable database encryption because it is already enabled.
3310816Cannot disable database encryption because it is already disabled.
3310916Cannot %S_MSG database encryption while an encryption, decryption, or key change scan is in progress.
3311016Cannot change database encryption key while an encryption, decryption, or key change scan is in progress.
3311116Cannot find server %S_MSG with thumbprint ‘%.*ls’.
3311210Beginning database encryption scan for database ‘%.*ls’.
3311310Database encryption scan for database ‘%.*ls’ is complete.
3311410Database encryption scan for database ‘%.*ls’ was aborted. Reissue ALTER DB to resume the scan.
3311516CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on the database. Try again later.
3311616CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database ‘%.*ls’. Try again later.
3311716Transparent Data Encryption is not available in the edition of this SQL Server instance. See books online for more details on feature support in different SQL Server editions.
3311816Cannot enable or modify database encryption on a database that is read-only, has read-only files or is not recovered.
3311916Cannot modify filegroup read-only/read-write state while an encryption transition is in progress.
3312016In order to encrypt the database encryption key with an %S_MSG, please use an %S_MSG that resides on an extensible key management provider.
3312116The %S_MSG ‘%ls’ does not have a login associated with it.  Create a login and credential for this key to automatically access the extensible key management provider ‘%ls’.
3312216This command requires a database encryption scan on database ‘%.*ls’. However, the database has changes from previous encryption scans that are pending log backup. Take a log backup and retry the command.
3312316Cannot drop or alter the database encryption key since it is currently in use on a mirror or secondary availability replica. Retry the command after all the previous reencryption scans have propagated to the mirror or secondary availability replicas or after availability relationship  has been disabled.
3312410Database encryption scan for database ‘%.*ls’ cannot complete since one or more files are offline. Bring the files online to run the scan to completion.
3312510Can not create login token because there are too many secondary principals. The maximum number of allowed secondary principals allowed is %lu. To fix this, remove the login from a server role.
3312610Database encryption key is corrupted and cannot be read.
3312716The %S_MSG cannot be dropped because it is used by one or more databases to encrypt a Database Encryption Key.
3312816Encryption failed. Key uses deprecated algorithm ‘%.*ls’ which is no longer supported at this db compatibility level. If you still need to use this key switch to a lower db compatibility level.
3312916Cannot use ALTER LOGIN with the ENABLE or DISABLE argument for a Windows group. GRANT or REVOKE the CONNECT SQL permission instead.
3313016Principal ‘%ls’ could not be found or this principal type is not supported.
3313116Principal ‘%ls’ has a duplicate display name. Make the display name unique in Azure Active Directory and execute this statement again.
3313216This principal type is not supported in Windows Azure SQL Database.
3313316Your subscription is not enabled for Integrated Authentication.
3313416Principal ‘%ls’ could not be resolved. Error message: ‘%ls’
3313516Altering the name of a Windows principal is not supported through this form of execution. For more information about this, see SQL Server Books Online.
3313616The operation could not be completed at this time. Please try again later.
3313716The tenant ‘%.*ls’ cannot be found.
3313816ALTER DATABASE on a federation member is not supported for Windows users or groups.
3313916This subscription does not support Integrated Authentication.
3314016The login ‘%.*ls’ could not be created because a login is already associated with certificate ‘%.*ls’.
3314110The credential created might not be able to decrypt the database master key. Please ensure a database master key exists for this database and is encrypted by the same password used in the stored procedure.
3314216Updating the tenantId for Azure SQL Server was not successful.
3314316The account admin of the subscription does not belong to this tenant.
3314416Cannot change the schema of a temporary object.
3314610The database ‘%.*ls’ is offline. The credential was created but SQL Server is unable to determine if the credential can decrypt the database master key.
3314720Federated Authentication Feature data used in login record to open a connection is structurally or semantically invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls.
3314816The user name for a windows login has to be identical to the login name.
3314916Dropping a credential ‘%.*ls’ which could still be used by Managed Backup.
3315016Warning: Can not check whether the credential ‘%.*ls’ is used by managed backup, because %ls. Please check whether the credential is used by managed backup.
3315116The user name for a user with password cannot be identical to the name of the server admin or the dbo of the database.
3315216Valid values of the database compatibility level are %d or %d.
3315316Valid values of the database compatibility level are %d, %d, or %d.
3315420Client sent an invalid token when server was expecting federated authentication token. And it was not a disconnect event.
3315520A disconnect event was raised when server is waiting for Federated Authentication token. This could be due to client close or server timeout expired.
3315620A Federated Authentication token was sent by the client when the server is not expecting it. So server will close the connection due to TDS non-conformance.
3315716Crypthographic providers are not supported on database credentials.
3315816Database credentials are not supported in master database.
3315916Principal ‘%ls’ could not be created. Only connections established with Active Directory accounts can create other Active Directory users.
3316010Unable to verify Authenticode signatures due to error code %d. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
3316115Database master keys without password are not supported in this version of SQL Server.
3316216TYPE and SID options have to be used along with each other, in this version of SQL Server.
3316316The value specified for TYPE option is not supported in this version of SQL Server. Allowed values are E (EXTERNAL_USER) and X (EXTERNAL_GROUP)
3316416Cannot drop the credential ‘%.*ls’ because it is used by an external data source.
3316516Cannot drop the external %ls ‘%.*ls’ because it is used by an external table.
3316616dbManager permission check failed.
3316716This command is not supported for Azure AD users. Execute this command as a SQL Authenticated user.
3316816TYPE option cannot be used along with FOR/FROM LOGIN, CERTIFICATE, ASYMMETRIC KEY, EXTERNAL PROVIDER, WITHOUT LOGIN or WITH PASSWORD, in this version of SQL Server.
3316916User name cannot have backslash character, when using the TYPE option.
3317016SID option cannot be used along with FOR/FROM LOGIN, CERTIFICATE, ASYMMETRIC KEY, EXTERNAL PROVIDER, WITHOUT LOGIN or WITH PASSWORD, in this version of SQL Server.
3317116Only active directory users can impersonate other active directory users.
3317216Encrypting Secret for Database ‘%.*ls’ and Credential ‘%.*ls’ failed.
3317316Assigning value for output parameter @credentialSecret failed because the parameter size is less than the required size %u. Please provide a larger size.
3317416Cannot get credential ‘%.*ls’ because it is not referenced by any external data source.
3317516Encryption operation failed. Key used for encryption has deprecated algorithm ‘%.*ls’ which is no longer supported at this db compatibility level. If you still need to use this key switch to a lower db compatibility level.
3317616Signing operation failed. Key uses deprecated algorithm ‘%.*ls’ which is no longer supported at this db compatibility  level. If you still need to use this key switch to a lower db compatibility level.
3317716Hash operation failed. Hash Function uses deprecated algorithm ‘%.*ls’ which is no longer supported at this db compatibility level. If you still need to use this hash algorithm switch to a lower db compatibility level.
3317816Encryption key length is over the currently supported maximum length of %d.
3317910Searching for ‘%.*ls’ only searches “‘%.*ls'” for SQL Server authentication logins.
3318010Searching for “‘%.*ls'” only searches for Azure Active Directory users. To search for a SQL Server authentication login, add the server name at the end. For example [%.*[email protected]%.*ls].
3318116The new owner cannot be Azure Active Directory group.
3318216The command must be executed on the target database ‘%.*ls’.
3318316The Azure Key Vault client encountered an error with message ‘%s’.
3318416An error occurred while obtaining information for the Azure Key Vault client with message ‘%s’.
3318516An error ocurred while attempting to copy the encrypted DEK from the DBTable.
3318616Cannot alter the credential ‘%.*ls’ because it is being used by an active audit session (‘%.*ls’).
3318716Internal enclave error. Enclave failed to decrypt a column value or parameter – invalid authentication tag. For more information, contact Customer Support Services.
3318916Internal enclave error: Enclave is out of session resources. For more information, contact Customer Support Services.
3319016Internal enclave error. Enclave attestation information requested for an unsupported enclave type. For more information, contact Customer Support Services.
3319116Enclave host encountered a runtime error: out of priority queue space.
3319216Internal enclave error. Enclave raised an exception (major = %d, minor = %d). See error log for more information. For more information, contact Customer Support Services.
3319416Internal enclave error. The enclave bcrypt method %hs failed with status 0x%x. For more information, contact Customer Support Services.
3319517Internal enclave error. Enclave was provided with an invalid session handle. For more information, contact Customer Support Services.
3319616Windows Management Instrumentation (WMI) error encountered during VBS enclave attestation. API: ‘%s’, ReturnCode: ‘%ld’.
3319716The value specified for TYPE option is not supported in this version of SQL Server. Allowed values are E (EXTERNAL_USER) and X (EXTERNAL_GROUP).
3319816TYPE and SID options have to be used along with each other, in this version of SQL Server.
3319916Only Active Directory logins can impersonate other Active Directory logins.
3320117An error occurred in reading from the audit file or file-pattern: ‘%s’. The SQL service account may not have Read permission on the files, or the pattern may be returning one or more corrupt files.
3320217SQL Server Audit could not write to file ‘%s’.
3320317SQL Server Audit could not write to the event log.
3320417SQL Server Audit could not write to the security log.
3320510Audit event: %s.
3320617SQL Server Audit failed to create the audit file ‘%s’. Make sure that the disk is not full and that the SQL Server service account has the required permissions to create and write to the file.
3320717SQL Server Audit failed to access the event log. Make sure that the SQL service account has the required permissions to the access the event log.
3320817SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to access the security log.
3320910Audit ‘%.*ls’ has been changed to ON_FAILURE=CONTINUE because the server was started by using the -m flag. because the server was started with the -m flag.
3321010SQL Server Audit failed to start, and the server is being shut down.  To troubleshoot this issue, use the -m flag (Single User Mode) to bypass Audit-generated shutdowns when the server is starting.
3321115A list of subentities, such as columns, cannot be specified for entity-level audits.
3321215There is an invalid column list after the object name in the AUDIT SPECIFICATION statement.
3321316All actions in an audit specification statement must be at the same scope.
3321417The operation cannot be performed because SQL Server Audit has not been started.
3321510One or more audits failed to start. Refer to previous errors in the error log to identify the cause, and correct the problems associated with each error.
3321610SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
3321710SQL Server Audit is starting the audits. This is an informational message. No user action is required.
3321810SQL Server Audit has started the audits. This is an informational message. No user action is required.
3321910The server was stopped because SQL Server Audit ‘%.*ls’ is configured to shut down on failure. To troubleshoot this issue, use the -m flag (Single User Mode) to bypass Audit-generated shutdowns when the server is starting.
3322016Audit actions at the server scope can only be granted when the current database is master.
3322116You can only create audit actions on objects in the current database.
3322210Audit ‘%.*ls’ failed to %S_MSG . For more information, see the SQL Server error log. You can also query sys.dm_os_ring_buffers where ring_buffer_type = ‘RING_BUFFER_XE_LOG’.
3322316ALTER SERVER AUDIT requires the STATE option to be specified without using any other options.
3322416The specified pattern did not return any files or does not represent a valid file share. Verify the pattern parameter and rerun the command.
3322516The specified values for initial_file_name and audit_record_offset do not represent a valid location within the audit file set. Verify the file name and offset location, and then rerun the command.
3322610The fn_get_audit_file function is skipping records from ‘%.*ls’ at offset %I64d.
3322716The specified value for QUEUE_DELAY is not valid. Specify either 0 or 1000 and higher.
3322816You cannot configure SQL Server Audit to shutdown the server because you do not have the permission to shut down the server. Contact your system administrator.
3322916Changes to an audit specification must be done while the audit specification is disabled.
3323016An audit specification for audit ‘%.*ls’ already exists.
3323116You can only specify securable classes DATABASE, SCHEMA, or OBJECT in AUDIT SPECIFICATION statements.
3323216You may not add a role to Sysadmin.
3323316You can only create a user with a password in a contained database.
3323416The parameter %s cannot be provided for users that cannot authenticate in a database.
3323516The parameter %s cannot be provided for users that cannot authenticate in a database. Remove the WITHOUT LOGIN or PASSWORD clause.
3323616The default language parameter can only be provided for users in a contained database.
3323716Cannot use parameter %s for Windows users or groups.
3323816MAX_FILES and MAX_ROLLOVER_FILES options cannot be specified toghether.
3323916An error occurred while auditing this operation. Fix the error in the audit and then retry this operation.
3324016A failure occurred during initializing of an Audit. See the errorlog for details.
3324116Failed to configure user instance on startup. Error updating the idle timeout.
3324216When providing a sid, the user must be a user without login or a user with password.
3324316Failed to generate a user instance of SQL Server due to a failure in setting access control list on the user instance’s process. The connection will be closed.%.*ls
3324417SQL Server Audit failed to create an audit file related to the audit ‘%s’ in the directory ‘%s’. Make sure that the disk is not full and that the SQL Server service account has the required permissions to create and write to the file.
3324517SQL Server Audit failed to write to an audit file related to the audit ‘%s’ in the directory ‘%s’. Make sure that the disk is not full and that the SQL Server service account has the required permissions to create and write to the file.
3324617SQL Server Audit failed to access the MDS file log. Make sure that the disk is not full and that the SQL Server service account has the required permissions to create and write to the file.
3324717SQL Server Audit could not write to the MDS local file (Error Code: %d).
3324816The specified value for QUEUE_DELAY is not valid for MDS log target. Specify value higher than 0.
3324916Cannot drop the credential ‘%.*ls’ because it is being used.
3325016Failed to allocate memory for caching credential ‘%.*ls’ which is used by a database file.
3325116A credential conflicting with ‘%.*ls’ already exists in credential cache in memory. Use alter step to change the secret. Drop and re-create to change the credential name.
3325216This CREATE AUDIT request exceeds the maximum number of audits that can be created per database.
3325316Failed to modify the identity field of  the credential ‘%.*ls’ because the credential is used by an active database file.
3325416This operation cannot be performed in the master database.
3325516Audit specification ‘%.*ls’ can only be bound to a %S_MSG audit.
3325616The audit store location or the audit store URL has been configured for this database audit.
3325716Cannot drop an audit store URL that is not configured for this database audit.
3325816Invalid value for procedure “%.*ls”, parameter “%.*ls”.
3325915Invalid security policy name ‘%.*ls’.
3326016The predicate was not added to the security policy ‘%.*ls’ because there are no available predicate IDs. Drop and recreate the security policy.
3326116The security policy ‘%.*ls’ does not contain a predicate on table ‘%.*ls’.
3326216A %S_MSG predicate for the same operation has already been defined on table ‘%.*ls’ in the security policy ‘%.*ls’.
3326316Security predicates can only be added to user tables and schema bound views. ‘%.*ls’ is not a user table or a schema bound view.
3326416The security policy ‘%.*ls’ cannot be enabled with a predicate on table ‘%.*ls’. Table ‘%.*ls’ is already referenced by the enabled security policy ‘%.*ls’.
3326516The security policy ‘%.*ls’ cannot have a predicate on table ‘%.*ls’ because this table is referenced by the indexed view ‘%.*ls’.
3326616The index on the view ‘%.*ls’ cannot be created because the view is referencing table ‘%.*ls’ that is referenced by a security policy.
3326716Security predicates cannot reference memory optimized tables. Table ‘%.*ls’ is memory optimized.
3326816Cannot find the object “%.*ls” because it does not exist or you do not have permissions.
3326916Security predicates are not allowed on temporary objects. Object names that begin with ‘#’ denote temporary objects.
3327016Cannot find the object “%.*ls” or this object is not an inline table-valued function.
3327116Cannot alter ‘%.*ls’ because it is not a security policy.
3327216Unable to load the security predicate for table “%.*ls”.
3327316Security predicates cannot be added on FileTables. ‘%.*ls’ is a FileTable.
3327416The version was not created for the key ‘%.*ls’ because there are no available version IDs. Drop and recreate the key.
3327516The encrypted value for this column encryption key cannot be dropped. Each column encryption key must have at least one encrypted value.
3327716Encryption scheme mismatch for columns/variables %.*ls. The encryption scheme for the columns/variables is %ls and the expression near line ‘%d’ expects it to be %ls.
3327816Cannot assign the same encryption scheme to two expressions at line ‘%d’. The encryption scheme of the first expression is %ls and the encryption scheme of the second expression is %ls. Other columns/variables with the same encryption scheme as the first expression are: %.*ls. Other columns/variables with the same encryption scheme as the second expression are: %.*ls.
3327916Cannot remove the credential ‘%.*ls/%.*ls’ because it is being used.
3328016Cannot create or alter encrypted column ‘%.*ls’ because data type ‘%ls’ is not supported for encryption.
3328116Column ‘%.*ls.%.*ls’ has a different encryption scheme than referencing column ‘%.*ls.%.*ls’ in foreign key ‘%.*ls’.
3328216Column ‘%.*ls.%.*ls’ is encrypted using a randomized encryption type and is therefore not valid for use as a key column in a constraint, index, or statistics.
3328316‘%S_MSG’ clause is unsupported for encrypted columns.
3328416The encrypted column ‘%.*ls.%.*ls’ cannot be used as a partition key column.
3328516Cannot set default constraint on encrypted column ‘%.*ls.%.*ls’. Default constraints are unsupported on encrypted columns.
3328616Cannot encrypt column ‘%.*ls’, because it is of a user-defined type.
3328716Cannot drop column encryption key ‘%.*ls’ because the key is referenced by column ‘%.*ls.%.*ls’.
3328816The encrypted value for the column encryption key cannot be added. There can be no more than two encrypted values for each column encryption key. Drop an exisiting encrypted value before adding the new one.
3328916Cannot create or alter encrypted column ‘%.*ls’. Character strings that do not use a *_BIN2 collation cannot be encrypted using deterministic encryption.
3329016There is no column encryption key value associated with the column master key ‘%.*ls’.
3329116There is already a column encryption key value associated with the column master key ‘%.*ls’.
3329216The encryption algorithm ‘%.*ls’ is not supported. Please specify a valid encryption algorithm.
3329316Cannot find the %S_MSG “%.*ls” because it does not exist or you do not have permissions.
3329416Some parameters or columns of the batch require to be encrypted, but the corresponding column encryption key cannot be found. Use sp_refresh_parameter_encryption to refresh the module parameters metadata.
3329616Cannot create table ‘%.*ls’ since it references a column encryption key from a different database.
3329716Cannot create %S_MSG. The %S_MSG cannot be empty.
3329816Internal Query Processor Error: The encryption scheme of certain parameters was incorrectly analyzed. For more information, contact Customer Support Services.
3329916Encryption scheme mismatch for columns/variables %.*ls. The encryption scheme for the columns/variables is %ls and the expression near line ‘%d’ expects it to be %ls (or weaker).
3330116The %ls that is specified for conversation priority ‘%.*ls’ is not valid. The value must be between 1 and %d characters long.
3330216The %ls that is specified for conversation priority ‘%.*ls’ is not valid. The value must be between 1 and 10.
3330316A conversation priority already exists in the database with either the name ‘%.*ls’ or the properties %ls=’%ls’, %ls=’%ls’, and %ls=’%.*ls’. Either use a unique name or a unique set of properties.
3330416The transmission queue row with conversation handle ‘%ls’ and message sequence number %d references a missing multicast message body row with reference %d.
3330516The multicast message body row with reference %d should have reference count value of %d.
3330616The unreferenced message with reference %d has been deleted from the message body table.
3330716The message with reference %d has been updated to a reference count of %d in the message body table.
3330810The queue %d in database %d has activation enabled and contains unlocked messages but no RECEIVE has been executed for %u seconds.
3330910Cannot start cluster endpoint because the default %S_MSG endpoint configuration has not been loaded yet.
3331016Local cluster name can be set only once.
3331110The wait for connect request completion failed.
3331210The wait for querying proxy routes failed or was aborted.
3331316An out of memory condition has occurred in the Service Broker transport layer. A service broker connection is closed due to this condition.
3331416The supplied whitelist is invalid.
3331516The redirected endpointurl is Invalid
3331616Failed to reset encryption while performing redirection.
3331716The redirect response contains invalid redirect string
3331816The redirect request contains invalid string or redirect handler failed to handle the request
3331916The redirector returned lookup failure
3332016Tried to send redirect request but the redirect string is empty
3332116The other end does not support redirection
3332216The redirect message is corrupted
3332316The endpoint is closing because the connection was redirected
3332416Failed to parse the redirect info string
3332516Failed to construct new endpoint after redirection
3332616Forwarder disconnected during redirection
3332716Failed to parse the specified connection string
3332816Redirector lookup failed with error code: %x
3332916XdbHost encountered error code: %x during socket duplication
3333016XdbHost returned an error during socket duplication
3333116DBCC CLEANUPCONVERSATIONS is not allowed on this server.
3333216DBCC CLEANUPCONVERSATIONS cannot be executed through MARS connection.
3333310The connection had a send posted for over %d seconds. The connection is suspected hung and is being closed.
3333410Error while setting up ssl channel. Error code: (%d, %d, %d)
3333510The connection has been flow controlled in the %d seconds (%d times, where threshold is %d). Min required transfer rate is %d Kbps. Actual transfer rate is %d Kbps. The connection is extensively flow controlled and is being closed.
3340116FILESTREAM database options cannot be set on system databases such as ‘%.*ls’.
3340216An invalid directory name ‘%.*ls’ was specified. Use a valid operating system directory name.
3340316The case-sensitive or binary collation ‘%.*ls’ cannot be used with the COLLATE_FILENAME option. Change the collation to a case-insensitive collation type.
3340416The database default collation ‘%.*ls’ is case sensitive and cannot be used to create a FileTable. Specify a case insensitive collation with the COLLATE_FILENAME option.
3340516An error occurred during the %S_MSG %S_MSG operation on a FileTable object. (HRESULT = ‘0x%08x’).
3340616An invalid filename, ‘%.*ls’, caused a FileTable check constraint error. Use a valid operating system filename.
3340716An invalid path locator caused a FileTable check constraint error.  The path locator cannot indicate a root row. Correct the path locator or use the default value.
3340816The operation caused a FileTable check constraint error.  A directory entry cannot have a data stream associated with the row. Remove the blob data or clear the is_directory flag.
3340916The operation caused a FileTable check constraint error. A file entry cannot have a NULL value for the data stream associated with the row. Insert file data or use 0x to insert a zero length file.
3341016An invalid path locator caused a FileTable check constraint error.  The parent of a row’s path locator must be a directory, not a file.  Correct the path locator to refer to a parent that is a directory.
3341116The option ‘%.*ls’ is only valid when used on a FileTable. Remove the option from the statement.
3341216The option ‘%.*ls’ is not valid when used with the ‘%.*ls’ syntax. Remove the option from the statement.
3341316The option ‘%.*ls’ can only be specified once in a statement. Remove the duplicate option from the statement.
3341416FileTable objects require the FILESTREAM database option DIRECTORY_NAME to be non-NULL. To create a FileTable in the database ‘%.*ls’, set the DIRECTORY_NAME option to a non-NULL value using ALTER DATABASE. Or, to set the DIRECTORY_NAME option to NULL, in the database ‘%.*ls’ disable or drop the existing FileTables.
3341516FILESTREAM DIRECTORY_NAME ‘%.*s’ attempting to be set on database ‘%.*s’ is not unique in this SQL Server instance. Provide a unique value for the database option FILESTREAM DIRECTORY_NAME to enable non-transacted access.
3341610When the FILESTREAM database option NON_TRANSACTED_ACCESS is set to FULL and the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION options are on, T-SQL and transactional read access to FILESTREAM data in the context of a FILETABLE is blocked.
3341716An invalid path locator caused a FileTable check constraint error.  The path locator has a level of %d, which is deeper than the limit of %d supported by FileTable. Reduce the depth of the directory hierarchy.
3341816FILETABLE_DIRECTORY ‘%.*s’ attempting to be set on table ‘%.*s’ is not unique in the database ‘%.*s’. Provide a unique value for the option FILETABLE_DIRECTORY to this operation.
3341916Function %ls is only valid on the varbinary(max) FILESTREAM column in a FileTable.
3342016Unable to process object ‘%.*s’ because it is a three-part or four-part name. Specifying the server or database is not supported in the object identifer.
3342116The object name ‘%.*s’ is not a valid FileTable object.
3342216The column ‘%.*s’ cannot be added to table ‘%.*s’ as it is a FileTable. Adding columns to the fixed schema of a FileTable object is not permitted.
3342316Invalid FileTable path name or format.
3342416Invalid computer host name in the FileTable path.
3342516Invalid share name in the FileTable path.
3342616INSERT, UPDATE, DELETE, or MERGE to FileTable ‘%.*ls’ is not allowed inside a trigger on a FileTable.
3342716Function %ls is not allowed on the deleted table inside a trigger.
3342814User does not have permission to kill non-transacted FILESTREAM handles in database ID %d.
3342916The non-transacted FILESTREAM handle %d does not exist.
3343010Killed %d non-transactional FILESTREAM handles from database ID %d.
3343116An invalid path locator caused a FileTable check constraint error.  The path locator has a length of %d, which is longer than the limit of %d allowed for depth %d. Reduce the length of the path locator.
3343310Unable to perform the Filetable lost update recovery for database id %d.
3343416The current state of the database ‘%.*s’ is not compatible with the specified FILESTREAM non-transacted access level. The database may be read only, single user or set to emergency state.
3343516Cannot publish the FileTable ‘%ls’ for replication.  Replication is not supported for FileTable objects.
3343616Cannot enable Change Data Capture on the FileTable ‘%ls’.  Change Data Capture is not supported for FileTable objects.
3343716Cannot publish the logbased view ‘%ls’ for replication.  Replication is not supported for logbased views that depend on FileTable objects.
3343816Cannot enable Change Tracking on the FileTable ‘%.*ls’.  Change Tracking is not supported for FileTable objects.
3343916Cannot use IGNORE_CONSTRAINTS hint when inserting into FileTable ‘%.*ls’, unless FILETABLE_NAMESPACE is disabled.
3344016When inserting into FileTable ‘%.*ls’ using BCP or BULK INSERT, either CHECK_CONSTRAINTS option needs to be on, or FILETABLE_NAMESPACE needs to be disabled on the table.
3344116The FileTable ‘%.*s’ cannot be partitioned. Partitioning is not supported on FileTable objects.
3344216The handle ID %d is opened against the server root share and cannot be killed. The lifetime of the handle is controlled by the client who originally opened it.
3344316The database ‘%.*s’ cannot be enabled for both FILESTREAM non-transacted access and Database Mirroring.
3344416The database ‘%.*s’ cannot be enabled for both FILESTREAM non-transacted access and HADR.
3344516The database ‘%.*s’ is a readable secondary database in an availability group and cannot be enabled for FILESTREAM non-transacted access.
3344616The FILESTREAM database configuration cannot be changed for database ‘%.*s’.  The database is either a mirror database in Database Mirroring, or is in a secondary replica of an Always On availability group.  Connect to the server instance that hosts the primary database replica, and retry the operation.
3344716Cannot access file_stream column in FileTable ‘%.*ls’, because FileTable doesn’t support row versioning. Either set transaction level to something other than READ COMMITTED SNAPSHOT or SNAPSHOT, or use READCOMMITTEDLOCK table hint.
3344816Cannot disable clustered index ‘%.*ls’ on FileTable ‘%.*ls’ because the FILETABLE_NAMESPACE is enabled.
3344910FILESTREAM File I/O access is enabled, but no listener for the availability group is created. A FILESTREAM PathName will be unable to refer to a virtual network name (VNN) and, instead, will need to refer to a physical Windows Server Failover Clustering (WSFC) node. This might limit the usability of FILESTEAM File I/0 access after an availability group failover. Therefore, we recommend that you create a listener for each availability group. For information about how to create an availability group listener, see SQL Server Books Online.
3345010FILESTREAM File I/O access is enabled. One or more availability groups (‘%ls’) currently do not have a listener.  A FILESTREAM PathName will be unable to refer to a virtual network name (VNN) and, instead, will need to refer to a physical Windows Server Failover Clustering (WSFC) node. This might limit the usability of FILESTEAM File I/0 access after an availability group failover. Therefore, we recommend that you create a listener for each availability group. For information about how to create an availability group listener, see SQL Server Books Online.
3350116Security predicates cannot be added on tables that contain filestream data. Column ‘%.*ls’ on table ‘%.*ls’ contains filestream data.
3350216The column ‘%.*ls’ could not be added to table ‘%.*ls’ because the column contains filestream data and the table is referenced by one or more security policies. Filestream columns are not allowed on tables that are referenced by security policies.
3350316BLOCK predicates can only be added to user tables. ‘%.*ls’ is not a user table.
3350416The attempted operation failed because the target object ‘%.*ls’ has a block predicate that conflicts with this operation. If the operation is performed on a view, the block predicate might be enforced on the underlying table. Modify the operation to target only the rows that are allowed by the block predicate.
3350516Partitioned view ‘%.*ls’ is not updatable because table ‘%.*ls’ has an enabled security policy that defines block predicates for this table.
3350616Only natively compiled inline table-valued functions can be used for security predicates on memory optimized tables. Table ‘%.*ls’ is memory optimized, but function ‘%.*ls’ is not natively compiled. Recreate the function using WITH NATIVE_COMPILATION.
3350716Function ‘%ls’ cannot be used in the definition of BLOCK security predicates. Modify the BLOCK security predicates for this table or view to not use this function.
3350816Column ‘%.*ls’ cannot be passed as a parameter for a BLOCK security predicate because the column definition contains an expression using a window function. Modify the BLOCK security predicates for this view to not use this column.
3350916Column ‘%.*ls’ cannot be passed as a parameter for an AFTER UPDATE or AFTER INSERT BLOCK security predicate for this view because it refers to a base table that is not being modified in this statement. Modify the AFTER INSERT and AFTER UPDATE BLOCK security predicates for this view to not use this column.
3351016BLOCK security predicates cannot reference temporal history tables. Table ‘%.*ls’ is a temporal history table.
3351116Table ‘%.*ls’ is memory optimized. Only security policies with schema binding enabled may specify security predicates for memory optimized tables. Create a new security policy with schema binding enabled.
3351216Binding for the non-schema bound security predicate on object ‘%.*ls’ failed with one or more errors, indicating the schema of the predicate function has changed. Update or drop the affected security predicates.
3351316Binding for the non-schema bound security predicate on object ‘%.*ls’ failed, because the predicate function is not an inline table-valued function. Only inline table-valued functions can be used for security predicates.
3351416Incorrect parameter encryption metadata was received from the client. The error occurred during the invocation of the batch and therefore the client can refresh the parameter encryption metadata by calling sp_describe_parameter_encryption and retry.
3351516The parameter “%.*ls” does not have the same encryption information as the one it was created with. Use sp_refresh_parameter_encryption to refresh the parameter encryption information for the module.
3351616The object ‘%.*ls’ is referenced by the security policy ‘%.*ls’. The currently installed edition of SQL Server does not support security policies. Either drop the security policy or upgrade the instance of SQL Server to a version that supports security policies.
3351716The column ‘%.*ls’ of the object ‘%.*ls’ is encrypted. The currently installed edition of SQL Server does not support encrypted columns. Either remove the encryption from the column or upgrade the instance of SQL Server to a version that supports encrypted columns.
3351816Valid values of the database compatibility level are %d, %d, %d, or %d.
3351916An external data source conflicting with ‘%.*ls’ already exists in EDS cache in memory. Use alter step to change the location or credential. Drop and re-create to change the EDS name.
3352016Failed to allocate memory for caching external data source ‘%.*ls’ which is used by a database file.
3352116Cannot drop the external data source ‘%.*ls’ because it is being used.
3352216Cannot remove the external data source ‘%.*ls’ because it is being used.
3352316Cryptographic failure due to insufficient memory.
3352410The fn_get_audit_file function is skipping records from ‘%.*ls’. You must be connected to database ‘%.*ls’ to access its audit logs.
3352510The fn_get_audit_file function is skipping records from ‘%.*ls’. You must be connected to server ‘%.*ls’ to access its audit logs.
3352610The fn_get_audit_file function is skipping records from ‘%.*ls’, as it does not conform to the auditing blob naming convention.
3352716Error occured while initializing the security functions lookup table. This might be because the installation of SQL Server is corrupted and a required file is missing.
3352816Valid values of the database compatibility level are %d, %d, %d, or %d.
3352916The audit filter predicate exceeds the maximum allowed length of %d characters.
3353016The combined length of audit name and blob storage container name exceeds the maximum allowed length (by %d character(s)). Please use shorter audit or container name.
3353116The specified value for QUEUE_DELAY is not valid with asynchronous log target. Specify value higher than 0.
3353216Invalid value given for parameter PATH. Please specify a valid blob container path with the following format : https://<storageName>.blob.core.windows.net/<containerName>
3353316SHUTDOWN on failure option is not supported in this version of SQL Server.
3353416Internal enclave error. Enclave loading failed: invalid path. For more information, contact Customer Support Services.
3353516Internal enclave error: Enclave call failed for method ‘%s’. For more information, contact Customer Support Services.
3353616VBS enclave attestation failed. Attestation status: ‘%ls’, substatus: ‘%ls’. For more information, see ‘https://go.microsoft.com/fwlink/?linkid=2099553’.
3353716Internal enclave error. Enclave attestation error: enclave platform returned unexpected output. For more information, contact Customer Support Services.
3353816The credentials of blob storage container ‘%.*ls’ are invalid.
3353916The blob storage ‘%.*ls’ was not found. Verify your storage account name.
3354016Invalid audit or database names, please use valid URL characters.
3354116The credentials of blob storage container ‘%.*ls’ was not found.
3354216Unsupported operation near line ‘%d’; operations on encrypted columns with string data types require a *_BIN2 collation. However, the column or the variable uses the ‘%.*ls’ collation.
3354316Cannot alter column ‘%.*ls’. The statement attempts to encrypt, decrypt or re-encrypt the column in-place using a secure enclave, but the current and/or the target column encryption key for the column is not enclave-enabled.
3354416Cannot alter column ‘%.*ls’. The statement attempts to change the encryption scheme of the column and one or more of the following column properties: collation (to a different code page), data type. Such changes cannot be combined in a single statement. Try using multiple statements.
3354516The statement requires a secure enclave, but the enclave has not been initialized in the SQL Server instance. Check the status of the enclave in sys.configurations and see https://go.microsoft.com/fwlink/?linkid=2005337 for more details.
3354616The statement triggers enclave computations, but a column encryption key, needed for the computations, has not been found inside the enclave. Check that: (1) column encryption and enclave computations are enabled on connection, (2) driver is enclave-enabled. For additional reasons see: https://go.microsoft.com/fwlink/?linkid=2086681.
3354816Internal enclave error: Enclave out of memory. For more information, contact Customer Support Services.
3354916Internal enclave error: OSF Serialization error. For more information, contact Customer Support Services.
3355016Internal enclave error: Invalid data format. For more information, contact Customer Support Services.
3355116Internal enclave error: Nonce checking in secure channel failed. For more information, contact Customer Support Services.
3355216Internal enclave error. Enclave shutdown due to a critical error. For more information, contact Customer Support Services.
3355316A failure occurred during initialization of an Audit to External Monitor target. See the errorlog for details.
3355416Encountered error 0x%08lx while waiting for encryption scan completion consensus. See the errorlog for details.
3355516Unable to find the user-specified certificate [Cert Hash(sha1) “%hs”] in the certificate store of the local computer. Please verify that certificate exists.
3355616Invalid character in the thumbprint [Cert Hash(sha1) “%hs”]. Please provide a certificate with a valid thumbprint.
3355716Invalid thumbprint length [Cert Hash(sha1) “%hs”]. Please provide a certificate with a valid thumbprint.
3355816Encryption scan can not be resumed because no encryption scan is in progress.
3355916Specified workload group does not exist. Retry with a valid workload group.
3356010TDE scan for database id [%d] was initiated on %S_DATE (UTC). The encryption scan will resume soon.
3356116Encryption scan can not be suspended because no encryption scan is in progress.
3356216TDE encryption scan state cannot be updated for database id [%d].
3356310TDE scan for database id [%d] was aborted on %S_DATE (UTC). The encryption scan will resume soon.
3356410TDE scan for database id [%d] was suspended on %S_DATE (UTC). To resume scan, run “ALTER DATABASE [%.*s] SET ENCRYPTION RESUME”.
3356516Found the certificate [Cert Hash(sha1) “%hs”] in the %S_MSG store but the SQL Server service account does not have access to it.
3356616Found the certificate [Cert Hash(sha1) “%hs”] in the %S_MSG store but it does not have a private key. Please verify and use a valid certificate.
3356716Column ‘%.*ls.%.*ls’ is encrypted using a randomized encryption type and is therefore not valid for use as a key column in a clustered index, constraint, or statistics.
3356816Internal enclave error: Structured exception within the enclave with status %d. For more information, contact Customer Support Services.
3356916Column ‘%.*ls.%.*ls’ is encrypted using a randomized encryption type using a non *_BIN2 collation and is therefore not valid for use as a key column in an index.
3357010Specified workload group does not exist. Switching to default workload group for TDE encryption scan.
3357216Encrypted index recovery: %ls %d
3357316Column ‘%.*ls.%.*ls’ is encrypted using randomized encryption with a non enclave-enabled column encryption key and is therefore not valid for use as a key column in a constraint, index, or statistics.
3357916Cannot drop a value for the column encryption key ‘%.*ls’; dropping the value makes the key enclave disabled, and one or more objects that are schema-bound to column ‘%.*ls’ depend on it.
3358016Operation supported by enclaves invoked on data encrypted with randomized encryption where the keys are not enclave-enabled. Please clear the proc cache.
3358116Cannot alter column ‘%.*ls’. The statement attempts to encrypt, decrypt or re-encrypt the column in-place using a secure enclave, but this is not supported for memory-optimized tables.
3358216Cannot create the module. Executing the module requires keys in a secure enclave, but this is not supported for memory-optimized tables.
3358610Warning: Index ‘%.*ls.%.*ls’ has an enclave-enabled key column, however Accelerated Database Recovery is not enabled for database ‘%.*ls’. Enabling it is strongly recommended to increase the database availability during recovery.
3358816Invalid encryption algorithm. Always Encrypted with secure enclaves requires data to be encrypted with the AEAD_AES_256_CBC_HMAC_SHA_256 algorithm.
3400116Dialog with queue ‘syspolicy_event_queue’ has encountered an error: %s.
3400216Dialog with queue ‘syspolicy_event_queue’ has ended.
3400316Error number %d was encountered while processing an event. The error message is: %s.
3400416Execution mode %d is not a valid execution mode.
3401016%s ‘%s’ already exists in the database.
3401116Specified value for property %s cannot be used with execution mode %d.
3401216Cannot delete %s referenced by a %s.
3401316%s ‘%s’ is referenced by a ‘%s’. Cannot add another reference.
3401416Facet does not exist.
3401516Policy group %s does not exist.
3401616Invalid target filer: %s. Only filters that restrict the first level below the Server node are allowed.
3401716Automated policies cannot reference conditions that contain script.
3401816Target type “%s” is not a valid target type.
3401916Object “%s” is invalid.
3402016Configuration option “%s” is unknown.
3402116Invalid value type for configuration option “%s”. Expecting “%s”.
3402216Policy automation is turned off.
3405016%ls
3405116%ls
3405216%ls
3405316%ls
3405416Policy Management cannot be enabled on this edition of SQL Server.
3410120An error was encountered during object serialization operation. Examine the state to find out more details about this error.
3410216An object in serialized stream has version %u but maximum supported version of this class is %u.
3410316Error in formatter during serialize/deserialize. Required to process %d elements but processed only %d elements.
3410416An error was encountered during object serialization operation. The object that failed serialization is %hs.
3490116The global lock manager encountered a severe failure.