SQL Server error messages list 22000 to 39000

SQL Server error messages list 22000 to 39000.

Following is the list of error messages for sql server (22000 to 39000):

error severity description
22101 16 The value supplied for the change_columns argument of CHANGE_TRACKING_IS_COLUMN_IN_MASK function is not valid. The value must be a bitmask returned by the CHANGETABLE(CHANGES …) function.
22102 16 The arguments supplied are not valid for the CHANGES option of the CHANGETABLE function.
22103 16 The arguments supplied are not valid for the VERSION option of the CHANGETABLE function.
22104 16 A table returned by the CHANGETABLE function must be aliased.
22105 16 Change tracking is not enabled on table ‘%.*ls’.
22106 16 The CHANGETABLE function does not support remote data sources.
22107 16 Object ‘%.*ls’ is of a data type that is not supported by the CHANGETABLE function. The object must be a user-defined table.
22108 16 The CHANGE_TRACKING_CONTEXT WITH clause cannot be used with a SELECT statement.
22109 16 The “context” argument for the CHANGE_TRACKING_CONTEXT WITH clause must be of type varbinary data type with a maximum length of 128.
22110 16 The number of columns specified in the CHANGETABLE(VERSION …) function does not match the number of primary key columns for table ‘%.*ls’.
22111 16 The column ‘%.*ls’ specified in the CHANGETABLE(VERSION …) function is not part of the primary key for table ‘%.*ls’.
22112 16 Each primary key column must be specified once in the CHANGETABLE(VERSION …) function. The column ‘%.*ls’ is specified more than once.
22113 16 %S_MSG is not allowed because the table is being tracked for change tracking.
22114 16 Change tracking options for ALTER DATABASE cannot be combined with other ALTER DATABASE options.
22115 16 Change tracking is enabled for one or more tables in database ‘%.*ls’. Disable change tracking on each table before disabling it for the database. Use the sys.change_tracking_tables catalog view to obtain a list of tables for which change tracking is enab
22116 16 Change tracking is not supported by this edition of SQL Server.
22500 16 Unexpected
22501 16 All articles in the publication passed data validation (rowcount and checksum).
22502 16 Not All articles in the publication passed data validation (rowcount only)
22503 16 Initializing.
22504 16 Applying the snapshot to the Subscriber.
22505 16 The merge completed with no data changes processed.
22506 16 No data needed to be merged.
22507 16 Uploading data changes to the Publisher.
22508 16 Downloading data changes to the Subscriber.
22509 16 Retrieving subscription information.
22510 16 Retrieving publication information.
22511 16 The merge completed successfully.
22512 16 Cannot use partition groups with unfiltered publications. Set “use_partition_groups” to “false” using sp_changemergepublication.
22513 16 Cannot use partition groups because the join filter between the following articles contains one or more functions: “%s” and “%s”.
22514 16 Cannot use partition groups because one or more filters reference the following view, which contains functions: “%s”.
22515 16 The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified for the articles in the publication. To use precomputed partitions, ensure that no circular join filter relationships exist.
22516 16 The publication “%s” was defined as having dynamic filters, but it does not contain any dynamic filters.
22517 16 The publication was defined as having no dynamic filters, but contains one or more dynamic filters.
22518 16 Cannot use column of type image, ntext, xml, CLR type, varchar(max), nvarchar(max), or varbinary(max) in a subset or join filter for article: ‘%s’.
22519 16 Cannot add a logical record relationship between tables “%s” and “%s” because a text, image, ntext, xml, varchar(max), nvarchar(max), or varbinary(max) column was referenced in the join clause.
22520 10 A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition will no longer be propagated to Subscribers in other partitions. Check the documentation for details.
22521 10 Unable to synchronize the row because the row was updated by a different process outside of replication.
22522 16 Article ‘%s’ cannot be published because it is published in another merge publication. An article that has a value of 3 for the @partition_options parameter of sp_addmergearticle (nonoverlapping partitions with a single subscription per partition) cannot
22523 16 An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship at the same time. Check article “%s”.
22524 16 Article ‘%s’ is published in another merge publication, with a different value specified for the @partition_options parameter of sp_addmergearticle. The specified value must be the same in all merge publications. Either specify the same value as the exist
22525 16 The publication “%s” cannot allow multiple subscriptions per partition if it contains articles using @partition_options = 3.
22526 16 An invalid value was specified for %s. Valid values are 0 (none), 1 (enforced partitions), 2 (nonoverlapping partitions with multiple subscriptions per partition), and 3 (nonoverlapping partitions with single subscription per partition).
22527 16 Invalid value specified for %s. Valid values are ‘day’, ‘days’, ‘dd’, ‘year’, ‘years’, ‘yy’, ‘yyyy’, ‘month’, ‘months’, ‘mm’, ‘week’, ‘weeks’, ‘wk’, ‘hour’, ‘hours’, ‘hh’, ‘minute’, ‘minutes’, ‘mi’.
22528 16 Cannot use a retention period unit other than “days” for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
22529 16 Cannot change the retention period unit for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
22530 16 Cannot update any column in article “%s” that is used in a logical record relationship clause.
22531 10 Initialization.
22532 10 Upload of Subscriber changes to the Publisher.
22533 10 Download of Publisher changes to the Subscriber.
22534 16 Character mode publication does not support partitioned tables.
22535 16 For heterogeneous publications, the %s parameters should be specified when calling “%s”.
22536 16 The %s parameter value cannot be updated or changed for heterogeneous publications.
22537 16 The job_login provided must match the Publisher login specified when adding the distribution Publisher (sp_adddistpublisher).
22538 16 Only replication jobs or job schedules can be added, modified, dropped or viewed through replication stored procedures.
22539 16 Use of parameters %s is invalid when parameter %s is set to %s.
22540 16 Cannot change publication “%s” to use sync_mode of “character”, because it contains one or more logical record relationships.
22541 16 Cannot add a logical record relationship in publication “%s” because it uses sync_mode of “character” and could have SQL Server Compact Edition subscribers.
22542 16 Invalid value for property @subscriber_upload_options. Valid values are 0 (allow uploads), 1 (disable uploads), 2 (disable uploads prohibit subscriber changes), and 3 (disable_outofpartition_subscriber_changes).
22543 16 When the publication property @allow_partition_realignment is set to “false”, the article property @subscriber_upload_options for all articles in the publication must be set to disable uploads.
22544 10 Warning: The procedure sp_mergecleanupmetadata has been deprecated. In SQL Server 2000 SP1 and later, the merge agent calls sp_mergemetadataretentioncleanup every time it runs, so manual cleanup of metadata is not needed. Ignoring passed-in parameters and
22545 16 Cannot add a logical record relationship in publication “%s” because it allows Web synchronization.
22546 16 Cannot change publication “%s” to allow Web synchronization because it contains one or more logical record relationships.
22547 16 A concurrent snapshot is not allowed for snapshot publications.
22548 16 Vertical partitioning is only allowed for log-based articles.
22549 16 A shared distribution agent (%s) already exists for this subscription.
22550 16 Cannot drop identity column “%s” from the vertical partition when identityrangemanagementoption is set to auto.
22551 16 The type “%s” is invalid. Valid types are “merge”, “tran”, and “both”.
22552 16 A valid value for parameter “@resync_date_str” needs to be provided when “@resync_type” is set to 2.
22553 16 The parameter “@resync_type” is set to “%d” but this subscription has never been successfully validated.
22554 16 Cannot change publication “%s” to use the sync_mode of “character” because it uses a retention period unit other than “day”. Use sp_changemergepublication to set the retention period unit to “day”.
22555 16 Cannot set the retention period unit to a value other than “day” for publication “%s” because it uses the sync_mode of “character” and may have SQL Server Compact Edition subscribers.
22556 16 Invalid value for the property “%s”. Valid values are 1 and 0.
22557 16 The status of the schema change could not be updated because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication “%s” to 90RTM.
22558 16 The status of the schema change could not be updated.
22559 16 The status of the schema change must be “active” or “skipped”.
22560 16 Merge replication does not allow filters that reference dynamic functions that take one or more parameters. Check the function “%s”.
22561 16 The requested operation failed because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication “%s” to 90RTM.
22562 16 Cannot change the compatibility level of a publication to a value lower than the existing value.
22563 16 contains one or more articles that do not upload changes
22564 16 uses ddl replication
22565 16 uses other than day as unit of retention period
22566 16 uses logical records
22567 16 contains one or more articles that use subscription-based or partition-based filtering
22568 16 contains one or more articles which will not compensate for errors
22569 16 contains one or more schema only articles
22570 16 contains one or more articles that use automatic identity range management
22571 16 contains one or more articles that use datatypes new in SQL Server 2000
22572 16 contains one or more articles with a timestamp column
22573 16 uses snapshot compression with snapshot_in_defaultfolder set to false
22574 16 contains one or more articles that use vertical partitioning
22575 16 When article property ‘published_in_tran_pub’ is set to ‘true’ then article property ‘upload_options’ has to be set to disable uploads.
22576 10 Invalid failover_mode value of %d was specified for [%s].[%s].[%s], setting to 0 [immediate].
22577 16 Failed to add subscription because the allowed number of %s subscriptions for SQL Workgroup Edition Publisher ‘%s’ would be exceeded. The maximum allowed number is %d.
22578 16 Cannot change publication “%s” to disallow use_partition_groups because it contains one or more logical record relationships. When using logical record relationships the publication must set the @use_partition_groups property to ‘true’.
22579 16 The subscription to publication ‘%s’ was not found but a shared agent does exist. To specify a subscription to a publication that is replicated via a shared agent specify ‘%s’ for the publication name.
22580 16 Cannot publish database ‘%s’ because it is marked as published on a different server. Before attempting to publish this database, execute sp_replicationdboption, specifying a value of FALSE for ‘publish’ and ‘merge publish’.
22581 16 Article ‘%s’ cannot be added or modified in publication ‘%s’. The replication of FILESTREAM columns is not supported for publications that have a ‘sync_mode’ of 1 (character mode). Specify a ‘sync_mode’ of 0 (native mode) for the publication by using sp_a
22582 16 Article ‘%s’ cannot be added or modified in publication ‘%s’. The replication of FILESTREAM columns is not supported for publications that have a ‘publication_compatibility_level’ of less than “90RTM” (SQL Server 2005). Specify a ‘publication_compatibilit
22583 16 Article ‘%s’ cannot be added or modified in publication ‘%s’. The replication of FILESTREAM columns is not supported for articles that have a ‘schema_option’ set to 0x20000000. This converts large object data types to data types that are supported on earl
22584 10 Warning: Values of some of the flags specified in the ‘schema_option’ property are not compatible with the publication’s compatibility level. The modified schema_option value of ‘%s’ will be used instead.
22585 10 The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article ‘%s’. Enabling this option after the article is created can cause replication to fail when the data in a FILESTREAM column exceeds 2GB and ther
22586 16 Column ‘%s’ cannot be added or modified in article ‘%s’ of publication ‘%s’. The DDL operatoin on hierarchyid and FILESTREAM columns is not supported for publications that have a ‘sync_mode’ of 1 (character mode) or with a lower than 90RTM backward compat
22801 16 Starting the Change Data Capture Collection Agent job. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic management view.
22802 16 Starting the Change Data Capture Cleanup Agent job using low watermark %s.
22803 16 Change Data Capture has scanned the log from LSN{%s} to LSN{%s}, %d transactions with %d commands have been extracted. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic management view.
22804 16 Change Data Capture cannot proceed with the job-related action because transactional replication is enabled on database %s but Distributor information cannot be retrieved to determine the state of the logreader agent. Make the Distributor database availab
22805 10 For more information, query the sys.dm_cdc_errors dynamic management view.
22806 16 The originator ID ‘%s’ is not valid. You must specify a non-zero ID that has never been used in the topology.
22807 16 The publication property ‘%s’ cannot be modified because the peer-to-peer publication ‘%s’ is not enabled for conflict detection. To enable the publication for conflict detection, use sp_configure_peerconflictdetection.
22808 16 Cannot execute procedure ‘%s’. Publication ‘%s’ must be enabled for peer-to-peer replication before you execute this procedure. To enable the publication for peer-to-peer replication, use sp_changepublication.
22809 10 The existing conflict table ‘%s’ was dropped.
22810 16 The @action parameter value is not valid. Valid values are ‘enable’ and ‘disable’.
22811 16 The roundtrip time-out must be greater than 0.
22812 10 The roundtrip ‘%s’ finished with timeout: %d seconds.
22813 10 The topology contains peer node versions that do not support conflict detection. To use conflict detection, ensure that all nodes in the topology are SQL Server 2008 or later versions.
22814 10 The topology contains a duplicate originator ID. To use conflict detection, the originator ID must be unique across the topology.
22815 10 A conflict of type ‘%s’ was detected at peer %d between peer %d (incoming), transaction id %s and peer %d (on disk), transaction id %s
22816 16 The qualified table name ‘%s’ is too long to be enabled for peer-to-peer conflict detection.
22817 10 %s has %s.
22818 10 A delete-delete conflict was detected and resolved. The row could not be deleted from the peer since the row does not exist. The incoming delete was skipped.
22819 10 A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and could not be resolved automatically. The incoming delete was skipped by peer %d. The conflict has to be resolved manually to guarantee data convergence between the
22820 10 A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming delete was applied to peer %d.
22821 10 An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was skipped by peer %d.
22822 10 An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was applied to peer %d.
22823 10 An update-delete conflict was detected and unresolved. The row could not be updated since the row does not exist. The incoming update was skipped. Check the priority of the destination peer and run data validation to ensure the delete conflict did not re
22824 10 An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was skipped by peer %d.
22825 10 An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was applied to peer %d.
22827 16 Peer-to-peer conflict detection alert
22828 16 The publication ‘%s’ was already %s for peer-to-peer conflict detection.
22829 16 The command %s failed. The values specified for the @ins_cmd, @del_cmd or @upd_cmd cannot be appended with schema name %s within the size limit %d.
22830 16 Could not update the metadata that indicates database %s is enabled for Change Data Capture. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit
22831 16 Could not update the metadata that indicates database %s is not enabled for Change Data Capture. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resu
22832 16 Could not update the metadata that indicates table %s is enabled for Change Data Capture. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit th
22833 16 Could not update the metadata that indicates table %s is not enabled for Change Data Capture. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmi
22834 16 Could not modify the the verbose logging status for table %s. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
22835 16 Could not update the metadata for database %s to indicate that a Change Data Capture job has been dropped. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failur
22836 16 Could not update the metadata for database %s to indicate that a Change Data Capture job has been added. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure
22837 16 Could not delete table entries or drop objects associated with capture instance ‘%s’. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the re
22838 16 All columns of a CDC unique index must be defined as NOT NULL. Index ‘%s’ selected as the CDC unique index for source table ‘%s.%s’ does not meet this requirement. Define all columns of the selected index as NOT NULL or select another unique index as the
22840 16 The application lock request ‘%s’ needed to modify Change Data Capture metadata was not granted. The value returned from the request was %d: -1 = timeout; -2 = canceled; -3 = deadlock victim; -999 validation or other call error. Examine the error cause an
22841 16 Could not upgrade the metadata for database ‘%s’ that is enabled for Change Data Capture. The failure occurred when executing the action ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the
22842 16 ALTER TABLE SWITCH statement failed because the partitioned destination table is enabled for Change Data Capture and does not have @allow_partition_switch set to 1.
22843 16 ALTER TABLE SWITCH statement failed because the partitioned source table is enabled for Change Data Capture and does not have @allow_partition_switch set to 1.
22844 16 The ‘%s’ option must be either 1 or 0.
22850 16 The threshold value specified for the Change Data Capture cleanup process must be greater than 0. When creating or modifying the cleanup job, specify a positive threshold value. If this error is encountered when executing the sys.sp_cdc_cleanup_change_tab
22851 16 Could not update cdc.change_tables to indicate a change in the low water mark for database %s.
22852 10 Could not delete change table entries made obsolete by a change in one or more low water marks for capture instances of database %s. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determi
22853 10 Could not delete obsolete entries in the cdc.lsn_time_mapping table for database %s. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the req
22854 16 Can not enable Change Data Capture on table ‘%s’ or add ColumnSet column to it because CDC does not support ColumnSet.
22855 10 Warning: The @allow_partition_switch parameter is set to 1. Change data capture will not track changes introduced in the table resulting from a partition switch which will cause data inconsistency when changes are consumed. Refer to books online for more
22856 10 Warning: The @allow_partition_switch parameter is set to 0. ALTER TABLE … SWITCH PARTITION statement will be disallowed on this partitioned table. Refer to books online for more information about partition switching behavior when using Change Data Captu
22857 10 Warning: The @allow_partition_switch parameter must be 1 for tables that are not partitioned. The explicit setting of the parameter to 0 was ignored. Refer to books online for more information about partition switching behavior when using Change Data Capt
22858 16 Unable to add entries to the Change Data Capture LSN time mapping table to reflect dml changes applied to the tracked tables. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22859 16 Log Scan process failed in processing log records. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22860 16 Log scan process failed in processing a ddl log record. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22861 10 Unable to upgrade database ‘%s’. Error ‘%d’ was raised: ‘%s’. Use the reported error to determine the cause of the failure and then execute sys.sp_cdc_vupgrade in the database context to rerun upgrade.
22862 16 The database snapshot ‘%s’ does not exist. Correct the parameter value and resubmit the request.
22863 16 Failed to insert rows into Change Data Capture change tables. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22864 16 The call to sp_MScdc_capture_job by the Capture Job for database ‘%s’ failed. Look at previous errors for the cause of the failure.
22901 16 The database ‘%s’ is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog vie
22902 16 Caller is not authorized to initiate the requested action. Sysadmin privileges are required.
22903 16 Another connection is already running ‘sp_replcmds’ for Change Data Capture in the current database.
22904 16 Caller is not authorized to initiate the requested action. DBO privileges are required.
22905 10 Database ‘%s’ is already enabled for Change Data Capture. Ensure that the correct database context is set, and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog vi
22906 16 The database ‘%s’ cannot be enabled for Change Data Capture because a database user named ‘cdc’ or a schema named ‘cdc’ already exists in the current database. These objects are required exclusively by Change Data Capture. Drop or rename the user or schem
22907 16 Parameter @role_name cannot be empty. Specify a value for @role_name and retry the operation. Supply null as the value if no role is to be used to gate access to captured change data.
22908 16 Could not create the Change Data Capture objects in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22909 16 Failed to cleanup the cdc.lsn_time_mapping table in database ‘%s’ when the last database table enabled for Change Data Capture was disabled. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22910 16 The cleanup request for database ‘%s’ failed. The database is not enabled for Change Data Capture.
22911 16 The capture job cannot be used by Change Data Capture to extract changes from the log when transactional replication is also enabled on the same database. When Change Data Capture and transactional replication are both enabled on a database, use the logre
22913 16 Could not drop the Change Data Capture objects in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22914 16 Only members of the sysadmin or db_owner or db_ddladmin roles can perform this operation when Change Data Capture is enabled for a database.
22916 16 Could not grant SELECT permission for the change enumeration functions for capture instance ‘%s’ and source table ‘%s.%s’ for the specified role. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22918 16 One or more columns in the list of included columns was not a captured column of the change table %s.
22919 16 One or more columns in the list of columns needing update flags was not a captured column of the change table %s.
22920 16 The named capture instance %s does not exist for database %s.
22921 16 Unable to generate scripts for all capture instances that the caller is authorized to access. To generate all such scripts, the parameters @column_list and @update_flag_list must both be null or empty.’
22923 16 Could not compute the new low endpoint for database ‘%s’ from retention %d. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22924 16 Could not clean up change tables for database ‘%s’. A failure occurred when attempting to clean up the database change tables based upon the current retention time. Refer to previous errors in the current session to identify the cause and correct any asso
22925 16 The number of columns captured by capture instance ‘%s’ exceeds the maximum allowed number: %d. Use the @captured_columns_list parameter to specify a subset of the columns less than or equal to the maximum allowed and resubmit the request.
22926 16 Could not create a capture instance because the capture instance name ‘%s’ already exists in the current database. Specify an explicit unique name for the parameter @capture_instance.
22927 16 Capture instance name ‘%s’ exceeds the length limit of 100 characters. Specify a name that satisfies the length constraint.
22928 16 Index name ‘%s’ is not an index for table ‘%s.%s’. Specify a valid index name for the table.
22929 16 Index ‘%s’ must be either a primary key or a unique index for table ‘%s.%s’. Specify an index that meets at least one of these requirements.
22930 16 Could not locate ‘%s’ as a column of source table ‘%s.%s’. Specify a valid column name.
22931 16 Source table ‘%s.%s’ does not exist in the current database. Ensure that the correct database context is set. Specify a valid schema and table name for the database.
22932 16 Capture instance name ‘%s’ is invalid. Specify a valid name. See the topic ‘Identifiers’ in SQL Server Books Online for object name rules.
22938 16 Role name ‘%s’ is invalid. Specify a valid name. See the topic ‘Identifiers’ in SQL Server Books Online for object name rules.
22939 16 The parameter @supports_net_changes is set to 1, but the source table does not have a primary key defined and no alternate unique index has been specified.
22940 16 Could not remove DDL history entries in the Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22941 16 Could not retrieve column information for index ‘%s’ of source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22942 16 Columns specified in the captured column list could not be mapped to columns in source table ‘%s.%s’. Verify that the columns specified in the parameter @captured_column_list are delimited properly and match columns in the source table.
22943 16 Columns used to uniquely identify a row for net change tracking must be included in the list of captured columns. Add either the primary key columns of the source table, or the columns defined for the index specified in the parameter @index_name to the li
22944 16 Could not create the specified database role ‘%s’ for gating access to change table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22945 16 Could not add column information to the cdc.index_columns system table for the specified index for source table ‘%s.%s. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22946 16 Could not add column information to the cdc.captured_columns system table for source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22947 16 Could not create the change table for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22948 16 Could not create the change enumeration functions for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22949 16 Could not update the Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22950 16 Could not remove index column entries in the Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22951 16 Could not remove captured column entries in the Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22952 16 Could not drop Change Data Capture objects created for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22953 16 Could not remove Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22954 16 Could not cleanup change tables for capture instance ‘%s’ using low end point %s. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22955 16 Could not obtain the maximum LSN for the database from function ‘sys.fn_cdc_get_max_lsn’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22956 16 Could not obtain the minimum LSN of the change table associated with capture instance ‘%s’ from function ‘sys.fn_cdc_get_min_lsn’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22957 16 LSN %s, specified as the new low end point for the change table associated with capture instance ‘%s’, is not within the Change Data Capture timeline [%s, %s].
22958 16 Could not create the function to query for all changes for capture instance ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22959 16 Could not create the function to query for net changes for capture instance ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22960 16 Change data capture instance ‘%s’ has not been enabled for the source table ‘%s.%s’. Use sys.sp_cdc_help_change_data_capture to verify the capture instance name and retry the operation.
22961 16 Could not create a nonclustered index to support net change tracking for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22962 16 Two capture instances already exist for source table ‘%s.%s’. A table can have at most two capture instances. If the current tracking options are not appropriate, disable change tracking for the obsolete instance by using sys.sp_cdc_disable_table and retr
22963 16 Parameter ‘%s’ cannot be null or empty. Specify a value for the named parameter and retry the operation.
22964 16 LSN %s, specified as the new low end point for change table cleanup must represent the start_lsn value of a current entry in the cdc.lsn_time_mapping table. Choose an LSN value that satisfies this requirement.
22965 16 A quoted column in the column list is not properly terminated. Verify that columns are correctly delimited and retry the operation. For more information, see ‘Delimited Identifiers’ in Books Online.
22966 16 Could not create table dbo.systranschemas in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22967 16 Could not create a clustered index for table dbo.systranschemas in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22968 16 Could not create DDL trigger ‘%s’ when enabling Change Data Capture for database ‘%s’. Additional messages in the SQL Server error log and system event log may provide more detail.
22970 16 The value for parameter @maxscans specified for the Change Data Capture job must be greater than 0.
22971 16 Could not allocate memory for the log reader history cache. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual settings on the server and examine memory usage to see if another application is excessively consum
22972 16 When calling stored procedure [sys].sp_cdc_help_change_data capture, if either @source_schema or @source_name is non-null and non-empty, the other parameter must also be non-null and non-empty.
22973 16 The specified filegroup ‘%s’ is not a valid filegroup for database ‘%s’. Specify a valid existing filegroup or create the named filegroup, and retry the operation.
22974 16 Tables contained in the cdc schema cannot be enabled for Change Data Capture.
22975 16 Source table ‘%s’ contains one of the following reserved column names: __$start_lsn, __$end_lsn, __$seqval, __$operation, and __$update_mask. To enable Change Data Capture for this table, specify a captured column list and ensure that these columns are ex
22976 16 Could not alter column ‘%s’ of change table ‘%s’ in response to a data type change in the corresponding column of the source table ‘%s’. The Change Data Capture meta data for source table ‘%s’ no longer accurately reflects the source table. Refer to previ
22977 16 Unable to update DDL history information to reflect columns changes applied to the tracked table associated with change table ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22978 16 Could not update the cdc.captured_columns entry for column ‘%s’ of change table ‘%s’ to reflect a data type change in the corresponding column of the source table ‘%s’. Change Data Capture column meta data for table ‘%s’ no longer accurately reflects the
22979 16 The unique index ‘%s’ on table ‘%s’ is used by Change Data Capture. The constraint using this index cannot be dropped or disabled.
22980 16 The unique index ‘%s’ on table ‘%s.%s’ is disabled and cannot be used as a unique index by Change Data Capture. Enable the index.
22981 16 Object does not exist or access is denied.
22982 16 Could not create internal stored procedures used to populate the change table for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22983 16 The unique index ‘%s’ on source table ‘%s’ is used by Change Data Capture. To alter or drop the index, you must first disable Change Data Capture on the table.
22984 16 An error occurred while waiting on the log reader history cache event. This error is reported by the internal task scheduling and might be transient. Retry the operation.
22985 16 Change data capture has not been enabled for source table ‘%s.%s’. Specify the name of a table enabled for Change Data Capture. To report on the tables enabled for Change Data Capture, query the is_tracked_by_cdc column in the sys.tables catalog view.
22986 16 Could not allocate memory for Change Data Capture population. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming
22987 16 Change Data Capture population failed writing blob data for one or more large object columns. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if
22988 16 This instance of SQL Server is the %s. Change data capture is only available in the Enterprise, Developer, and Enterprise Evaluation editions.
22989 16 Could not enable Change Data Capture for database ‘%s’. Change data capture is not supported on system databases, or on a distribution database.
22990 16 The value specified for the parameter @pollinginterval cannot exceed 24 hours or be less than 0. Specify a polling interval (in seconds) that is less than or equal to 24 hours (86,400 seconds).
22991 16 The value specified for the parameter @maxtrans must be greater than 0.
22992 16 The specified @job_type, %s, is not supported. The value specified for the parameter @job_type must be N’capture’ to indicate a capture job, or N’cleanup’ to indicate a cleanup job.
22993 16 The Change Data Capture job table containing job information for database ‘%s’ cannot be found in the msdb system database. Run the stored procedure ‘sys.sp_cdc_add_job’ to create the appropriate CDC capture or cleanup job. The stored procedure will creat
22994 16 The retention value specified for the Change Data Capture cleanup process must be greater than 0 and less than or equal to 52594800. When creating or modifying the cleanup job, specify a retention value (in minutes) that is within that range. If this erro
22995 16 A value for the parameter @retention cannot be specified when the job type is ‘capture’. Specify NULL for the parameter, or omit the parameter from the statement.
22996 16 When adding or modifying the CDC cleanup job, @pollinginterval, @maxtrans, @maxscans, and @continuous may not be assigned non-null values.
22997 16 The Change Data Capture ‘%s’ job does not exist in the system table ‘msdb.dbo.cdc_jobs’. Use the stored procedure ‘sys.sp_cdc_add_job’ to add the Change Data Capture job.
22998 16 The value specified for the parameter @continuous must be 0 or 1.
22999 16 The value specified for the parameter @pollinginterval must be null or 0 when the stored procedure ‘sys.sp_cdc_scan’ is not being run in continuous mode.
23003 17 The WinFS share permissions have become corrupted {Error: %ld}. Please try setting the share permissions again.
23100 16 Invalid input parameter(s).
23101 16 Access is denied.
23102 16 Item does not exist {ItemId: %ls}.
23103 16 Folder already exists {ItemId: %ls}.
23104 16 Folder does not exist {ItemId: %ls}.
23105 16 Operation violates hierarchical namespace uniqueness.
23106 16 Container is not empty {ItemId: %ls}.
23107 16 Item cannot be copied onto itself.
23108 16 Scoping path does not exist or is invalid.
23109 16 Container does not exist.
23110 16 No more items to enumerate.
23111 16 Item does not exist in the given scope {ItemId: %ls, Scope: %ls}.
23112 16 Transaction not in active state.
23113 16 Item either does not exist or it is not a file-backed one.
23114 16 Sharing violation.
23115 16 Transaction bindtoken must be null when called within the context of a transaction.
23116 16 Inconsistent StreamSize and/or AllocationSize data {ItemId: %ls}.
23117 16 File-backed item does not exist {ItemId: %ls}.
23200 16 ItemId of folder ‘%ls’ not found.
23201 16 Share ‘%ls’ does not exist in Catalog.
23202 16 Could not delete Share ‘%ls’ in Catalog.
23203 16 Store item not found in Catalog.
23204 16 Could not delete Store item in Catalog.
23205 16 Store database name not found in Catalog.
23206 16 Could not create share to the ItemPath ‘%ls’.
23207 16 Could not add Share item for ‘%ls’ in Catalog.
23208 16 ItemPath ‘%ls’ does not exist in Store.
23209 16 Could not update Store state in Catalog.
23210 16 Itempath ‘%ls’ is a file-backed item or within it’s sub-tree.
23211 16 Could not start Store Manager. Please look in WinFS UT Log for details.
23212 16 Itempath ‘%ls’ is a compound item.
23401 16 Operation failed with HRESULT 0x%x.
23402 16 Multiple store items were found for the given store name in the catalog.
23403 16 Cannot create a store with the specified name, it already exists.
23404 16 Cannot delete the system stores (Catalog or DefaultStore)
23405 16 Store not found.
23406 16 A share with the same name already exists.
23407 16 Could not find a share with the specified name.
23408 16 The specified itempath is invalid.
23409 16 Cannot delete system shares (Catalog or DefaultStore)
23410 16 System error occurred {ErrorCode: %d}.
23411 16 WinFS could not find the specified volume.
23412 16 WinFS Store manager is not ready for requests.
23413 16 WinFS Store Manager currently does not support non-system volumes.
23414 16 There was a timeout trying to get a lock on the volume object for this operation.
23415 16 The specified volume is not mounted or is not supported by WinFS
23416 16 Access Denied. Look in the WinFS UT log for more details.
23417 16 Invalid argument(S)
23418 16 Itempath is a compound item.
23419 16 Itempath is a file-backed item or within it’s sub tree.
23420 16 Itempath does not exist in Store.
23421 16 Not enough memory available in the system to process the request.
23422 16 The Disk or File Group is full.
23423 16 Error accessing files on disk. Refer to the WinFS UT log for more information.
23424 16 The database operation was rolled back due to a deadlock. Refer to WinFS UT log for details.
23425 16 Cannot call sp_winfs_deletestore on a connection to the store specified for delete.
23426 16 Could not initialize the WSM memory clerk during startup.
23427 16 Could not initialize the WSM memory object during startup.
23428 16 Could not initialize WSM tracing during startup.
23500 16 Item container does not exist.
23501 16 Owning Item does not exist.
23502 16 NamespaceName is empty or exceeds the maximum length.
23503 16 Invalid Source endpoint type
23504 16 Invalid Target endpoint type
23505 16 A File-backed item must be a compound item type.
23506 16 A File Backed Item may not contain other Items.
23509 16 Source Item does not exist.
23510 16 Item with name already exists in container.
23511 16 New container cannot be a sub-container of item.
23513 16 Item does not exist.
23515 16 Item can not be deleted if it has children
23519 16 Target Item does not exist.
23525 16 Invalid Namespace Name.
23530 16 Operation can not be called inside a un-committable transaction
23536 16 Win32 file handle is open for item
23573 16 Cannot change ContainerId when replacing item.
23579 16 This procedure is reserved and cannot be called.
23587 16 File stream cannot be null.
23588 16 Container ids must be the same.
23996 16 The request could not be performed because of an device I/O error.
23997 16 System error occurred {ErrorCode: %d}.
23998 16 Not enough memory available in the system to process the request.
23999 16 Unspecified error(s) occurred.
25002 16 The specified Publisher is not enabled as a remote Publisher at this Distributor. Ensure the value specified for the parameter @publisher is correct, and that the Publisher is enabled as a remote Publisher at the Distributor.
25003 16 Upgrade of the distribution database MSmerge_subscriptions table failed. Rerun the upgrade procedure in order to upgrade the distribution database.
25005 16 It is invalid to drop the default constraint on the rowguid column that is used by merge replication.
25006 16 The new column cannot be added to article ‘%s’ because it has more than %d replicated columns.
25007 16 Cannot synchronize the subscription because the schemas of the article at the Publisher and the Subscriber do not match. It is likely that pending schema changes have not yet been propagated to the Subscriber. Run the Merge Agent again to propagate the ch
25008 16 The merge replication views could not be regenerated after performing the data definition language (DDL) operation.
25009 16 Invalid value ‘%s’ specified while executing sp_changemergearticle on article ‘%s’ for the ‘identityrangemanagementoption’ property.
25010 16 The constraint is used by merge replication for identity management and cannot be dropped directly. Execute sp_changemergearticle @publication, @article, “identityrangemanagementoption”, “none” to disable merge identity management, which will also drop th
25012 16 Cannot add an identity column since the table is published for merge replication.
25013 16 Cannot perform alter table because the table is published in one or more publications with a publication_compatibility_level of lower than ’90RTM’. Use sp_repladdcolumn or sp_repldropcolumn.
25014 16 sp_repladdcolumn does not allow adding columns of datatypes that are new to this release.
25015 10 Schema Changes and Bulk Inserts
25016 10 Prepare Dynamic Snapshot
25017 16 Failed to execute the command “%s” through xp_cmdshell. Detailed error information is returned in a result set.
25018 16 Precomputed partitions cannot be used because articles “%s” and “%s” are part of a join filter and at least one of them has a constraint with a CASCADE action defined.
25019 16 The logical record relationship between articles “%s” and “%s” cannot be added because at least one of the articles has a constraint with a CASCADE action defined.
25020 16 The article cannot be created on table ‘%s’ because it has more than %d columns and column-level tracking is being used. Either reduce the number of columns in the table or change to row-level tracking.
25021 16 Replication stored procedure sp_MSupdategenhistory failed to update the generation ‘%s’. This generation will be retried in the next merge.
25022 16 The snapshot storage option (@snapshot_storage_option) must be ‘file system’, or ‘database’.
25023 16 Stored procedures containing table-value parameters cannot be published as ‘[serializable] proc exec’ articles.
25024 16 A snapshot storage option of ‘database’ is incompatible with the use of character mode bcp for snapshot generation.
25025 16 Cannot add a sparse column or a sparse column set because the table is published for merge replication. Merge replication does not support sparse columns.
25026 16 The proc sp_registercustomresolver cannot proceed because it is not run in the context of the distribution database, or the distribution database is not properly upgraded.
25601 17 The extended event engine is out of memory.
25602 17 The %S_MSG, “%.*ls”, encountered a configuration error during initialization. Object cannot be added to the event session.
25603 17 The %S_MSG, “%.*ls”, could not be added. The maximum number of singleton targets has been reached.
25604 17 The extended event engine is disabled.
25605 17 The %S_MSG, “%.*ls”, could not be added. The maximum number of packages has been reached.
25606 17 The extended event engine could not be initialized. Check the SQL Server error log and the Windows event logs for information about possible related problems.
25607 17 The extended event engine has been disabled by startup options. Features that depend on extended events may fail to start.
25608 17 The extended event engine could not allocate record for local thread/fiber.
25623 16 The %S_MSG name, “%.*ls”, is invalid, or the object could not be found
25624 16 The constraints of %S_MSG name, “%.*ls”, have been violated. The object does not support binding to actions or predicates. Event not added to event session.
25625 16 The %S_MSG, “%.*ls”, already exists in the event session. Object cannot be added to the event session.
25629 16 For %S_MSG, “%.*ls”, the customizable attribute, “%ls”, does not exist.
25630 16 The predicate expression bound to %S_MSG ,”%.*ls”, has mismatching types.
25631 16 The %S_MSG, “%.*ls”, already exists. Choose a unique name for the event session.
25632 16 The specified buffer size is less than the minimum size.
25633 16 The buffer size specified exceeds the maximum size.
25634 16 The dispatch latency specified is below the minimum size.
25635 16 An attempt was made to add an asynchronous target to a session with a maximum memory of 0. For asynchronous targets to be added to a session, the session must have a maximum memory greater than 0.
25636 16 Source and comparator types of the predicate do not match.
25638 16 Event data exceeded allowed maximum.
25639 16 The %S_MSG, “%.*ls”, exceeds the number of allowable bound actions.
25640 16 Maximum event size is smaller than configured event session memory. Specify a larger value for maximum event size, or specify 0.
25641 16 For %S_MSG, “%.*ls”, the parameter “%ls” passed is invalid. %ls
25642 16 Mandatory customizable attributes are missing for %S_MSG, “%.*ls”.
25643 16 The %S_MSG, “%.*ls”, can not be added to an event session that specifies no event loss.
25644 16 The %S_MSG, “%.*ls”, cannot be bound to the event session.
25646 16 The %S_MSG name, “%.*ls”, is invalid.
25647 16 The %S_MSG, “%.*ls”, could not be found. Ensure that the object exists and the name is spelled correctly.
25648 16 The %S_MSG, “%.*ls”, could not be found. Ensure that the package exists and the name is spelled correctly.
25649 16 Two of the actions/predicates for %S_MSG, “%.*ls”, can not coexist. Please remove one.
25650 16 For %S_MSG, “%.*ls” the customizable attribute, “%ls”, was specified multiple times.
25651 16 For %S_MSG, “%.*ls”, the value specified for customizable attribute, “%ls”, did not match the expected type, “%ls”.
25653 16 The %S_MSG, “%.*ls”, does not exist in the event session. Object cannot be dropped from the event session.
25699 17 The extended event engine failed unexpectedly while performing an operation.
25701 15 Invalid event session name “%.*ls”. Temporary event sessions are not allowed.
25702 16 The event session option, “%.*ls”, is set more than once. Remove the duplicate session option and re-issue the statement.
25703 16 The event session option, “%.*ls”, has an invalid value. Correct the value and re-issue the statement.
25704 16 The event session has already been stopped.
25705 16 The event session has already been started.
25706 16 The %S_MSG, “%.*ls”, could not be found.
25707 16 Event session option “%.*ls” cannot be changed while the session is running. Stop the event session before changing this session option.
25708 16 The “%.*ls” specified exceeds the maximum allowed value. Specify a smaller configuration value.
25709 16 One or more event sessions failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
25710 16 Event session “%.*ls” failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
25711 16 Failed to parse an event predicate.
25712 16 An invalid comparison operator was specified for an event predicate.
25713 16 The value specified for %S_MSG, “%.*ls”, %S_MSG, “%.*ls”, is invalid.
25715 16 The predicate on event “%ls” is invalid. Operator ‘%ls’ is not defined for type “%ls”, %S_MSG: “%.*ls”.
25716 16 The predicate on event, “%.*ls”, exceeds the maximum length of %d characters.
25717 16 The operating system returned error %ls while reading from the file ‘%s’.
25718 16 The log file name “%s” is invalid. Verify that the file exists and that the SQL Server service account has access to it.
25719 16 Initial file name and initial offset must be specified as a pair. Please correct the parameters and retry your query.
25720 10 ‘sys.fn_xe_file_target_read_file’ is skipping records from “%.*ls” at offset %I64d.
25721 16 The metadata file name “%s” is invalid. Verify that the file exists and that the SQL Server service account has access to it.
25722 16 The offset %d is invalid for log file “%s”. Specify an offset that exists in the log file and retry your query.
25723 16 An error occurred while obtaining metadata information from the file “%s”. The file may be damaged.
25724 16 Predicate too large for display
25807 16 The %d KB buffer size specified is too low for the ETW target. Increase the size and retry your command.
25809 16 The log file path “%ls” to the ETW target is invalid. Verify that the path exists and that the SQL Server startup account has access to the log file.
25810 16 The session name specified exceeds the maximum length of %d characters.
25811 16 The operating system returned error 5 (ACCESS_DENIED) while creating an ETW tracing session. Ensure that the SQL Server startup account is a member of the ‘Performance Log Users’ group and then retry your command.
25812 16 The field ‘%ls’ is invalid for the event ‘%ls’. Verify that the field exists and try your command again.
25813 16 The action “%ls” does not exist. Verify that the action exists and try your command again.
25814 16 The filtering event “%ls” does not exist. Verify that the event exists and try your command again.
25815 16 The source type, %d, is invalid. Valid types are 0 for event fields or 1 for actions.
25816 16 The slot count, %d, exceeds the maximum slot count size of %d. Reduce the slot count value and try your command again.
25817 16 The column or action name specified exceeds the maximum length of %d characters.
25818 16 The event “%ls” was not found.
25819 16 The column “%ls” was not found.
25820 16 The action “%ls” was not found.
25821 16 The number of begin and end columns must match. Specify the same number of columns for begin and end matching.
25822 16 The number of begin and end actions must match. Specify the same number of actions for begin and end matching.
25824 16 The begin and end columns at position %d are not of the same type. Specify matching columns that are the same type and try your command again.
25825 16 The begin and end action at postition %d are not of the same type. Specify matching actions that are the same type and try your command again.
25827 16 The operating system returned error %d while creating the file ‘%ls’. Verify that the path exists and that the SQL Server startup account has access to the location.
25833 16 Counter target could not add package “%ls” to the list of packages to count. Events from this package will not be counted.
25834 16 Ring Buffer target could not add package “%ls” to the package occurrence list. Events from this package will not be kept based on occurrence number.
25838 16 A value is required for the parameter ‘filtering_event_name’ when source type is 0.
26010 10 The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: %#x. Check certificates to make sure they are valid.
26011 16 The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system.
26012 16 The server has attempted to initialize SSL encryption when it has already been initialized. This indicates a problem with SQL Server. Contact Technical Support.
26013 10 The certificate [Cert Hash(sha1) “%hs”] was successfully loaded for encryption.
26014 16 Unable to load user-specified certificate [Cert Hash(sha1) “%hs”]. The server will not accept a connection. You should verify that the certificate is correctly installed. See “Configuring Certificate for Use by SSL” in Books Online.
26015 16 Unable to load user-specified certificate. Because connection encryption is required, the server will not be able to accept any connections. You should verify that the certificate is correctly installed. See “Configuring Certificate for Use by SSL” in Boo
26017 10 Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
26018 10 A self-generated certificate was successfully loaded for encryption.
26022 10 Server is listening on [ %hs <%hs> %d].
26023 16 Server TCP provider failed to listen on [ %hs <%hs> %d]. Tcp port is already in use.
26024 16 Server failed to listen on %hs <%hs> %d. Error: %#x. To proceed, notify your system administrator.
26025 10 HTTP authentication succeeded for user ‘%.*ls’.%.*ls
26026 14 HTTP authentication failed.%.*ls
26027 10 Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.
26028 10 Server named pipe provider is ready to accept connection on [ %hs ].
26029 16 Server named pipe provider failed to listen on [ %hs ]. Error: %#x
26030 10 Server shared memory provider is ready for clients to connect to [ %hs ].
26031 16 Server shared memory provider failed to initialize. Error: %#x
26032 10 Server VIA provider is ready for clients to connect to [ %hs:%d ].
26033 16 Server VIA provider failed to initialize. Error: %#x
26034 10 The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will proceed with immediate termination.
26035 16 The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. Winsock error code: %#x.
26036 10 Server named pipe connections are restricted to local access only. This is an informational message only. No user action is required.
26037 10 The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: %#x, state: %d. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This i
26038 10 The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: %#x, state: %d. Administrator should deregister this SPN manually to avoid client authentication errors.
26039 16 The SQL Server Network Interface library was unable to load SPN related library. Error: %#x.
26040 17 Server TCP provider has stopped listening on port [ %d ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
26041 10 Server TCP provider has successfully reestablished listening on port [ %d ].
26042 17 Server HTTP provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
26043 10 Server HTTP provider has successfully reestablished listening.
26044 17 Server named pipe provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
26045 10 Server named pipe provider has successfully reestablished listening on [ %hs ].
26046 17 Server shared memory provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
26047 10 Server shared memory provider has successfully reestablished listening.
26048 10 Server local connection provider is ready to accept connection on [ %hs ].
26049 16 Server local connection provider failed to listen on [ %hs ]. Error: %#x
26050 17 Server local connection provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to re-establish listening.
26051 10 Server local connection provider has successfully re-established listening on [ %hs ].
26052 10 SQL Server Network Interfaces initialized listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. This is an informational message only. No user action is required.
26053 16 SQL Server Network Interfaces failed to initialize listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. There may be insufficient memory. Free up additional memory, then turn the node off and on again. If th
26054 16 Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQ
26055 16 The SQL Server failed to initialize VIA support library [%hs]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: %#x.
26056 10 Failed to update the dedicated administrator connection (DAC) port number in the registry. Clients may not be able to discover the correct DAC port through the SQL Server Browser Service. Error: %#x.
26057 16 Failed to determine the fully qualified domain name of the computer while initializing SSL support. This might indicate a problem with the network configuration of the computer. Error: %#x.
26058 16 A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections.
26059 10 The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
26060 10 The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
26061 10 Failed to determine the fully qualified domain name of the computer while composing the Service Principal Name (SPN). This might indicate a problem with the network configuration of the computer. Error: %#x.
26062 16 Invalid parameter detected while initializing TCP listening port. Error: %#x, state: %d. Contact Technical Support.
26063 10 Warning: Support for the VIA protocol is deprecated and will be removed in a future version of Microsoft SQL Server. If possible, use a different network protocol and disable VIA.
26065 16 Extended Protection for the SQL Server Database Engine is enabled, but the operating system does not support Extended Protection. Connection attempts using Windows Authentication might fail. Check for an operating system service pack to allow for Extended
26066 16 An error occurred while configuring cluster virtual IP addresses for Extended Protection. Connection attempts using Windows Authentication might fail. Error: %d.
26073 16 TCP connection closed but a child process of SQL Server may be holding a duplicate of the connection’s socket. Consider enabling the TcpAbortiveClose SQL Server registry setting and restarting SQL Server. If the problem persists, contact Technical Suppor
27001 16 Reserved error message. Should never be issued.
27002 16 A null or invalid SqlCommand object was supplied to Fuzzy Lookup Table Maintenance by SQLCLR. Reset the connection.
27003 16 Bad token encountered during tokenization.
27004 16 Unexpected token type encountered during tokenization.
27005 16 Error Tolerant Index is corrupt.
27006 16 Deleted more than one rid from ridlist during delete operation. Error Tolerant Index is corrupt.
27007 16 Attempt to delete from empty ridlist. Error Tolerant Index is corrupt.
27008 16 rid to be deleted not found in rid-list. Error Tolerant Index is corrupt.
27009 16 Error Tolerant Index frequencies must be non-negative. Error Tolerant Index is corrupt.
27010 16 Attempt to insert row whose ID is already present. Error Tolerant Index is corrupt.
27011 16 No ridlist provided for appending. Error Tolerant Index is corrupt.
27012 16 Cannot delete token. Error Tolerant Index is corrupt.
27013 16 Tokenizer object has no delimiter set. Error Tolerant Index is corrupt.
27014 16 Deletion failed because token does not occur in index. Error Tolerant Index is corrupt.
27015 16 Unexpected ridlist length. Error Tolerant Index is corrupt.
27016 16 Cannot connect to Error Tolerant Index. Bad or missing SqlCommand object.
27017 16 Failed to drop index on reference table copy.
27018 16 Could not retrieve metadata from Error Tolerant Index. The index is probably corrupt.
27019 16 Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt.
27022 16 An error specific to fuzzy lookup table maintenance has occurred.
27023 16 A system error occurred during execution of fuzzy lookup table maintenance.
27024 16 Cannot write at negative index position. Could not update Error Tolerant Index. The index is probably corrupt.
27025 16 Argument is not a valid hex string. Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt.
27026 16 Negative count in Error Tolerant Index metadata. The index is probably corrupt.
27027 16 Error tolerant index metadata contains unsupported normalization flags. The index is probably corrupt.
27028 16 Invalid Error Tolerant Index metadata. The index is probably corrupt.
27029 16 Invalid Error Tolerant Index metadata version.
27030 16 Missing metadata. The Error Tolerant Index is probably corrupt.
27031 16 Unable to parse token counts in Error Tolerant Index metadata. The index is probably corrupt.
27032 16 Error Tolerant Index Metadata string too long. Index is probably corrupt.
27033 16 Error Tolerant Index Metadata length limit exceeded.
27034 16 Unexpected end of Error Tolerant Index metadata. Index is probably corrupt.
27037 16 No table name provided for Error Tolerant Index. The index is probably corrupt.
27038 16 No input provided for decoding in Error Tolerant Index metadata. Index is probably corrupt.
27039 16 No input provided for encoding in Error Tolerant Index metadata. Index is probably corrupt.
27040 16 No Error Tolerant Index metadata string provided for initialization. Index is probably corrupt.
27041 16 No Error Tolerant Index metadata provided for serialization. The index is probably corrupt.
27042 16 Could not lookup object_id. No object name provided.
27043 16 Could not lookup object_id. Null command object provided.
27044 16 Open connection required. Cannot query Error Tolerant Index.
27045 16 Cannot write to null output buffer. Could not update Error Tolerant Index. The index is probably corrupt.
27046 16 Output buffer provided is too small. Could not update Error Tolerant Index. The index is probably corrupt.
27047 16 The number of min-hash q-grams per token must be positive.
27048 16 Could not create index on reference table copy.
27049 16 Reference table (or internal copy) missing integer identity column. Error tolerant index is probably corrupt.
27050 16 The maximum allow integer identity value has been reached. Consider re-building the error tolerant index to use any gaps in sequence.
27051 16 Could not read rid from data provided (missing column name, null reader object, or corrupted data). The index is probably corrupted.
27052 16 Table maintenance insertion failed.
27053 16 A positive q-gram length is required for tokenization.
27054 16 Maintenance trigger already installed on this reference table.
27055 16 Missing extended property on maintenance trigger.
27056 16 Maintenance trigger name out of sync with Error Tolerant Index metadata. Index is probably corrupt.
27058 16 A SQL error occurred during execution of fuzzy lookup table maintenance.
27059 16 Could not lookup object_id. The reference table or maintenance trigger could not be found.
27060 16 The Error Tolerant Index table name provided is not a valid SQL identifier.
27061 16 The Error Tolerant Index table name provided refers to a missing table. Check sys.tables.
27062 16 An auxiliary Fuzzy Lookup table maintenance table is missing.
27063 16 An auxiliary Fuzzy Lookup table maintenance table name is null. Maintenance cannot proceed.
27064 16 The row deleted from the reference table could not be located in the reference table copy.
27065 16 Fuzzy Lookup Table Maintenance is not installed or the Error Tolerant Index is corrupt.
28000 16 The decrypted session key has an unexpected size.
28001 16 A corrupted message has been received. It contains invalid flags. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
28002 16 Cannot start service broker manager. Operating system error: %ls.
28003 16 An internal service broker error occurred. Operating system error: %ls.
28004 16 This message could not be delivered because the ‘%S_MSG’ action cannot be performed in the ‘%.*ls’ state.
28005 16 An exception occurred while enqueueing a message in the target queue. Error: %d, State: %d. %.*ls
28006 14 User does not have permission to %S_MSG the conversation ‘%.*ls’ in state ‘%.*ls’. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission.
28007 16 A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
28008 16 The conversation handle ‘{%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}’ is invalid.
28009 16 The crypto API has detected bad data while trying to perform a decryption operation.
28010 16 This message could not be delivered because it contains an invalid acknowledged message number. Highest expected message number: %I64d. Acknowledged message number: %I64d, fragment number: %d.
28011 16 This message could not be delivered because its %S_MSG has expired or is invalid.
28012 16 The Service Broker in the target database is unavailable: ‘%S_MSG’.
28013 16 The service broker is administratively disabled.
28014 16 The database is in read-only mode.
28015 16 The database is in single-user mode.
28016 16 The message has been dropped because the service broker in the target database is unavailable: ‘%S_MSG’.
28017 16 The message has been dropped because the target service broker is unreachable.
28018 16 The database is a replica of a mirrored database.
28019 16 System error %d occurred while creating a new message element GUID for this forwarded message.
28020 16 Could not create user token for user %d in database %d.
28021 16 One or more messages could not be delivered to the local service targeted by this dialog.
28022 10 An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate is not yet valid.
28023 10 An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate has expired.
28024 16 The security certificate bound to database principal (Id: %i) is not yet valid. Either wait for the certificate to become valid or install a certificate that is currently valid.
28025 16 The security certificate bound to database principal (Id: %i) has expired. Create or install a new certificate for the database principal.
28026 10 Connection handshake failed. Not enough memory available. State %d.
28027 10 Connection handshake failed. There is no compatible %S_MSG. State %d.
28028 10 Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State %d.
28029 10 Connection handshake failed. Unexpected event (%d) for current context (%d). State %d.
28030 10 Connection handshake failed. A call to the SQL Server Network Interface failed: (%x) %ls. State %d.
28031 10 Connection handshake failed. An OS call failed: (%x) %ls. State %d.
28032 10 A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration and it will be closed. All traffic will be redirected to the previously existing connection. This is an informational messag
28033 10 A new connection was established with the same peer. This connection lost the arbitration and it will be closed. All traffic will be redirected to the newly opened connection. This is an informational message only. No user action is required. State %d.
28034 10 Connection handshake failed. The login ‘%.*ls’ does not have CONNECT permission on the endpoint. State %d.
28035 10 Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d.
28036 10 Connection handshake failed. The certificate used by this endpoint was not found: %S_MSG. Use DBCC CHECKDB in master database to verify the metadata integrity of the endpoints. State %d.
28037 10 Connection handshake failed. Error %d occurred while initializing the private key corresponding to the certificate. The SQL Server errorlog and the Windows event log may contain entries related to this error. State %d.
28038 10 Connection handshake failed. The handshake verification failed. State %d.
28039 10 Connection handshake failed. The receive SSPI packet is not of type of the negotiated package. State %d.
28040 10 A corrupted message has been received. The adjacent error message header is invalid.
28041 16 A corrupted message has been received. The encrypted payload offset is invalid (%d).
28042 16 A corrupted message has been received. The arbitration request header is invalid.
28043 16 A corrupted message has been received. The arbitration response header is invalid.
28044 16 A corrupted message has been received. It is not encrypted and signed using the currently configured endpoint algorithm. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
28045 10 Connection handshake failed. The certificate used by the peer does not match the one in MASTER database with same issuer name and serial number. State %d.
28046 10 %S_MSG Login succeeded for user ‘%.*ls’. Authentication mode: %.*ls. %.*ls
28047 10 %S_MSG login attempt failed with error: ‘%.*ls’. %.*ls
28048 10 %S_MSG login attempt by user ‘%.*ls’ failed with error: ‘%.*ls’. %.*ls
28050 10 The session keys for this conversation could not be created or accessed. The database master key is required for this operation.
28051 10 Could not save a dialog session key. A master key is required in the database to save the session key.
28052 16 Cannot decrypt session key while regenerating master key with FORCE option.
28053 16 Service Broker could not upgrade conversation session keys in database ‘%.*ls’ to encrypted format (Error: %d). The Service Broker in this database was disabled. A master key is required to the database in order to enable the broker.
28054 16 Service Broker needs to access the master key in the database ‘%.*ls’. Error code:%d. The master key has to exist and the service master key encryption is required.
28055 16 The certificate ‘%.*ls’ is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certificate expiration date.
28056 16 This message could not be delivered because the user with ID %i in database ID %i does not have control permission on the service. Service name: ‘%.*ls’.
28057 10 Service Broker in database ‘%.*ls’ has a pending conversation upgrade operation. A database master key in the database is required for this operation to complete.
28058 16 Service Broker could not upgrade this conversation during a database upgrade operation.
28059 16 Connection handshake failed. The received premaster secret of size %d does not have the expected size of %d. State %d.
28060 16 The AES encryption algorithm is only supported on Windows XP, Windows Server 2003 or later versions.
28061 16 A corrupted message has been received. The adjacent message integrity check signature could not be validated.
28062 16 A corrupted message has been received. The signed dialog message header is invalid.
28063 16 A corrupted message has been received. A required variable data field is not present: %S_MSG. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
28064 16 A corrupted message has been received. A string variable data field is not a valid UNICODE string: %S_MSG. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
28065 16 A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
28066 16 A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
28067 16 A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
28068 16 A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
28069 16 Unexpected session key when encrypting a dialog message.
28070 10 Connection handshake failed. The received SSPI message Confirm status is unexpected. State %d.
28072 16 A serious error occurred in the Service Broker message transmitter (operation %i): Error: %i, State: %i. Message transmission will resume in %i seconds.
28073 16 An out of memory condition has occurred in the Service Broker message transmitter (operation %i). Message transmission will resume in %i seconds.
28074 16 Service Broker could not upgrade conversation with conversation_handle ‘%ls’. Use END CONVERSATION … WITH CLEANUP to delete this conversation, then try again to enable the broker. Use ALTER DATABASE … SET ERROR_BROKER to error all conversations in thi
28075 10 The broker in the sender’s database is in single user mode. Messages cannot be delivered while in single user mode.
28076 10 Could not query the FIPS compliance mode flag from registry. Error %ls.
28077 10 %S_MSG transport is running in FIPS compliance mode. This is an informational message only. No user action is required.
28078 10 The RC4 encryption algorithm is not supported when running in FIPS compliance mode.
28079 10 Connection handshake failed. The received SSPI packet is not of the expected direction. State %d.
28080 10 Connection handshake failed. The %S_MSG endpoint is not configured. State %d.
28081 10 Connection handshake failed. An unexpected status %d was returned when trying to send a handshake message. State %d.
28082 10 Connection handshake failed. An unexpected internal failure occurred when trying to marshal a message. State %d.
28083 16 The database principal ‘%.*ls’ cannot be used in a remote service binding because it cannot own certificates. Remote service bindings cannot be associated with 1) roles, 2) groups or 3) principals mapped to certificates or asymmetric keys.
28084 10 An error occurred in Service Broker internal activation while trying to scan the user queue ‘%ls’ for its status. Error: %i, State: %i. %.*ls This is an informational message only. No user action is required.
28085 16 The activated task was ended because the associated queue was dropped.
28086 16 The activated task was ended because either the queue or activation was disabled.
28087 16 The activated task was aborted because the invoked stored procedure ‘%ls’ did not execute RECEIVE.
28088 16 The activated task was aborted due to an error (Error: %i, State %i). Check ERRORLOG or the previous “Broker:Activation” trace event for possible output from the activation stored procedure.
28089 16 The database principal ‘%.*ls’ cannot be used in a remote service binding because it cannot own certificates. This is a special user for backward compatibility with implicitly connected user schemas.
28090 16 An error occurred while deleting sent messages from the transmission queue, Error: %i, State: %i. Verify that no other operation is locking the transmission queue, and that the database is available.
28098 10 A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State
28099 10 During the database upgrade process on database ‘%.*ls’, a user object ‘%S_MSG’ named ‘%.*ls’ was found to already exist. That object is now reserved by the system in this version of SQL Server. Because it already exists in the database, the upgrade proce
28101 16 User ‘%.*ls\%.*ls’ does not have permission to debug the requested client connection.
28102 16 Batch execution is terminated because of debugger request.
28201 10 SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE cannot be found.
29001 16 To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO).
29003 16 Invalid parameter combinations.
29004 16 Unknown property specified: %s.
30003 16 A fulltext system view or stvf cannot open database id %d.
30004 16 A fulltext system view or stvf cannot open user table object id %d.
30005 16 The name specified for full-text index fragment %.*ls is not valid.
30006 16 A fulltext system view or stvf cannot open fulltext index for user table object id %d.
30007 16 Parameters of dm_fts_index_keywords and dm_fts_index_keywords_by_document cannot be null.
30008 16 The level number specified for function fn_fulltext_compindex is not valid. Valid level numbers start from 0 and must be less than the number of levels of the compressed index. Use the correct level number.
30009 16 The argument data type ‘%ls’ specified for the full-text query is not valid. Allowed data types are char, varchar, nchar, nvarchar.
30020 16 The full-text query parameter for %S_MSG is not valid.
30022 10 Warning: 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
30023 16 The 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.
30024 16 The fulltext stoplist ‘%.*ls’ already exists in the current database. Duplicate stoplist names are not allowed. Rerun the statement and specify a unique stoplist name.
30028 17 Failed to get pipeline interface for ‘%ls’, resulting in error: 0x%X. There is a problem communicating with the host controller or filter daemon host.
30029 17 The full-text host controller failed to start. Error: 0x%X.
30031 17 A full-text master merge failed on full-text catalog ‘%ls’ in database ‘%.*ls’ with error 0x%08X.
30032 16 The 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.
30033 16 The 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.
30034 16 Full-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
30037 16 An argument passed to a fulltext function is not valid.
30038 17 Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
30039 17 Data 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.
30043 16 Stopwords of zero length cannot be added to a full-text stoplist. Specify a unique stopword that contains at least one character.
30044 16 The 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.
30045 17 Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
30046 16 SQL 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 th
30047 16 The user does not have permission to %.*ls stoplist ‘%.*ls’.
30048 10 Informational: Ignoring duplicate thesaurus rule ‘%ls’ while loading thesaurus file for LCID %d. A duplicate thesaurus phrase was encountered in either the section of an expansion rule or the section of a replacement rule. This causes an ambig
30049 17 Fulltext thesaurus internal error (HRESULT = ‘0x%08x’)
30050 16 Both the thesaurus file for lcid ‘%d’ and the global thesaurus could not be loaded.
30051 16 Phrases longer than 512 unicode characters are not allowed in a thesaurus file. Phrase: ‘%ls’.
30052 16 The 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 repeate
30053 16 Word breaking timed out for the full-text query string. This can happen if the wordbreaker took a long time to process the full-text query string, or if a large number of queries are running on the server. Try running the query again under a lighter load.
30055 10 Full-text catalog import has started for full-text catalog ‘%ls’ in database ‘%ls’.
30056 10 Full-text catalog import has finished for full-text catalog ‘%ls’ in database ‘%ls’. %d fragments and %d keywords were processed.
30057 10 Upgrade option ‘%ls’ is being used for full-text catalog ‘%ls’ in database ‘%ls’.
30059 16 A 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 craw
30060 16 The 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
30061 17 The 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
30062 17 The SQL Server failed to load FDHost service group sid. This might be because installation is corrupted.
30063 10 Warning: SQL Server could not set fdhost.exe processor affinity to %d because the value is not valid.
30064 17 SQL 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.
30067 10 Warning: 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
30068 10 During 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’.
30069 11 The 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
30070 10 During 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.
30071 11 The 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
30072 10 During 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’.
30073 11 The 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 sl
30074 17 The master merge of full-text catalog ‘%ls’ in database ‘%.*ls’ was cancelled.
30075 10 Full-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.
30076 10 Full-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.
30077 16 The 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
30078 10 The 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.
30079 10 The full text query ignored UNKNOWN in the OPTIMIZE FOR hint.
30080 16 The 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.
30081 10 A cached plan was compiled using trace flags that are incompatible with the current values. Consider recompiling the query with the new trace flag settings.
30082 16 Full-text predicates cannot appear in an aggregate expression. Place the aggregate expression in a subquery.
30083 16 Full-text predicates cannot appear in the GROUP BY clause. Place a GROUP BY clause expression in a subquery.
30084 16 The full-text index cannot be created because filegroup ‘%.*ls’ does not exist or the filegroup name is incorrectly specified. Specify a valid filegroup name.
30085 16 A 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.
30086 16 The 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.
30087 17 Data 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.
30088 10 The full-text filter daemon host process has stopped normally. The process will be automatically restarted if necessary.
30089 17 The 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 indexi
30090 10 A new instance of the full-text filter daemon host process has been successfully started.
30091 10 A 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
30092 16 Full-text stoplist ID ‘%d’ does not exist.
30093 17 The 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 re
30094 17 The 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.
30095 10 The 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
30096 10 A 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’.
30097 10 The 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
30098 10 An 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 rem
30099 17 Fulltext internal error
31001 16 The session ‘%s’ already exists. Use a different session name.
31002 16 This operation can be performed only by the owner of the session.
31003 16 User does not have enough permissions to tune one or more of the databases specified.
32001 10 Log shipping backup log job for %s.
32002 10 Log shipping copy job for %s:%s.
32003 10 Log shipping restore log job for %s:%s.
32004 10 Log shipping backup log job step.
32005 10 Log shipping copy job step.
32006 10 Log shipping restore log job step.
32007 16 Database %s is not ONLINE.
32008 10 Database %s is not ONLINE. The backup job will not be performed until this database is brought online.
32009 16 A log shipping primary entry already exists for database %s.
32010 16 Database %s does not exist as log shipping primary.
32011 16 Primary Database %s has active log shipping secondary database(s). Drop the secondary database(s) first.
32012 16 Secondary %s.%s already exists for primary %s.
32013 16 A log shipping entry already exists for secondary database %s.
32014 16 Database %s does not exist as log shipping secondary.
32015 16 The primary database %s cannot have SIMPLE recovery for log shipping to work properly.
32016 16 The specified agent_id %s or agent_type %d do not form a valid pair for log shipping monitoring processing.
32017 16 Log shipping is supported on Enterprise, Developer, Standard and Workgroup editions of SQL Server. This instance has %s and is not supported.
32018 16 Log shipping is not installed on this instance.
32019 10 Log shipping alert job.
32020 10 Log shipping alert job step.
32021 10 Log shipping alert job schedule.
32022 16 Cannot 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.
32023 16 An entry for primary server %s, primary database %s does not exist on this secondary. Register the primary first.
32024 16 An entry for primary server %s, primary database %s already exists.
32025 16 Primary Server %s, Database %s has active log shipping secondary database(s) on the secondary. Drop the secondary database(s) first.
32026 10 Log shipping Primary Server Alert.
32027 10 Log shipping Secondary Server Alert.
32028 16 Invalid value = %d for parameter @threshold_alert was specified.
32029 10 Log 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.
32030 10 Could not query monitor information for log shipping primary %s.%s from monitor server %s.
32031 10 Could not query monitor information for log shipping secondary %s.%s from monitor server %s.
32032 16 Invalid value ‘%d’ for update period. Update period should be between 1 and 120 minutes.
32033 16 The update job for the database mirroring monitor already exists. To change the update period, use sys.sp_dbmmonitorchangemonitoring
32034 16 An internal error occurred when setting up the database mirroring monitoring job.
32035 16 An internal error occurred when modifying the database mirroring monitoring job.
32036 16 Parameter(s) out of range.
32037 16 The units for the update period for the database mirroring monitor job have been changed.
32038 16 An internal error has occurred in the database mirroring monitor.
32039 16 The database ‘%s’ is not being mirrored. No update of the base table was done.
32040 16 The alert for ‘oldest unsent transaction’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
32041 16 The database mirroring monitor base tables have not been created. Please run sys.sp_dbmmonitorupdate to create them.
32042 16 The alert for ‘unsent log’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
32043 16 The alert for ‘unrestored log’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
32044 16 The alert for ‘mirror commit overhead’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
32045 16 ‘%s’ must be executed in msdb.
32046 16 Only members of the sysadmin fixed server role or the ‘dbm_monitor’ role in msdb can perform this operation.
32047 15 Database Mirroring Monitor Job
32048 15 Database Mirroring Monitor Schedule
32049 16 The database mirroring monitoring job does not exist. Run sp_dbmmonitoraddmonitoring to setup the job.
32050 16 Alerts cannot be created on the system databases, master, msdb, model or tempdb.
32051 10 System administrator privilege is required to update the base table. The base table was not updated.
32052 16 Parameter ‘%s’ cannot be null or empty. Specify a value for the named parameter and retry the operation.
32053 16 The server name, given by ‘@@servername’, is currently null.
32054 16 There was an error establishing a link to the remote monitor server.
32055 16 There was an error configuring the remote monitor server.
33001 16 Cannot drop the option because the option is not specified on %S_MSG.
33002 16 Access to %ls %ls is blocked because the signature is not valid.
33003 16 DDL statement is not allowed.
33004 16 The password of login ‘%.*ls’ is invalid. A new password should be set for this login without specifying the old password.
33005 16 Cannot find the certificate or asymmetric key from the file %.*ls. ErrorCode: 0x%x.
33006 16 WITH SIGNATURE option cannot be specified on database.
33007 16 Cannot encrypt symmetric key with itself.
33008 16 Cannot grant, deny, or revoke %.*ls permission on INFORMATION_SCHEMA or SYS %S_MSG.
33009 16 The 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.
33010 16 The MUST_CHANGE option cannot be specified together with the HASHED option.
33011 16 The %S_MSG private key cannot be dropped because one or more entities are encrypted by it.
33012 10 Cannot %S_MSG signature %S_MSG %S_MSG ‘%.*ls’. Signature already exists or cannot be added.
33013 16 A %S_MSG by %S_MSG ‘%.*s’ does not exist.
33014 16 Cannot countersign ‘%.*s’. Only modules can be countersigned.
33015 16 The database principal is referenced by a %S_MSG in the database, and cannot be dropped.
33016 16 The user cannot be remapped to a login. Remapping can only be done for users that were mapped to Windows or SQL logins.
33017 16 Cannot 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.
33018 16 Cannot remap user to login ‘%.*s’, because the login is already mapped to a user in the database.
33019 16 Cannot create implicit user for the special login ‘%.*s’.
33020 16 A HASHED password cannot be set for a login that has CHECK_POLICY turned on.
33021 16 Failed 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
33022 16 Cannot obtain cryptographic provider properties. Provider error code: %d.
33023 16 The %S_MSG is too long. Maximum allowed length is %d bytes.
33024 16 Cryptographic provider %S_MSG ‘%ls’ in dll is different from the guid recorded in system catalog for provider with id %d.
33025 16 Invalid cryptograpihic provider property: %S_MSG.
33026 16 Cryptographic provider with guid ‘%ls’ already exists.
33027 16 Cannot load library ‘%.*ls’. See errorlog for more information.
33028 16 Cannot open session for %S_MSG ‘%.*ls’. Provider error code: %d. (%S_MSG)
33029 16 Cannot initialize cryptographic provider. Provider error code: %d. (%S_MSG)
33030 16 Cryptographic provider is not available.
33031 16 Cryptographic provider ‘%.*ls’ is in disabled.
33032 16 SQL Crypto API version ‘%02d.%02d’ implemented by provider is not supported. Supported version is ‘%02d.%02d’.
33033 16 Specified key type or option ‘%S_MSG’ is not supported by the provider.
33034 16 Cannot specify algorithm for existing key.
33035 16 Cannot create key ‘%.*ls’ in the provider. Provider error code: %d. (%S_MSG)
33036 10 Cannot drop the key with thumbprint ‘%.*ls’ in the provider.
33037 16 Cannot export %S_MSG from the provider. Provider error code: %d. (%S_MSG)
33038 16 Operation is not supported by cryptographic provider key.
33039 16 Invalid algorithm ‘%.*ls’. Provider error code: %d. (%S_MSG)
33040 16 Cryptographic provider key cannot be encrypted by password or other key.
33041 16 Cannot create login token for existing authenticators. If dbo is a windows user make sure that its windows account information is accessible to SQL Server.
33042 16 Cannot add %S_MSG because it is already mapped to a login.
33043 16 Cannot add %S_MSG ‘%.*ls’ because there is already %S_MSG specified for the login.
33044 16 Cannot drop %S_MSG because there is %S_MSG referencing this provider.
33045 16 Cannot drop %S_MSG because it is not mapped to this login.
33046 16 Server principal ‘%.*ls’ has no credential associated with %S_MSG ‘%.*ls’.
33047 16 Fail to obtain or decrypt secret for %S_MSG ‘%.*ls’.
33048 16 Cannot use %S_MSG under non-primary security context.
33049 16 Key with %S_MSG ‘%.*ls’ does not exist in the provider or access is denied. Provider error code: %d. (%S_MSG)
33050 16 Cannot create key ‘%.*ls’ in the provider. Provider does not allow specifying key names.
33051 16 Invalid algorithm id: %d. Provider error code: %d. (%S_MSG)
33052 16 Cryptographic provider key cannot be a temporary key.
33053 16 Extensible Key Management is disabled or not supported on this edition of SQL Server. Use sp_configure ‘EKM provider enabled’ to enable it.
33054 16 Extensible key management is not supported in this edition of SQL Server.
33055 16 Exception happened when calling cryptographic provider ‘%.*ls’ in the API ‘%.*ls’. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx.
33056 16 Cannnot impersonate login ‘%.*ls’ to access %S_MSG ‘%.*ls’.
33057 10 Cryptographic 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.
33058 10 Cryptographic 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.
33070 16 The 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.
33071 16 This command requires %S_MSG to be disabled. Disable the %S_MSG and rerun this command.
33072 16 The audit log file path is invalid.
33073 16 Cannot find %S_MSG ‘%.*ls’ or you do not have the required permissions.
33074 16 Cannot %S_MSG a %S_MSG %S_MSG from a user database. This operation must be performed in the master database.
33075 16 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.
33076 16 The specified maximum size limit is greater than the maximum value allowed. The maximum size limit must be less than 16777215 TB.
33077 16 RESERVE_DISK_SPACE cannot be specified when setting MAXSIZE = UNLIMITED. Either reduce MAXSIZE or do not specify RESERVE_DISK_SPACE.
33079 16 Cannot 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.
33080 10 Cryptographic provider library ‘%.*ls’ loaded into memory. This is an informational message only. No user action is required.
33081 10 Failed to load cryptographic provider ‘%.*ls’ due to an invalid Authenticode signature or invalid file path. Check previous messages for other failures.
33082 16 Cannot find Cryptographic provider library with guid ‘%ls’.
33083 16 Cannot create %S_MSG for %S_MSG ‘%ls’ because it is not supported by the extensible key management provider ‘%ls’.
33084 16 The 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 cryp
33085 10 One or more methods cannot be found in cryptographic provider library ‘%.*ls’.
33086 10 SQL Server Audit failed to record %ls action.
33087 16 %S_MSG property of the key returned by EKM provider doesn’t match the expected value
33088 16 The algorithm: %.*ls is not supported for EKM operations by SQL Server
33089 16 Key validation failed since an attempt to get algorithm info for that key failed. Provider error code: %d. (%S_MSG)
33090 10 Attempting to load library ‘%.*ls’ into memory. This is an informational message only. No user action is required.
33091 10 Warning: 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
33101 16 Cannot 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.
33102 16 Cannot encrypt a system database. Database encryption operations cannot be performed for ‘master’, ‘model’, ‘tempdb’, ‘msdb’, or ‘resource’ databases.
33103 16 A database encryption key already exists for this database.
33104 16 A database encryption key does not exist for this database.
33105 16 Cannot 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.
33106 16 Cannot change database encryption state because no database encryption key is set.
33107 16 Cannot enable database encryption because it is already enabled.
33108 16 Cannot disable database encryption because it is already disabled.
33109 16 Cannot disable database encryption while an encryption, decryption, or key change scan is in progress.
33110 16 Cannot change database encryption key while an encryption, decryption, or key change scan is in progress.
33111 16 Cannot find server %S_MSG with thumbprint ‘%.*ls’.
33112 10 Beginning database encryption scan for database ‘%.*ls’.
33113 10 Database encryption scan for database ‘%.*ls’ is complete.
33114 10 Database encryption scan for database ‘%.*ls’ was aborted. Reissue ALTER DB to resume the scan.
33115 16 CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on the database. Try again later.
33116 16 CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database ‘%.*ls’. Try again later.
33117 16 Transparent 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.
33118 16 Cannot enable or modify database encryption on a database that is read-only, has read-only files or is not recovered.
33119 16 Cannot modify filegroup read-only/read-write state while an encryption transition is in progress.
33120 16 In order to encrypt the database encryption key with an %S_MSG, please use an %S_MSG that resides on an extensible key management provider.
33121 16 The %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’.
33122 16 This 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.
33123 16 Cannot drop or alter the database encryption key since it is currently in use on a mirror. Retry the command after all the previous reencryption scans have propagated to the mirror or after mirroring is disabled.
33124 10 Database encryption scan for database ‘%.*ls’ cannot complete since one or more files are offline. Bring the files online to run the scan to completion.
33125 10 Can 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.
33201 17 An 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.
33202 17 SQL Server Audit could not write to file ‘%s’.
33203 17 SQL Server Audit could not write to the event log.
33204 17 SQL Server Audit could not write to the security log.
33205 10 Audit event: %s.
33206 17 SQL Server Audit failed to create the audit file ‘%s’. Make sure that the disk is not full and that the SQL service account has the required permissions to create and write to the file.
33207 17 SQL 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.
33208 17 SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to access the security log.
33209 10 Audit ‘%.*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.
33210 10 SQL 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.
33211 15 A list of subentities, such as columns, cannot be specified for entity-level audits.
33212 15 There is an invalid column list after the object name in the AUDIT SPECIFICATION statement.
33213 16 All actions in an audit specification statement must be at the same scope.
33214 17 The operation cannot be performed because SQL Server Audit has not been started.
33215 10 One 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.
33216 10 SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
33217 10 SQL Server Audit is starting the audits. This is an informational message. No user action is required.
33218 10 SQL Server Audit has started the audits. This is an informational message. No user action is required.
33219 10 The 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.
33220 16 Audit actions at the server scope can only be granted when the current database is master.
33221 16 You can only create audit actions on objects in the current database.
33222 10 Audit ‘%.*ls’ failed to %.*ls. 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’.
33223 16 ALTER SERVER AUDIT requires the STATE option to be specified without using any other options.
33224 16 The specified pattern did not return any files or does not represent a valid file share. Verify the pattern parameter and rerun the command.
33225 16 The 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.
33226 10 The fn_get_audit_file function is skipping records from ‘%.*ls’ at offset %I64d.
33227 16 The specified value for QUEUE_DELAY is not valid. Specify either 0 or 1000 and higher.
33228 16 You 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.
33229 16 Changes to an audit specification must be done while the audit specification is disabled.
33230 16 An audit specification for audit ‘%.*ls’ already exists.
33231 16 You can only specify securable classes DATABASE, SCHEMA, or OBJECT in AUDIT SPECIFICATION statements.
33301 16 The %ls that is specified for conversation priority ‘%.*ls’ is not valid. The value must be between 1 and %d characters long.
33302 16 The %ls that is specified for conversation priority ‘%.*ls’ is not valid. The value must be between 1 and 10.
33303 16 A 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.
34001 16 Dialog with queue ‘syspolicy_event_queue’ has encountered an error: %s.
34002 16 Dialog with queue ‘syspolicy_event_queue’ has ended.
34003 16 Error number %d was encountered while processing an event. The error message is: %s.
34004 16 Execution mode %d is not a valid execution mode.
34010 16 %s ‘%s’ already exists in the database.
34011 16 Specified value for property %s cannot be used with execution mode %d.
34012 16 Cannot delete %s referenced by a %s.
34013 16 %s ‘%s’ is referenced by a ‘%s’. Cannot add another reference.
34014 16 Facet does not exist.
34015 16 Policy group %s does not exist.
34016 16 Invalid target filer: %s. Only filters that restrict the first level below the Server node are allowed.
34017 16 Automated policies cannot reference conditions that contain script.
34018 16 Target type “%s” is not a valid target type.
34019 16 Object “%s” is invalid.
34020 16 Configuration option “%s” is unknown.
34021 16 Invalid value type for configuration option “%s”. Expecting “%s”.
34022 16 Policy automation is turned off.
34050 16 %ls
34051 16 %ls
34052 16 %ls
34053 16 %ls
34054 16 Policy Management cannot be enabled on this edition of SQL Server.
34101 20 An error was encountered during object serialization operation. Examine the state to find out more details about this error.
34102 16 An object in serialized stream has version %u but maximum supported version of this class is %u.
34103 16 Error in formatter during serialize/deserialize. Required to process %d elements but processed only %d elements.
34104 16 An error was encountered during object serialization operation. The object that failed serialization is %hs.
35001 16 Parent Server Group does not exist.
35002 16 Server type and parent Server Group type are not the same
35003 16 Cannot move node to one of its children
35004 16 Could not find server group
35005 16 An invalid value NULL was passed in for @server_group_id.
35006 16 An invalid value NULL was passed in for @server_id.
35007 16 Could not find shared registered server.
35008 16 Cannot delete system shared server groups.
35009 16 An invalid value NULL was passed in for @server_type.
35010 16 An invalid value %d was passed in for parameter @server_type.
35011 16 The @server_name parameter cannot be a relative name.
35012 16 You cannot add a shared registered server with the same name as the Configuration Server.
36001 16 %s ‘%s’ already exists in the database.
36002 16 instance_id already exists in the database.
36003 16 %s ‘%s’ already exists for the given DAC instance.
36004 16 DacInstance with the specified instance_id does not exist.
36005 16 Dac root – database %s does not exist.
36006 16 Dac Policy with the specified policy id already exists in the parts table.
36007 16 Dac Part the policy refers to, does not exist.
36008 16 Dac Policy refers to a non-existent Policy.
36009 16 %s ‘%s’ already exists in the Dac Parts.
36010 16 The caller must be a member of the dbcreator fixed server role to perform this action.
36011 16 The caller must be sysadmin or the creator of the history entry being updated.
36012 10 Unable to execute T-SQL within procedure due to SQL Server limitation.\nPlease execute following T-SQL in database ‘%s’ context after this procedure finishes:\n%s
37001 16 This operation is not allowed since there are dependent objects pending installation.
37002 16 Cannot find the database ‘%s’, because it does not exist or you do not have permission to access it.
37003 16 This operation is not allowed because a utility control point already exists on this instance of SQL Server.
37004 16 The specified instance of SQL Server cannot be used as a utility control point because the feature is not enabled in SQL Server ‘%s’.
37005 16 The specified instance of SQL Server cannot be managed by a utility control point because the feature is not enabled in SQL Server ‘%s’.
37006 16 Cannot perform the operation because the specified instance of SQL Server is not enrolled in a SQL Server utility.
37007 16 An error occurred during upload to the SQL Server utility control point.
37008 16 The operation cannot continue. To remove the SQL Server utility control point, the user must be a member of the sysadmin role.
37009 16 The operation cannot continue. The specified instance of SQL Server is not a SQL Server utility control point.
37010 16 The operation cannot continue. The SQL Server utility control point has managed instances of SQL Server enrolled.
38001 16 Cannot find the file id %d in the database ‘%s’.
38002 16 Only users having %s permission can execute this stored procedure.

sql server error list 22000 to 39000
sql server error list error codes 22000 to 39000
sql server error numbers 22000 to 39000
sql server error list 2005 22000 to 39000
sql server error list 2008 22000 to 39000
sql server 2008 error message list 22000 to 39000
sql server errors logs
sql server errors list table

(Visited 1,029 times, 1 visits today)