SQL Server System Errors: 30000 - 32999
List of error messages between 30000 and 32999 in SQL Server 2017.
These error messages are all available by querying the sys.messages catalog view on the master database.
| message_id | severity | is_event_logged | text |
|---|---|---|---|
| 30003 | 16 | 0 | A fulltext system view or stvf cannot open database id %d. |
| 30004 | 16 | 0 | A fulltext system view or stvf cannot open user table object id %d. |
| 30005 | 16 | 0 | The name specified for full-text index fragment %.*ls is not valid. |
| 30006 | 16 | 0 | A fulltext system view or stvf cannot open fulltext index for user table object id %d. |
| 30007 | 16 | 0 | Parameters of dm_fts_index_keywords, dm_fts_index_keywords_by_document, dm_fts_index_keywords_by_property, and dm_fts_index_keywords_position_by_document cannot be null. |
| 30008 | 16 | 0 | This is an internal error when invoking the TVF to access the full-text index. The level number specified for the TVF is not valid. Valid level numbers start from 0 and must be less than the number of levels of the compressed index. |
| 30009 | 16 | 0 | The argument data type '%ls' specified for the full-text query is not valid. Allowed data types are char, varchar, nchar, nvarchar. |
| 30020 | 16 | 0 | The full-text query parameter for %S_MSG is not valid. |
| 30022 | 10 | 0 | 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-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name START FULL POPULATION. |
| 30023 | 16 | 0 | 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 | 0 | 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. |
| 30025 | 16 | 0 | The search property list '%.*ls' does not exist or you do not have permission to perform this action. Verify that the correct search property list name is specified and that you have the permission required by the Transact-SQL statement. For a list of the search property lists on the current database, use the sys.registered_search_property_lists catalog view. For information about permissions required by a Transact-SQL statement, see the Transact-SQL reference topic for the statement in SQL Server Books Online. |
| 30026 | 16 | 0 | The search property list '%.*ls' already exists in the current database. Duplicate search property list names are not allowed. Rerun the statement and specify a unique name for the search property list. For a list of the search property lists on the current database, use the sys.registered_search_property_lists catalog view. |
| 30027 | 10 | 0 | The full-text index is in an inconsistent state because the search property list of the full-text index was reconfigured using the WITH NO POPULATION clause. To bring the full-text index into a consistent state, start a full population using the statement ALTER FULLTEXT INDEX ON |
| 30028 | 17 | 0 | 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 | 0 | The full-text host controller failed to start. Error: 0x%X. |
| 30030 | 16 | 0 | The search property '%.*ls' does not exist, or you do not have permission to perform this action. Verify that the correct search property is specified and that you have the permission required by the Transact-SQL statement. For a list of the search properties on the current database, use the sys.registered_search_properties catalog view. For information about the permissions required by a Transact-SQL statement, see the Transact-SQL reference topic for the statement in SQL Server Books Online. |
| 30031 | 17 | 0 | A full-text master merge failed on full-text catalog '%ls' in database '%.*ls' with error 0x%08X. |
| 30032 | 16 | 0 | 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 | 0 | 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 | 0 | 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 then look up that stoplist ID in the stoplist_id column of the sys.fulltext_stoplists catalog view. Either drop the full-text index by using DROP FULLTEXT INDEX or change its stoplist setting by using ALTER FULLTEXT INDEX. Then retry dropping the stoplist. |
| 30035 | 16 | 0 | The search property '%.*ls' already exists in the search property list. Specify a search property name that is unique within the specified search property list. For a list of the search properties on the current database, use the sys.registered_search_properties catalog view. |
| 30036 | 16 | 0 | Search property list '%.*ls' cannot be dropped because it is being used by at least one full-text index. To identify the full-text indexes that are using the search property list, obtain the search property list id from the property_list_id column of the sys.registered_search_property_lists catalog view, and then obtain the object ID of every table or indexed view whose full-text index is associated with this search property list from the object_id and property_list_id columns of the sys.fulltext_indexes catalog view . For each full-text index, either remove the search property list or drop the full-text index, if it is no longer needed. To remove the search property list, use ALTER FULLTEXT INDEX ON <table_name> SET SEARCH PROPERTY LIST OFF;. To drop a full-text index, use DROP FULLTEXT INDEX ON <table_name>;. |
| 30037 | 16 | 0 | An argument passed to a fulltext function is not valid. |
| 30038 | 17 | 0 | 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 | 0 | 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. |
| 30040 | 10 | 0 | During a full-text crawl of table or indexed view '%ls', an unregistered property, '%ls', was found in batch ID %d. This property will be indexed as part of the generic content and will be unavailable for property-scoped full-text queries. Table or indexed view ID is '%d'. Database ID is '%d'. For information about registering properties and updating the full-text index of a table or indexed view, see the full-text search documentation in SQL Server Books Online. This is an informational message. No user action is necessary. |
| 30041 | 10 | 0 | The master merge started at the end of the full crawl of table or indexed view '%ls' failed with HRESULT = '0x%08x'. Database ID is '%d', table id is %d, catalog ID: %d. |
| 30043 | 16 | 0 | Stopwords of zero length cannot be added to a full-text stoplist. Specify a unique stopword that contains at least one character. |
| 30044 | 16 | 0 | 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 | 0 | 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 | 0 | 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 the SQL Server instance. |
| 30047 | 16 | 0 | The user does not have permission to %.*ls stoplist '%.*ls'. |
| 30048 | 10 | 0 | Informational: Ignoring duplicate thesaurus rule '%ls' while loading thesaurus file for LCID %d. A duplicate thesaurus phrase was encountered in either the <sub> section of an expansion rule or the <pat> section of a replacement rule. This causes an ambiguity and hence this phrase will be ignored. |
| 30049 | 17 | 0 | Fulltext thesaurus internal error (HRESULT = '0x%08x') |
| 30050 | 16 | 0 | Both the thesaurus file for lcid '%d' and the global thesaurus could not be loaded. |
| 30051 | 16 | 0 | Phrases longer than 512 unicode characters are not allowed in a thesaurus file. Phrase: '%ls'. |
| 30052 | 16 | 0 | 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 repeated terms. |
| 30053 | 16 | 0 | An error has occurred during the full-text query. Common causes include: word-breaking errors or timeout, FDHOST permissions/ACL issues, service account missing privileges, malfunctioning IFilters, communication channel issues with FDHost and sqlservr.exe, etc. |
| 30055 | 10 | 0 | Full-text catalog import has started for full-text catalog '%ls' in database '%ls'. |
| 30056 | 10 | 0 | Full-text catalog import has finished for full-text catalog '%ls' in database '%ls'. %d fragments and %d keywords were processed. |
| 30057 | 10 | 0 | Upgrade option '%ls' is being used for full-text catalog '%ls' in database '%ls'. |
| 30058 | 16 | 0 | Properties of zero length cannot be added to a search property list. Specify a search property name that contains at least one character and that is unique to the specified search property list. For a list of the search properties on the current database, use the sys.registered_search_properties catalog view. |
| 30059 | 16 | 0 | 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 crawl log. Then, resume the population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name RESUME POPULATION. |
| 30060 | 16 | 0 | 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 it, or by taking the database offline and bringing it back online. If the error is not recoverable, rebuild the full-text catalog. |
| 30061 | 17 | 0 | 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 after the issue is fixed. |
| 30062 | 17 | 0 | The SQL Server failed to load FDHost service group sid. This might be because installation is corrupted. |
| 30063 | 10 | 0 | Warning: SQL Server could not set fdhost.exe processor affinity to %d because the value is not valid. |
| 30064 | 17 | 0 | 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. |
| 30065 | 10 | 0 | Filegroup '%ls' is offline, readonly, or no data file. Full-text population on table '%ls' is not resumed. Resume full-text population after fixing the filegroup status. |
| 30067 | 10 | 0 | 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 and then detach it. This warning will not fail the database detach operation. |
| 30068 | 10 | 0 | 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 | 0 | 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 avoid this, rebuild the full-text catalog using the current version of the filter component. |
| 30070 | 10 | 0 | 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 | 0 | 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 results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the word-breaker component. |
| 30072 | 10 | 0 | 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 | 0 | 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 slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the protocol handler component. |
| 30074 | 17 | 0 | The master merge of full-text catalog '%ls' in database '%.*ls' was cancelled. |
| 30075 | 10 | 0 | 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 | 0 | 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 | 0 | 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 term. |
| 30078 | 10 | 0 | 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 | 0 | The full text query ignored UNKNOWN in the OPTIMIZE FOR hint. |
| 30080 | 16 | 0 | 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 | 0 | 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 | 0 | Full-text predicates cannot appear in an aggregate expression. Place the aggregate expression in a subquery. |
| 30083 | 16 | 0 | Full-text predicates cannot appear in the GROUP BY clause. Place a GROUP BY clause expression in a subquery. |
| 30084 | 16 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | The full-text filter daemon host process has stopped normally. The process will be automatically restarted if necessary. |
| 30089 | 17 | 0 | 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 indexing or query processing. The process will be restarted automatically. |
| 30090 | 10 | 0 | A new instance of the full-text filter daemon host process has been successfully started. |
| 30091 | 10 | 0 | 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 ON %.*ls RESUME POPULATION. To stop it, use the following statement: ALTER FULLTEXT INDEX ON %.*ls STOP POPULATION. |
| 30092 | 16 | 0 | Full-text stoplist ID '%d' does not exist. |
| 30093 | 17 | 0 | 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 resolved. Try stopping SQL Server and any filter daemon host processes and then restarting the instance of SQL Server. |
| 30094 | 17 | 0 | 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 | 0 | 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. To avoid any possible inconsistencies of query results, consider rebuilding the full-text catalog. |
| 30096 | 10 | 0 | 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 | 0 | 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 or recreated before attach. |
| 30098 | 10 | 0 | 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 removed. |
| 30099 | 17 | 0 | Fulltext internal error |
| 30101 | 16 | 0 | The parameter '%s' is mandatory in stored procedure '%s'. |
| 30103 | 16 | 0 | Invalid CM instance name. |
| 30104 | 16 | 0 | Invalid matrix name. |
| 30105 | 16 | 0 | Invalid TCP port number: %s. |
| 30106 | 16 | 0 | Invalid network security level. |
| 30107 | 16 | 0 | Invalid network isolation level. |
| 30108 | 16 | 0 | Invalid matrix guid. |
| 30109 | 16 | 0 | Invalid or duplicated brick ID was used: %s |
| 30110 | 16 | 0 | Invalid parameter. |
| 30111 | 16 | 0 | Matrix setup stored procedure '%s' failed with HRESULT 0x%x. |
| 30112 | 16 | 0 | Insert brick into metadata operation failed during execution of stored procedure '%s'. |
| 30113 | 16 | 0 | Insert manager into metadata operation failed during execution of stored procedure '%s'. |
| 30114 | 16 | 0 | Insert parameter into metadata operation failed during execution of stored procedure '%s'. |
| 30115 | 16 | 0 | No more bricks can be reserved. The maximum amount of %lu bricks is reached. |
| 30118 | 16 | 0 | Invalid server name provided to configure a matrix brick. |
| 30119 | 16 | 0 | Invalid CM brick GUID. |
| 30120 | 16 | 0 | Invalid brick GUID. |
| 30121 | 16 | 0 | '%s' in only allowed in standalone (non matrix) mode. |
| 30122 | 16 | 0 | '%s' in only allowed in single user (-m) mode. |
| 30123 | 16 | 0 | Drop existing matrix configuration failed during execution of stored procedure '%s'. |
| 30124 | 16 | 0 | An error occurred while updating the CM metadata to remove a brick. |
| 30125 | 16 | 0 | Configuration manager could not write the WMI offline configuration file during the execution of stored procedure '%s'. |
| 30126 | 16 | 0 | Could not complete the last operation with the brick_id %u due a metadata failure |
| 30127 | 16 | 0 | Attempt to cancel the reservation of a brick that is not reserved: %u |
| 30128 | 16 | 0 | The stored procedure '%s' failed with the error code %d |
| 30129 | 16 | 0 | '%s' in only allowed in matrix mode. |
| 30130 | 16 | 0 | The brick with server name '%s' already exists in the configuration. |
| 31001 | 16 | 0 | The session '%s' already exists. Use a different session name. |
| 31002 | 16 | 0 | This operation can be performed only by the owner of the session. |
| 31003 | 16 | 0 | User does not have enough permissions to tune one or more of the databases specified. |
| 31004 | 16 | 0 | Could not create DTA directory for saving tuning option file when invoking DTA for auto indexing. |
| 31005 | 16 | 0 | Could not create DTA tuning option file when invoking DTA for auto indexing. |
| 31006 | 16 | 0 | Could not write DTA tuning option to file when invoking DTA for auto indexing. |
| 31007 | 16 | 0 | Could not create a DTA job when invoking DTA for auto indexing. |
| 31008 | 16 | 0 | Could not retrieve limit and job state information from DTA job object when invoking DTA for auto indexing. |
| 31009 | 16 | 0 | Could not set limits on DTA job object when invoking DTA for auto indexing. |
| 31010 | 16 | 0 | Could not create a DTA process when invoking DTA for auto indexing. |
| 31011 | 16 | 0 | Could not terminate DTA process after it fails to be assigned to DTA job object when invoking DTA for auto indexing. |
| 31012 | 16 | 0 | Could not resume DTA process to start tuning when invoking DTA for auto indexing. |
| 31013 | 16 | 0 | Invalid tuning option specified for auto indexing. |
| 31014 | 16 | 0 | Could not terminate DTA job when cancelling DTA tuning for auto indexing. |
| 31015 | 16 | 0 | Could not delete DTA tuning options file when cancelling DTA tuning for auto indexing. |
| 31016 | 16 | 0 | Could not cleanup hypothetical indexes and statistics when cancelling DTA tuning for auto indexing. |
| 31017 | 16 | 0 | DTA tuning for auto indexing is only supported on Azure DB. |
| 31018 | 16 | 0 | Could not get winfab temp directory when performing DTA tuning related task. |
| 31019 | 16 | 0 | Could not create GUID when performing DTA tuning related task. |
| 31020 | 16 | 0 | String operation failed. |
| 31021 | 16 | 0 | Could not get winfab log directory when performing DTA tuning related task. |
| 31022 | 16 | 0 | Could not get winfab data package directory when performing DTA tuning related task. |
| 31201 | 16 | 0 | Property-scoped full-text queries cannot be specified on the specified table because its full-text index is not configured for property searching. To support property-scoped searches, the full-text index must be associated with a search property list and repopulated. The Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON <table_name> SET SEARCH PROPERTY LIST >property_list_name<;. |
| 31202 | 10 | 0 | Reconfiguring the search property list of the full-text index has truncated the existing data in the index. Until the full-text index has been fully repopulated, full-text queries will return partial results. The ALTER FULLTEXT INDEX <table_name> SET SEARCH PROPERTY LIST ...; statement automatically issues a full population, but if the ALTER FULLTEXT INDEX statement specified the WITH NO POPULATION clause, you must run a full population on the full-text index using ALTER FULLTEXT INDEX ON <table_name> START FULL POPULATION;. This is a warning. |
| 31203 | 10 | 0 | Warning Master Merge operation was not done for dbid %d, objid %d, so querying index will be slow. Please run alter fulltext catalog reorganize. |
| 31204 | 16 | 0 | Operation %ls is not supported on the %ls platform. |
| 32001 | 10 | 0 | Log shipping backup log job for %s. |
| 32002 | 10 | 0 | Log shipping copy job for %s:%s. |
| 32003 | 10 | 0 | Log shipping restore log job for %s:%s. |
| 32004 | 10 | 0 | Log shipping backup log job step. |
| 32005 | 10 | 0 | Log shipping copy job step. |
| 32006 | 10 | 0 | Log shipping restore log job step. |
| 32007 | 16 | 0 | Database %s is not ONLINE. |
| 32008 | 10 | 0 | Database %s is not ONLINE. The backup job will not be performed until this database is brought online. |
| 32009 | 16 | 0 | A log shipping primary entry already exists for database %s. |
| 32010 | 16 | 0 | Database %s does not exist as log shipping primary. |
| 32011 | 16 | 0 | Primary Database %s has active log shipping secondary database(s). Drop the secondary database(s) first. |
| 32012 | 16 | 0 | Secondary %s.%s already exists for primary %s. |
| 32013 | 16 | 0 | A log shipping entry already exists for secondary database %s. |
| 32014 | 16 | 0 | Database %s does not exist as log shipping secondary. |
| 32015 | 16 | 0 | The primary database %s cannot have SIMPLE recovery for log shipping to work properly. |
| 32016 | 16 | 0 | The specified agent_id %s or agent_type %d do not form a valid pair for log shipping monitoring processing. |
| 32017 | 16 | 0 | Log shipping is supported on Enterprise, Developer and Standard editions of SQL Server. This instance has %s and is not supported. |
| 32018 | 16 | 0 | Log shipping is not installed on this instance. |
| 32019 | 10 | 0 | Log shipping alert job. |
| 32020 | 10 | 0 | Log shipping alert job step. |
| 32021 | 10 | 0 | Log shipping alert job schedule. |
| 32022 | 16 | 0 | 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 | 0 | An entry for primary server %s, primary database %s does not exist on this secondary. Register the primary first. |
| 32024 | 16 | 0 | An entry for primary server %s, primary database %s already exists. |
| 32025 | 16 | 0 | Primary Server %s, Database %s has active log shipping secondary database(s) on the secondary. Drop the secondary database(s) first. |
| 32026 | 10 | 0 | Log shipping Primary Server Alert. |
| 32027 | 10 | 0 | Log shipping Secondary Server Alert. |
| 32028 | 16 | 0 | Invalid value = %d for parameter @threshold_alert was specified. |
| 32029 | 10 | 0 | 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 | 0 | Could not query monitor information for log shipping primary %s.%s from monitor server %s. |
| 32031 | 10 | 0 | Could not query monitor information for log shipping secondary %s.%s from monitor server %s. |
| 32032 | 16 | 0 | Invalid value '%d' for update period. Update period should be between 1 and 120 minutes. |
| 32033 | 16 | 0 | The update job for the database mirroring monitor already exists. To change the update period, use sys.sp_dbmmonitorchangemonitoring |
| 32034 | 16 | 0 | An internal error occurred when setting up the database mirroring monitoring job. |
| 32035 | 16 | 0 | An internal error occurred when modifying the database mirroring monitoring job. |
| 32036 | 16 | 0 | Parameter(s) out of range. |
| 32037 | 16 | 0 | The units for the update period for the database mirroring monitor job have been changed. |
| 32038 | 16 | 0 | An internal error has occurred in the database mirroring monitor. |
| 32039 | 16 | 0 | The database '%s' is not being mirrored. No update of the base table was done. |
| 32040 | 16 | 0 | The alert for 'oldest unsent transaction' has been raised. The current value of '%d' surpasses the threshold '%d'. |
| 32041 | 16 | 0 | The database mirroring monitor base tables have not been created. Please run sys.sp_dbmmonitorupdate to create them. |
| 32042 | 16 | 0 | The alert for 'unsent log' has been raised. The current value of '%d' surpasses the threshold '%d'. |
| 32043 | 16 | 0 | The alert for 'unrestored log' has been raised. The current value of '%d' surpasses the threshold '%d'. |
| 32044 | 16 | 0 | The alert for 'mirror commit overhead' has been raised. The current value of '%d' surpasses the threshold '%d'. |
| 32045 | 16 | 0 | '%s' must be executed in msdb. |
| 32046 | 16 | 0 | Only members of the sysadmin fixed server role or the 'dbm_monitor' role in msdb can perform this operation. |
| 32047 | 15 | 0 | Database Mirroring Monitor Job |
| 32048 | 15 | 0 | Database Mirroring Monitor Schedule |
| 32049 | 16 | 0 | The database mirroring monitoring job does not exist. Run sp_dbmmonitoraddmonitoring to setup the job. |
| 32050 | 16 | 0 | Alerts cannot be created on the system databases, master, msdb, model or tempdb. |
| 32051 | 10 | 0 | System administrator privilege is required to update the base table. The base table was not updated. |
| 32052 | 16 | 0 | Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation. |
| 32053 | 16 | 0 | The server name, given by '@@servername', is currently null. |
| 32054 | 16 | 0 | There was an error establishing a link to the remote monitor server. |
| 32055 | 16 | 0 | There was an error configuring the remote monitor server. |
| 32056 | 17 | 0 | The SQL Server failed to create full-text FTData directory. This might be because FulltextDefaultPath is invalid or SQL Server service account does not have permission. Full-text may fail until this issue is resolved. Restart SQL Server after the issue is fixed. |