错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 11 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 19814 — Database could not be successfully detached for deletion.
- 19815 — Workspace state could not be successfully fetched.
- 19816 — Complex types not supported for parquet data unit. Underlying data description: %ls.
- 19817 — DataBlock size is too small. Underlying data description: %ls.
- 19818 — DataBlock column offset is incorrect. Underlying data description: %ls.
- 19819 — DataBlock column sizes offset is incorrect. Underlying data description: %ls.
- 19820 — DataBlock column options are incorrect. Underlying data description: %ls.
- 19821 — DataBlock size is incorrect. Underlying data description: %ls.
- 19822 — Decimal rescale failed. Underlying data description: %ls.
- 19823 — Empty column name found while resolving schema for CosmosDB collection: %ls.
- 19824 — Error encountered while reading data: '%ls'. Underlying data description: %ls.
- 19825 — Column count mismatch, the column count in the file doesn't match column count in the table schema when reading row %d. Set the MATCH_COLUMN_COUNT opt…
- 19826 — Error encountered while updating One Security mode for database '%ls' under workspace '%ls'.
- 19827 — Column count mismatch, the column count in the file doesn't match column count in the table schema. Column '%ls' is not present in the table. Set the …
- 19828 — Column count mismatch, the column count in the file doesn't match column count in the table schema. Column '%ls' is not present in the file. Set the M…
- 19829 — Error encountered while trying to lock a shared object %d.
- 19830 — Cannot grant, deny, or revoke %.*ls permission because the warehouse is in user's identity mode for OneLake access. To use these statements, the wareh…
- 19831 — Cannot change membership of the fixed database roles because the warehouse is in user's identity mode for OneLake access. To use these statements, the…
- 19832 — Error in reading Frontend instance certificate thumbprint.
- 19833 — Select statements are not allowed in SQL scalar user defined functions.
- 19834 — Database backup failed.
- 19835 — Scalar UDF execution is currently unavailable in this context. See https://go.microsoft.com/fwlink/?linkid=2304777 for updates.
- 19836 — Unable to execute CREATE, ALTER, or DROP for a security policy on user tables because the warehouse is in user's identity mode for OneLake access. To …
- 19837 — CODEPAGEs different than 65001 and 1200 are not supported when JSON/JSONL format is specified.
- 19838 — CODEPAGE different than 65001 is not supported when JSON/JSONL format is specified.
- 19839 — File read failed because the total LOB size (%I64u) bytes of the current row exceeds the defined limit (%I64u) bytes.
- 19840 — Failed to attach database for recovery.
- 19841 — Function %.*ls.%.*ls cannot be inlined. Expression block: %.*ls%.*ls. Scalar UDF inlining: %.*ls%.*ls. Choose an option: For standalone execution: Cre…
- 19842 — Function %.*ls.%.*ls was created with INLINE=AUTO and is not inlineable. Function can be invoked only as a standalone scalar expression, not over a us…
- 19843 — Credential injection completed successfully.
- 19844 — Log activation failed while primary data file is started. This typically indicates the log file is locked by another process. Automatic log rebuild is…
- 19845 — Error encountered while setting user's Security Sync flag for database '%ls' under workspace '%ls'.
- 19846 — Failed to record the database recovery model change notification to the STO.
- 19847 — Unexpected error happened during IO against file: '%ls'. Underlying data description: %ls.
- 19848 — Request rejected for user '%.*ls'. The workspace capacity is throttled.%.*ls
- 19849 — Function %.*ls.%.*ls can be inlined via Expression block.
- 19850 — Function %.*ls.%.*ls can be inlined via Scalar UDF inlining, which supports a sub-set of query shapes. See https://go.microsoft.com/fwlink/?linkid=237…
- 19851 — Function %.*ls.%.*ls can be inlined via Expression block and Scalar UDF inlining. Inlining eligibility may affect supported query shapes. See https://…
- 19852 — '%.*ls' is not a supported STORAGE_PROFILE.
- 19853 — The connection type is not expected from %ls.
- 19901 — An internal error occurred.
- 20001 — There is no nickname for article '%s' in publication '%s'.
- 20002 — The filter '%s' already exists for article '%s' in publication '%s'.
- 20003 — Could not generate nickname for '%s'.
- 20004 — Publication '%s' has the following property: '%s'. SQL Server subscribers below version '%s' will ignore this setting.
- 20005 — %ls: Cannot convert parameter %ls: Resulting colv would have too many entries.
- 20006 — Cannot make the change because the article might be in a publication that has anonymous or client subscriptions. Set @force_reinit_subscription to 1 t…
- 20007 — The system tables for merge replication could not be dropped successfully.
- 20008 — The system tables for merge replication could not be created successfully.
- 20009 — The article '%s' could not be added to the publication '%s'.
- 20010 — The Snapshot Agent corresponding to the publication '%s' could not be dropped.
- 20011 — Cannot set incompatible publication properties. The 'allow_anonymous' property of a publication depends on the 'immediate_sync' property.
- 20012 — The subscription type '%s' is not allowed on publication '%s'.
- 20013 — The publication property '%s' cannot be changed when there are subscriptions on it.
- 20014 — Invalid @schema_option value.
- 20015 — Could not remove directory '%ls'. Check the security context of xp_cmdshell and close other processes that may be accessing the directory.
- 20016 — Invalid @subscription_type value. Valid values are 'pull' or 'anonymous'.
- 20017 — The subscription on the Subscriber does not exist.
- 20018 — The @optional_command_line is too long. Use an agent definition file.
- 20019 — Replication database option '%s' cannot be set unless the database is a publishing database or a distribution database.
- 20020 — The article resolver supplied is either invalid or nonexistent.
- 20021 — The subscription could not be found.
- 20022 — This article has now settings to disable uploads and compensate_for_errors=true. However, local and anonymous subscribers will behave as if compensate…
- 20023 — Invalid @subscriber_type value. Valid options are 'local', 'global', or 'anonymous'.
- 20024 — The alt_snapshot_folder cannot be the same as the working directory.
- 20025 — The publication name must be unique. The specified publication name '%s' has already been used.
- 20026 — The publication '%s' does not exist.
- 20027 — The article '%s' does not exist.
- 20028 — The Distributor has not been installed correctly. Could not enable database for publishing.
- 20029 — The Distributor has not been installed correctly. Could not disable database for publishing.
- 20030 — The article '%s' already exists on another publication with a different column tracking option.
- 20031 — Could not delete the row because it does not exist.
- 20032 — '%s' is not defined as a Subscriber for '%s'.
- 20033 — Invalid publication type.
- 20034 — Publication '%s' does not support '%s' subscriptions.
- 20036 — The Distributor has not been installed correctly.
- 20037 — The article '%s' already exists in another publication with a different article resolver.
- 20038 — The article filter could not be added to the article '%s' in the publication '%s'.
- 20039 — The article filter could not be dropped from the article '%s' in the publication '%s'.
- 20040 — Could not drop the article(s) from the publication '%s'.
- 20041 — Transaction rolled back. Could not execute trigger. Retry your transaction.
- 20043 — Could not change the article '%s' because the publication has already been activated.
- 20044 — The priority property is invalid for local subscribers.
- 20045 — You must supply an article name.
- 20046 — The article does not exist.
- 20047 — You are not authorized to perform this operation.
- 20048 — To modify the priority of a subscription, run sp_changemergesubscription at the Publisher instead of using sp_changemergepullsubscription at subscribe…
- 20049 — The priority value should not be larger than 100.0.
- 20050 — The retention period must be greater than or equal to 0, and it must not extend past December 31, 9999.
- 20051 — The Subscriber is not registered.
- 20052 — The @metatype parameter value must be null, 1, 2, 5, or 6.
- 20053 — An article with a different %s value already exists for object '%s'.
- 20054 — Current database is not enabled for publishing.
- 20055 — Table '%s' cannot be published for merge replication because it has a timestamp column.
- 20056 — Table '%s' cannot be republished.
- 20057 — The profile name '%s' already exists for the specified agent type.
- 20058 — The @agent_type must be 1 (Snapshot), 2 (Logreader), 3 (Distribution), or 4 (Merge)
- 20059 — The @profile_type must be 0 (System) or 1 (Custom)
- 20060 — Compatibility level cannot be smaller than 60.
- 20061 — The compatibility level of this database must be set to 70 or higher to be enabled for merge publishing.
- 20062 — Updating columns with the rowguidcol property is not allowed.
- 20063 — Table '%s' into which you are trying to insert, update, or delete data has been marked as read-only. Only the merge process can perform these operatio…
- 20064 — Cannot drop profile. Either it is not defined or it is defined as the default profile.
- 20065 — Cannot drop profile because it is in use.
- 20066 — Profile not defined.
- 20067 — The parameter name '%s' already exists for the specified profile.
- 20068 — The article cannot be created on table '%s' because it has more than %d columns.
- 20069 — Cannot validate a merge article that uses looping join filters.
- 20070 — Cannot update subscription row.
- 20072 — Cannot update Subscriber information row.
- 20073 — Articles can be added or changed only at the Publisher.
- 20074 — Only a table object can be published as a "table" article for merge replication.
- 20075 — The 'status' parameter value must be either 'active' or 'unsynced'.
- 20076 — The @sync_mode parameter value must be 'native' or 'character'.
- 20077 — Problem encountered generating replica nickname.
- 20078 — The @property parameter value must be one of the following: 'sync_type', 'priority', 'description', 'subscriber_security_mode', 'subscriber_login', 's…
- 20079 — Invalid @subscription_type parameter value. Valid options are 'push', 'pull', or 'both'.
- 20081 — Publication property '%s' cannot be NULL.
- 20084 — Publication '%s' cannot be subscribed to by Subscriber database '%s'.
- 20086 — Publication '%s' does not support the nosync type because it contains a table that does not have a rowguidcol column.
- 20087 — You cannot push an anonymous subscription.
- 20088 — Only assign priorities that are greater than or equal to 0 and less than 100.
- 20089 — Could not get license information correctly.
- 20090 — Could not get version information correctly.
- 20091 — sp_mergesubscription_cleanup is used to clean up push subscriptions. Use sp_dropmergepullsubscription to clean up pull or anonymous subscriptions.
- 20092 — Table '%s' into which you are trying to insert, update, or delete data is currently being upgraded or initialized for merge replication. On the publis…
- 20093 — Merge replication upgrade is not complete until the snapshot agent is run for the publisher and the merge agent run for all the subscribers.
- 20094 — Profile parameter '%s' is dynamically reloadable and the change will be applied to running agents within configured period of time.
- 20095 — For agent profile '%s', parameters marked as is_reloadable in msdb.dbo.MSagentparameterlist table will be applied to running agents within configured …
- 20100 — Cannot drop Subscriber '%s'. There are existing subscriptions.
- 20201 — [Data Recovery][DbId: %d]: An internal call to create an accessor for rowset %I64d failed when processing log record at %S_LSN.
- 20202 — [Data Recovery][DbId: %d]: Cannot find a row with the clustered key in log record %S_LSN for rowset %I64d.
- 20203 — [Data Recovery][DbId: %d]: Cannot find the page that contains the row with the clustered key in log record %S_LSN for rowset %I64d.
- 20204 — [Data Recovery]: CREATE TABLE statement failed on tempdb for annotated logs with error %d.
- 20205 — [Data Recovery]: INSERT statement failed on tempdb for annotated logs. DbId: %d, HRESULT: 0x%x.
- 20206 — [Data Recovery]: UPDATE statement failed on tempdb for annotated logs with error %d.
- 20207 — [Data Recovery]: DROP TABLE statement failed on tempdb for annotated logs with error %d.
- 20208 — [Data Recovery]: Read failed on tempdb for annotated logs with error %d.
- 20209 — [Data Recovery]: LSN generation failed for annotated logs with error %d.
- 20211 — [Data Recovery]: Unable to create recovery file %ls for database ID %d. Error: %d.
- 20212 — [Data Recovery]: Unable to append to recovery file %ls for database ID %d. Error: %d.
- 20213 — [Data Recovery]: Unable to close recovery file %ls for database ID %d. Error: %d.
- 20214 — [Data Recovery]: File %ls was created for database ID %d.
- 20215 — [Data Recovery]: Error encountered when generating content in the recovery file for database with ID %d.
- 20216 — [Data Recovery]: Invalid value for parameter '%ls'.
- 20217 — [Data Recovery]: The Data Recovery folder path is invalid: %ls.
- 20218 — [Data Recovery]: User does not have permission to perform this operation. The ALTER ANY AVAILABILITY GROUP permission is required.
- 20219 — [Data Recovery]: Data Recovery folder path '%ls' validation failed. HRESULT: 0x%08x. Ensure the folder path exists and the service account has proper …
- 20220 — [Data Recovery]: The Data Recovery feature is not enabled on this SQL Server instance. Enable the feature before using this stored procedure.
- 20221 — [Data Recovery]: Unable to delete temporary file during directory validation. Error: %d. Check file permissions and disk space in the target directory…
- 20222 — [Data Recovery]: Failed to convert string to LSN with error %d.
- 20223 — [Data Recovery]: Failed to fetch data from annotated log table with error %d.
- 20224 — [Data Recovery]: Failed to SetRange for annotated log table with error %d.
- 20225 — [Data Recovery]: Failed to create accessor for annotated log table with error %d.
- 20226 — [Data Recovery]: Unable to get DBTABLE due to error: %d.
- 20227 — [Data Recovery]: Failed to access AnnotatedLogMgr with error %d.
- 20228 — [Data Recovery][DbId: %d]: Data Recovery encountered an unexpected log record at %S_LSN, with OpCode = %ld and context = %ld.
- 20229 — [Data Recovery][DbId: %d]: Data Recovery failed a consistency check at %S_LSN. Reason: %ls.
- 20230 — [Data Recovery][DbId: %d]: Data Recovery encountered a LOP_TEXT_INFO_END log at %S_LSN that does not have a matching complex column in inrow data with…
- 20231 — [Data Recovery]: Failed to access master database metadata for Data Recovery settings with error %d, severity %d, state %d.
- 20232 — [Data Recovery]: Unable to create temporary file '%ls' during directory validation. Error: %d. Check directory permissions and manually remove any lef…
- 20233 — [Data Recovery]: Unable to write to temporary file '%ls' during directory validation. Error: %d. Check write permissions for the directory.
- 20234 — [Data Recovery]: Unable to delete temporary file '%ls' during directory validation. Error: %d. Please delete the temporary file to prevent disk space …
- 20235 — [Data Recovery][DbId: %d]: Cannot find a column with column ID %d for rowset %I64d when processing log record at %S_LSN.
- 20236 — [Data Recovery][DbId: %d]: Data Recovery encountered a LOP_TEXT_INFO_BEGIN log at %S_LSN that is correlated to a different column than the LOP_TEXT_IN…
- 20237 — [Data Recovery][DbId: %d]: Data Recovery encountered a LOP_BEGIN_XACT log at %S_LSN while not all complex columns of the last DML statement have been …
- 20238 — [Data Recovery]: Cannot update Data Recovery settings because the feature is currently disabled. Enable the feature first using @action = 'enable'.
- 20239 — [Data Recovery][DbId: %d]: Data Recovery failed to write %ld bytes of blob fragment to blob handle for log record at %S_LSN. HRESULT: 0x%08x.
- 20240 — [Data Recovery][DbId: %d]: Data Recovery failed to read %ld bytes of blob fragment from blob handle for log record at %S_LSN. HRESULT: 0x%08x.
- 20241 — [Data Recovery][DbId: %d]: In Data Recovery, collected blob fragment size does not match the actual blob size for log record at %S_LSN. Expected %ld b…
- 20242 — [Data Recovery][DbId: %d]: A Data Recovery snapshot database named [%.*ls] already exists. Drop the existing snapshot database and retry the operation…
- 20243 — [Data Recovery]: Database [%.*ls] contains a logical file '%.*ls' that does not have a corresponding physical file defined.
- 20244 — [Data Recovery][DbId: %d]: The newly generated physical file '%.*ls' for Data Recovery snapshot database [%.*ls] already exists. Delete any unneeded s…
- 20245 — [Data Recovery][DbId: %d]: Data Recovery encountered a LOP_DELETE_ROWS log record with LCX_TEXT_MIX context at %S_LSN with an old data size larger tha…
- 20246 — [Data Recovery][DbId: %d]: Data Recovery encountered a LOP_BEGIN_XACT log at %S_LSN with a begin transaction local record time of %ls which is earlier…
- 20247 — [Data Recovery][DbId: %d]: Data Recovery encountered a LOP_COMMIT_XACT log at %S_LSN with a commit transaction local record time of %ls which is earli…
- 20248 — [Data Recovery][DbId: %d]: After encountering a LOP_INSERT_ROWS at %S_LSN marked with InsDel_ForUpdate, Data Recovery failed to see a LOP_DELETE_ROW w…
- 20249 — [Data Recovery]: %ls DDL operation is not supported while Data Recovery is enabled.
- 20250 — [Data Recovery]: Failed to load Data Recovery settings from the master database metadata.
- 20251 — [Data Recovery]: Failed to run Data Recovery for database [%.*ls] because the Data Recovery feature is disabled.
- 20252 — [Data Recovery]: Could not allocate memory for Data Recovery. Verify that SQL Server has sufficient memory.
- 20253 — [Data Recovery][DbId: %d]: Log Annotator did not see any LOP_MODIFY_ROW or LOP_DELETE_ROWS log records in blob update for log record at %S_LSN.
- 20254 — [Data Recovery][DbId: %d]: Encountered LOP_REPL_COMMAND log record at %S_LSN without REPLICATE flag which is unsupported.
- 20255 — [Data Recovery]: Cannot enable data recovery because at least one database has auto-shrink enabled (for example, '%ls'). Disable auto-shrink on all af…
- 20256 — [Data Recovery]: Unexpected chained forwarding stub encountered for database ID %d, page ID %d:%d, slot ID %d during forwarding stub resolution at LSN…
- 20257 — [Data Recovery]: Another data recovery session with session ID %d is active in this database.
- 20258 — [Data Recovery]: Cannot enable data recovery because database '%ls' has '%ls' enabled. Combining '%ls' with Data Recovery is currently not supported.
- 20259 — Cannot enable replication on database '%ls' because Data Recovery is enabled on this server. Combining replication (transactional or merge) with Data …
- 20260 — [Data Recovery]: Data recovery for forced failover completed for database ID %d in %I64u.%03I64u seconds. %I64u committed transaction(s) recovered wit…
- 20261 — LOB column partial update operations are not supported when data recovery is enabled. The .WRITE() method for varchar(max), nvarchar(max), and varbina…
- 20262 — [Data Recovery]: Skipping data recovery for database ID %d because the database is part of a Basic Availability Group, which does not support data rec…
- 20500 — The updatable Subscriber stored procedure '%s' does not exist.
- 20501 — Could not insert into sysarticleupdates using sp_articlecolumn.
- 20502 — Invalid '%s' value. Valid values are 'read only', 'sync tran', 'queued tran', or 'failover'.
- 20503 — Invalid '%s' value in '%s'. The publication is not enabled for '%s' updatable subscriptions.
- 20504 — Immediate Updating Subscriptions: The xml values inserted/updated by Subscriber will be replicated as NULL to publisher.
- 20505 — Could not drop synchronous update stored procedure '%s' in '%s'.
- 20506 — Source table '%s' not found in '%s'.
- 20507 — Table '%s' not found in '%s'.
- 20508 — Updatable subscriptions: The text, ntext, or image values inserted at the Subscriber will be NULL.
- 20509 — Updatable subscriptions: The text, ntext, or image values cannot be updated at the Subscriber.
- 20510 — Updateable Subscriptions: Cannot update identity columns.
- 20511 — Updateable Subscriptions: Cannot update timestamp columns.
- 20512 — Updateable Subscriptions: Rolling back transaction.
- 20513 — Database '%s' does not contain any replication metadata for a row whose ROWGUIDCOL matches the value specified for the @rowguid parameter of sp_showro…
- 20514 — A rowcount validation request has been submitted to heterogeneous publisher %s for article %s of publication %s. Validation results will be posted to …
- 20515 — Updateable Subscriptions: Rows do not match between Publisher and Subscriber. Run the Distribution Agent to refresh rows at the Subscriber.
- 20516 — Updateable Subscriptions: Replicated data is not updatable.
- 20518 — Updateable Subscriptions: INSERT and DELETE operations are not supported unless published table has a timestamp column.
- 20519 — Updateable Subscriptions: INSERT operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscr…
- 20520 — Updateable Subscriptions: UPDATE operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscr…
- 20521 — sp_MSmark_proc_norepl: must be a member of the db_owner or sysadmin roles.
- 20522 — sp_MSmark_proc_norepl: invalid object name '%s'.
- 20523 — Could not validate the article '%s'. It is not activated.
- 20524 — Table '%s' may be out of synchronization. Rowcounts (actual: %s, expected: %s). Rowcount method %d used (0 = Full, 1 = Fast).
- 20525 — Table '%s' might be out of synchronization. Rowcounts (actual: %s, expected %s). Checksum values (actual: %s, expected: %s).
- 20526 — Table '%s' passed rowcount (%s) validation. Rowcount method %d used (0 = Full, 1 = Fast).
- 20527 — Table '%s' passed rowcount (%s) and checksum validation. Checksum is not compared for any text or image columns.
- 20528 — Log Reader Agent startup message.
- 20529 — Starting agent.
- 20530 — Run agent.
- 20531 — Detect nonlogged agent shutdown.
- 20532 — Replication agent schedule.
- 20533 — Replication agents checkup
- 20534 — Detects replication agents that are not logging history actively.
- 20535 — Removes replication agent history from the distribution database.
- 20536 — Replication: agent failure
- 20537 — Replication: agent retry
- 20538 — Replication: expired subscription dropped
- 20539 — Replication Warning: %s (Threshold: %s)
- 20540 — Replication: agent success
- 20541 — Removes replicated transactions from the distribution database.
- 20542 — Detects and removes expired subscriptions from published databases or distribution databases.
- 20543 — @rowcount_only parameter must be the value 0,1, or 2. 0=7.0 compatible checksum. 1=only check rowcounts. 2=new checksum functionality introduced in ve…
- 20545 — Default agent profile
- 20546 — Verbose history agent profile.
- 20547 — Agent profile for detailed history logging.
- 20548 — Slow link agent profile.
- 20549 — Agent profile for low bandwidth connections.
- 20550 — Windows Synchronization Manager profile
- 20551 — Profile used by the Windows Synchronization Manager.
- 20552 — Could not clean up the distribution transaction tables.
- 20553 — Could not clean up the distribution history tables.
- 20554 — The replication agent has not logged a progress message in %ld minutes. This might indicate an unresponsive agent or high system activity. Verify that…
- 20555 — 6.x publication.
- 20556 — Heartbeats detected for all running replication agents.
- 20557 — Agent shutdown. For more information, see the SQL Server Agent job history for job '%s'.
- 20558 — Table '%s' passed full rowcount validation after failing the fast check. DBCC UPDATEUSAGE will be initiated automatically.
- 20559 — Conditional Fast Rowcount method requested without specifying an expected count. Fast method will be used.
- 20560 — An expected checksum value was passed, but checksums will not be compared because rowcount-only checking was requested.
- 20561 — Generated expected rowcount value of %s for %s.
- 20565 — Replication: Subscriber has failed data validation
- 20566 — Replication: Subscriber has passed data validation
- 20567 — Agent history clean up: %s
- 20568 — Distribution clean up: %s
- 20569 — Expired subscription clean up
- 20570 — Reinitialize subscriptions having data validation failures
- 20571 — Reinitializes all subscriptions that have data validation failures.
- 20572 — Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a validation failure.
- 20573 — Replication: Subscription reinitialized after validation failure
- 20574 — Subscriber '%s' subscription to article '%s' in publication '%s' failed data validation.
- 20575 — Subscriber '%s' subscription to article '%s' in publication '%s' passed data validation.
- 20576 — Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a synchronization failure.
- 20577 — No entries were found in msdb..sysreplicationalerts.
- 20578 — Replication: agent custom shutdown
- 20579 — Generated expected rowcount value of %s and expected checksum value of %s for %s.
- 20580 — Heartbeats not detected for some replication agents. The status of these agents have been changed to 'Failed'.
- 20581 — Cannot drop server '%s' because it is used as a Distributor in replication.
- 20582 — Cannot drop server '%s' because it is used as a Publisher in replication.
- 20583 — Cannot drop server '%s' because it is used as a Subscriber in replication.
- 20584 — Cannot drop server '%s' because it is used as a Subscriber to remote Publisher '%s' in replication.
- 20585 — Validation Failure. Object '%s' does not exist.
- 20586 — (default destination)
- 20587 — Invalid '%s' value for stored procedure '%s'.
- 20588 — The subscription is not initialized. Run the Distribution Agent first.
- 20589 — Agent profile for replicated queued transaction reader.
- 20590 — The article property 'status' cannot include bit 64, 'DTS horizontal partitions' because the publication does not allow data transformations.
- 20591 — Only 'DTS horizontal partitions' and 'no DTS horizontal partitions' are valid 'status' values because the publication allows data transformations.
- 20592 — 'dts horizontal partitions' and 'no dts horizontal partitions' are not valid 'status' values because the publication does not allow data transformatio…
- 20593 — Cannot modify publication '%s'. The sync_method cannot be changed to 'native', or 'concurrent' because the publication is enabled for heterogeneous su…
- 20594 — A push subscription to the publication exists. Use sp_subscription_cleanup to drop defunct push subscriptions.
- 20595 — Skipping error signaled.
- 20596 — Only '%s' or members of db_owner can drop the anonymous agent.
- 20597 — Dropped %d anonymous subscription(s).
- 20598 — The row was not found at the Subscriber when applying the replicated %S_MSG command for Table '%s' with Primary Key(s): %s
- 20599 — Continue on data consistency errors.
- 20600 — Agent profile for skipping data consistency errors. It can be used only by SQL Server Subscribers.
- 20601 — Invalid value specified for agent parameter 'SkipErrors'.
- 20602 — The value specified for agent parameter 'SkipErrors' is too long.
- 20603 — The agent profile cannot be used by heterogeneous Subscribers.
- 20604 — You do not have permissions to run agents for push subscriptions. Make sure that you specify the agent parameter 'SubscriptionType'.
- 20605 — Invalidated the existing snapshot of the publication. Run the Snapshot Agent again to generate a new snapshot.
- 20606 — Reinitialized subscription(s).
- 20607 — Cannot make the change because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force the change and invalidate the existing sn…
- 20608 — Cannot make the change because there are active subscriptions. Set @force_reinit_subscription to 1 to force the change and reinitialize the active sub…
- 20609 — Cannot attach subscription file '%s'. Make sure that it is a valid subscription copy file.
- 20610 — Cannot run '%s' when the Log Reader Agent is replicating the database.
- 20611 — Cannot add the article. Publications that allow transformable subscriptions with Data Transformation Services (DTS) can only include tables and indexe…
- 20612 — Checksum validation is not supported because the publication allows DTS. Use row count only validation.
- 20613 — Validation is not supported for articles that are set up for DTS horizontal partitions.
- 20614 — Validation is not supported for heterogeneous Subscribers.
- 20615 — Unable to add a heterogeneous subscription to the publication. The publication is not enabled for heterogeneous subscriptions.
- 20616 — High Volume Server-to-Server Profile
- 20617 — Merge agent profile optimized for the high volume server-to-server synchronization scenario.
- 20618 — You must have CREATE DATABASE permission to attach a subscription database.
- 20619 — Server user '%s' is not a valid user in database '%s'. Add the user account or 'guest' user account into the database first.
- 20620 — The security mode specified requires the server '%s' to be registered as a linked server. Use sp_addlinkedserver to add the server.
- 20621 — Cannot copy a subscription database to an existing database.
- 20622 — Replication database option 'sync with backup' cannot be set on the publishing database because the database is in Simple Recovery mode.
- 20623 — You cannot validate article '%s' unless you have 'SELECT ALL' permission on table '%s'.
- 20624 — The value specified for the @login parameter is not valid. User '%s' is not a user in database '%s'. Add the user account to the database before attem…
- 20625 — Cannot create the merge replication publication access list (PAL) database role for publication '%s'. This role is used by replication to control acce…
- 20626 — Filter '%s' already exists in publication '%s'. Specify a unique name for the @filtername parameter of sp_addmergefilter.
- 20627 — Partition id has to be greater than or equal to 0.
- 20628 — Failed to generate dynamic snapshot.
- 20629 — Failed to get partition id information.
- 20630 — Cannot create partitioned snapshot job. A job already exists for publication '%ls' that uses the values you specified for the @suser_sname and/or @hos…
- 20631 — Cannot find a location in which to generate a partitioned snapshot. Verify that the there is a valid snapshot folder specified for the publication. Th…
- 20632 — Failed to create a dynamic snapshot job to generate the dynamic snapshot.
- 20633 — Cannot start the partitioned snapshot job. Verify that SQL Server Agent is running on the Distributor.
- 20634 — The root publication information could not be found on the republisher.
- 20635 — A push subscription to '%ls' was found. Cannot add a pull subscription agent for a push subscription.
- 20636 — Cannot generate merge replication stored procedures for article '%s'. Stored procedures are generated on the Publisher when the Snapshot Agent runs or…
- 20637 — The article order specified in the @processing_order parameter of sp_addmergearticle does not reflect the primary key-foreign key relationships betwee…
- 20638 — Merge table articles do not support different values for the @source_object and @destination_object parameters of sp_addmergearticle. Either do not sp…
- 20639 — Cannot enable the publication to support non-SQL Server subscriptions because the publication is enabled for updatable subscriptions. To support non-S…
- 20640 — Cannot change enabled for heterogeneous subscriptions property while there are subscriptions to the publication.
- 20641 — Failed to check if the subset_filterclause has a dynamic function in it.
- 20642 — Cannot add article '%s' with one or more dynamic functions in the subset_filterclause '%s' to publication '%s' because the publication could have acti…
- 20643 — Cannot change the value of validate_subscriber_info for publication '%s' because the publication has active subscriptions. Set @force_reinit_subscript…
- 20644 — Invalid value "%s" specified for the parameter @identityrangemangementoption . Valid values are "auto", "manual", or "none".
- 20645 — The property "%s" cannot be modified for publications that are enabled for non-SQL Server subscriptions.
- 20646 — Peer-to-peer publications do not support %s. Change the value for parameter '%s'.
- 20647 — Cannot modify property '%s'. The publication is used in a peer-to-peer topology, which does not allow this property to be modified after the publicati…
- 20648 — An article already exists for table "%s" with a different value for the @delete_tracking property. The value must be the same for all publications in …
- 20649 — Publications enabled for heterogeneous subscriptions do not support %s. Please change the '%s' parameter value.
- 20650 — Cannot enable data definition language (DDL) replication (a value of "true" for the @replicate_ddl parameter) for publication "%s". This is because th…
- 20651 — Publication "%s" "%s". Therefore the compatibility level of the publication cannot be set to lower than %d. To set the compatibility level lower, disa…
- 20652 — Required metadata for publication '%s' could not be found in the sysmergeschemachange system table. Run the Snapshot Agent again.
- 20653 — Cannot have a dynamic snapshot job with both dynamic_filter_login and dynamic_filter_hostname being NULL.
- 20654 — Dynamic snapshots are only valid for merge publications.
- 20655 — The partitioned snapshot process cannot complete. Cannot retrieve the maximum timestamp information from the MSsnapshot_history table in the distribut…
- 20656 — The @subset_filterclause parameter cannot reference a computed column.
- 20657 — The value for the @pub_identity_range parameter must be a multiple of the increment for the identity column. The increment for table "%s" and identity…
- 20658 — The value for the @identity_range parameter must be a multiple of the increment for the identity column. The increment for table "%s" and identity col…
- 20659 — The value of IDENT_CURRENT ("%s") is greater than the value in the max_used column of the MSmerge_identity_range system table.
- 20660 — The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range .
- 20661 — The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @identity_range .
- 20662 — The republisher does not have a range of identity values from the root Publisher '%s' that it can assign to its Subscribers. Ensure that the republish…
- 20663 — The identity range allocation entry for the Publisher could not be found in the system table MSmerge_identity_range. Ensure that the value for the @id…
- 20664 — The Publisher cannot be assigned a new range of identity values, because the values for the identity column's data type have all been used. Change the…
- 20665 — The republisher does not have a range of identity values from the root Publisher that it can assign to its Subscribers. Run the Merge Agent to synchro…
- 20666 — Cannot refresh the identity range and/or the check constraint on the Publisher. Ensure the following: that the value in the identity column has not re…
- 20667 — Cannot allocate an identity range for article "%s". The article is not enabled for automatic identity range management.
- 20668 — Not enough range available to allocate a new range for a subscriber.
- 20669 — Object referenced by the given @article or @artid '%s' could not be found.
- 20670 — Cannot add, drop, or alter the identity range check constraint for table %s. This constraint is used by replication for automatic identity range manag…
- 20671 — Cannot find the identity range allocation entry for the Subscriber in the MSmerge_identity_range table. Reinitialize the subscription.
- 20672 — A value for the parameter @host_name was specified, but no articles in the publication use HOST_NAME() for parameterized filtering.
- 20673 — A value for the parameter @host_name was specified, but no articles in the publication use SUSER_SNAME() for parameterized filtering.
- 20674 — The publication does not use dynamic filtering.
- 20675 — The identity range values cannot be NULL.
- 20676 — Cannot refresh the Publisher identity range for article "%s". Execute the stored procedure sp_adjustpublisheridentityrange to refresh the identity ran…
- 20677 — Cannot add article "%s" with automatic identity range management. The article is already published in a transactional publication with automatic ident…
- 20678 — Could not find the regular snapshot job for the specified publication '%s'.
- 20679 — Cannot execute the stored procedure sp_adjustpublisheridentityrange on the current database because the database is a republisher or a Subscriber. To …
- 20680 — Failed to get metadata for a batch of rows.
- 20681 — Cannot specify a value of 1, 2, or 3 for the parameter @partition_options because publication "%s" has a compatibility level lower than 90RTM. Use the…
- 20682 — Failed deletion of rows in batched delete attempt on table %s.
- 20683 — Failed batched deletion on download only article %s.
- 20684 — Deleted more rows than expected in the batched delete attempt on table %s. Stop and restart the Merge Agent.
- 20685 — Cannot drop the filter '%s' . The filter specified for the @filtername parameter cannot be found.
- 20686 — Parameter '%s' cannot be NULL or empty when this procedure is run from a '%s' database.
- 20687 — Parameter '%s' must be NULL when this procedure is not being run from a '%s' database.
- 20688 — The tracer token ID (%d) could not be found for Publisher %s, database %s, publication %s. Use the stored procedure sp_helptracertokens to retrieve a …
- 20689 — The check for a Publisher needing a new identity range allocation failed on table %s. This check occurs every time the Merge Agent and Snapshot Agent …
- 20690 — Cannot set up the Publisher identity range for table %s. Verify that appropriate ranges were specified when the article was created, and then rerun th…
- 20691 — Merge replication upgrade of SQL Server 2005 metadata and triggers on the subscriber failed.
- 20692 — One or more rows to be inserted in the batch insert procedure for table %s were present in MSmerge_tombstone; merge replication cannot use batch inser…
- 20693 — One or more rows to be inserted in the batch insert procedure for table %s were present in MSmerge_contents; merge replication cannot use batch insert…
- 20694 — One or more rows to be updated for table %s contain changes in the column %s, which is used in one or more filters; merge replication cannot use batch…
- 20695 — Only %ld out of %ld rows were updated in the batched update procedure for table %s; other rows could not be updated because they have been deleted. No…
- 20696 — The object %s is marked as shipped by Microsoft (ms_shipped). It cannot be added as an article for merge replication.
- 20697 — Cannot drop article %s from publication %s. In this publication, this is the only article that uses a parameterized filter. Dropping this article chan…
- 20698 — A value for the parameter @host_name was not specified while publication uses HOST_NAME() for dynamic filtering.
- 20699 — A value for the parameter @suser_sname was not specified while publication uses SUSER_SNAME() for dynamic filtering.
- 20701 — The dynamic snapshot job schedule could not be changed on the distributor.
- 20702 — The dynamic snapshot job schedule could not be changed due to one or more errors.
- 20703 — One or more rows inserted in table '%s' were out of partition while the table was published with 'partition_options' set to %d.
- 20704 — The datatype of the identity column of table '%s' is tinyint. tinyint does not have enough numbers available for merge auto identity range. Change the…
- 20705 — Cannot set @conflict_logging to 'both' because publication '%s' has a compatibility level lower than 90. Set @publication_compatibility_level to '90RT…
- 20706 — The max or min allowed identity numbers for the identity column could not be found for the given article.
- 20707 — Failed to publish the article with identityrangemanagementoption set to 'auto' due to one or more errors.
- 20708 — An article is not allowed to be part of a logical record when it has a custom business logic resolver.
- 20709 — The merge process could not clean up the conflict table "%s" for publication "%s".
- 20710 — Incorrect identity range allocation was detected when logging identity range allocation information on the distributor for publisher '%s', publisher_d…
- 20711 — The dynamic filters property for publication '%s' has been incorrectly set. Use sp_changemergepublication to reset the value to true if the publicatio…
- 20712 — Unable to acquire the replication merge administrative application lock for database '%s'. This could be due an active snapshot running while the sche…
- 20713 — Replication merge admin stored procedure '%s' failed for publication '%s'. This could be due an active snapshot running while the admin proc was calle…
- 20714 — Failed to prepare article '%s' in publication '%s' for merge replication.
- 20715 — Failed to create merge replication triggers for object '%s'.
- 20716 — Failed to create publication views for merge replication publication '%s'.
- 20717 — sp_addmergelogsettings failed to add log settings. If log settings already exist for this subscription then use sp_changemergelogsettings to change th…
- 20718 — Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'. Use sp_addmergelogsettings to add the settings.
- 20719 — sp_changemergelogsettings failed to update log settings. Check the parameter values.
- 20720 — Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'.
- 20721 — sp_dropmergelogsettings failed to remove log settings.
- 20722 — '%s' failed. The value for parameter '%s' is not valid. Valid values are @support_options [0 - 5], @log_severity [1 - 4], @log_file_size [2,000,000 - …
- 20723 — Computed column "%s" can only be added to publication after its depending object "%s" is added.
- 20724 — Could not find a valid command line for the dynamic snapshot job with job_id '%s' for publication '%s'.
- 20725 — Unable to update the dynamic snapshot location for the dynamic snapshot job with job_id '%s' in publication '%s'.
- 20726 — Failed to change the dynamic snapshot location in one or more dynamic snapshot jobs for the given publication.
- 20727 — An invalid value was specified for parameter @subscription_type . Valid values are 'push', 'pull', 'both', 'anonymous' or 'all'.
- 20728 — Failed to restore the max allocated identity value for article '%s' in publication '%s'.
- 20729 — The max identity value allocation for article '%s' in publication '%s' could not be found on the distributor.
- 20730 — Setting @upload_first to 'true' requires the publication to be at publication_compatibility_level of '80RTM' or higher. Use sp_changemergepublication …
- 20731 — This edition of SQL Server does not support publications. Dropping existing publications.
- 20732 — Warning: Values of some of the flags specified in the 'schema_option' property are not compatible with the publication's compatibility level. The modi…
- 20733 — One or more rows updated in table '%s' were out of partition while the table was published with 'partition_options' set to %d.
- 20734 — One or more rows deleted in table '%s' were out of partition while the table was published with 'partition_options' set to %d.
- 20735 — Cannot add article '%s' to publication '%s'. The publication already contains 256 articles, which is the maximum.
- 20736 — Warning: Values of some of the flags specified in the 'schema_option' property are not compatible with the publication's compatibility level. The modi…
- 20737 — Warning: To allow replication of FILESTREAM data to perform optimally and reduce memory utilization, the 'stream_blob_columns' property has been set t…
- 20738 — Cannot add article '%s' with sparse column or column set to merge publication since merge replication does not support sparse columns and column set.
- 20739 — The DDL operation is not supported for article '%s'. If the column in the DDL operation is enabled for FILESTREAM or is of type hierarchyid, geometry,…
- 20800 — Cannot reinitialize the article '%s' in subscription '%s:%s' to publication '%s'. The publication is enabled for peer-to-peer transactional replicatio…
- 20801 — Cannot reinitialize the subscription. The publication is enabled for peer-to-peer transactional replication, which does not allow subscriptions to be …
- 20802 — Cannot publish objects from the replication administrative user schema [%s]. This schema owns all replication procedures and metadata tables, but it c…
- 20803 — Peer-To-Peer topologies require identical articles in publications at all nodes prior to synchronizing. Articles in publication [%s].[%s].[%s] do not …
- 20804 — Articles can only be included in a single peer-to-peer publication. [%s].[%s] is already included in the peer-to-peer publication '%s'.
- 20805 — Peer-to-peer topologies require identical publication names on each Publisher. You are attempting to republish object [%s].[%s] that is already being …
- 20806 — An error occurred while executing a peer-to-peer forwarding command. Contact Customer Support Services.
- 20807 — No peers were found for %s:%s:%s. If you encounter this error when executing the stored procedure sp_requestpeerresponse, verify that subscriptions ha…
- 20808 — The peer-to-peer publication '%s' does not exist. Execute sp_helppublication to view a list of publication names.
- 20809 — Peer-To-Peer topologies require identical publication names on each publisher. The distribution agent for publication [%s].[%s].[%s] is attempting to …
- 20810 — The specified source object must be a user-defined aggregate object if it is published as an 'aggregate schema only' type article.
- 20811 — Replication monitoring refresher for %s.
- 20812 — The specified source object must be a synonym if it is published as a 'synonym schema only' type article.
- 20813 — Only members of the sysadmin fixed server role can modify a %s that does not have a job with a proxy account defined.
- 20814 — Distribution Profile for OLEDB streaming
- 20815 — Distribution agent profile enabled for the processing LOB data using OLEDB streaming.
- 20816 — Peer-To-Peer publishers are only supported on Enterprise class editions of SQL Server. This instance is %s.
- 20817 — An error occurred during the execution of '%ls'. A call to '%ls' failed with error code: '%ld', return code: '%d'.
- 21000 — Cannot subscribe to an inactive publication.
- 21001 — Cannot add a Distribution Agent at the Subscriber for a push subscription.
- 21002 — The Distribution Agent for this subscription already exists (%s).
- 21003 — Changing publication names is no longer supported.
- 21004 — Cannot publish the database object '%s' because it is encrypted.
- 21005 — For backward compatibility, sp_addpublisher can be used to add a Publisher for this Distributor. However, sp_adddistpublisher is more flexible.
- 21006 — Cannot use sp_addpublisher to add a Publisher. Use sp_adddistpublisher.
- 21007 — Cannot add the remote Distributor. Make sure that the local server is configured as a Publisher at the Distributor.
- 21008 — Cannot uninstall the Distributor because there are Subscribers defined.
- 21009 — The specified filter procedure is already associated with a table.
- 21010 — Removed %ld replicated transactions consisting of %ld statements in %ld milliseconds (%ld rows/millisec).
- 21011 — Deactivated subscriptions.
- 21012 — Cannot change the 'allow_push' property of the publication to "false". There are push subscriptions on the publication.
- 21013 — Cannot change the 'allow_pull' property of the publication to "false". There are pull subscriptions on the publication.
- 21014 — The @optname parameter value must be 'transactional' or 'merge'.
- 21015 — The replication option '%s' has been set to TRUE already.
- 21016 — The replication option '%s' has been set to FALSE already.
- 21017 — Cannot perform SQL Server 7.0 compatible checksum operation on a merge article that has a vertical or horizontal partition. Rowcount validation and SQ…
- 21018 — There are too many consecutive snapshot transactions in the distribution database. Run the Log Reader Agent again or clean up the distribution databas…
- 21019 — Distribution agent for subscription added.
- 21020 — no comment specified.
- 21021 — Drop the Distributor before you uninstall replication.
- 21022 — If set 'immediate_sync' property of a publication to true then must also set 'independent_agent' property to true.
- 21023 — '%s' is no longer supported.
- 21024 — The stored procedure '%s' is already published as an incompatible type.
- 21025 — The string being encrypted cannot have null characters.
- 21026 — Cannot have an anonymous subscription on a publication that does not have an independent agent.
- 21027 — '%s' replication stored procedures are not installed. You must reinstall SQL Server with Replication.
- 21028 — Replication components are not installed on this server. Run SQL Server Setup again and select the option to install replication.
- 21029 — Cannot drop a push subscription entry at the Subscriber unless @drop_push is 'true'.
- 21030 — Names of SQL Server replication agents cannot be changed.
- 21031 — 'post_script' is not supported for stored procedure articles.
- 21032 — Could not subscribe because non-SQL Server Subscriber '%s' does not support 'sync tran' update mode.
- 21033 — Cannot drop server '%s' as Distribution Publisher because there are databases enabled for replication on that server.
- 21034 — Rows inserted or updated at the Subscriber cannot be outside the article partition.
- 21035 — You have updated the Publisher property '%s' successfully.
- 21036 — Another %s agent for the subscription or subscriptions is running, or the server is working on a previous request by the same agent.
- 21037 — Invalid working directory '%s'.
- 21038 — Integrated Authentication is not supported by the server.
- 21039 — The article '%s' contains the destination owner '%s'. Non-SQL Server Subscribers require articles to have the destination owner of NULL.
- 21040 — Publication '%s' does not exist.
- 21041 — A remote distribution Publisher is not allowed on this server version.
- 21042 — The distribution Publisher property, 'distributor_password', has no usage and is not supported for a Distributor running on Windows NT 4.0.
- 21043 — The Distributor is not installed.
- 21044 — Cannot ignore the remote Distributor (@ignore_remote_distributor cannot be 1) when enabling the database for publishing or merge publishing.
- 21045 — Cannot uninstall the Distributor because there are databases enabled for publishing or merge publishing.
- 21046 — Cannot change distribution Publisher property 'distribution_db' because the Publisher is using the current distribution database.
- 21047 — Cannot drop the local distribution Publisher because there are Subscribers defined.
- 21048 — Cannot add login '%s' to the publication access list because it does not have access to the distribution server '%s'.
- 21049 — The login '%s' does not have access permission on publication '%s' because it is not in the publication access list.
- 21050 — Only members of the sysadmin fixed server role or db_owner fixed database role can perform this operation. Contact an administrator with sufficient pe…
- 21051 — Could not subscribe because non-SQL Server Subscriber '%s' does not support custom stored procedures.
- 21052 — Cannot write to the message queue for the queued updating subscription. Ensure that Microsoft Distributed Transaction Coordinator is running, and that…
- 21053 — Input property parameter is not valid. See SQL Server Books Online for a list of valid parameters for sp_changemergepublication.
- 21054 — The trigger at the Subscriber could not execute commands at the Publisher over the linked server connection (triggers are used for Subscribers with up…
- 21055 — Invalid value for parameter %s specified for %s.
- 21056 — The subscription to publication '%s' has expired or does not exist.
- 21057 — Anonymous Subscribers cannot have updatable subscriptions.
- 21058 — An updatable subscription to publication '%s' on Subscriber '%s' already exists.
- 21059 — Cannot reinitialize subscriptions of non-immediate_sync publications.
- 21060 — Could not subscribe because non-SQL Server Subscriber '%s' does not support parameterized statements.
- 21061 — Invalid article status %d specified when adding article '%s'.
- 21062 — The row size of table '%s' exceeds the replication limit of 6,000 bytes.
- 21063 — Table '%s' cannot participate in updatable subscriptions because it is published for merge replication.
- 21064 — The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization. If using queued failover option, run Que…
- 21070 — This subscription does not support automatic reinitialization (subscribed with the 'no sync' option). To reinitialize this subscription, you must drop…
- 21071 — Cannot reinitialize article '%s' in subscription '%s:%s' to publication '%s' (subscribed with the 'no sync' option).
- 21072 — The subscription has not been synchronized within the maximum retention period or it has been dropped at the Publisher. You must reinitialize the subs…
- 21073 — The publication specified does not exist.
- 21074 — The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated.
- 21075 — The initial snapshot for publication '%s' is not yet available.
- 21076 — The initial snapshot for article '%s' is not yet available.
- 21077 — Deactivated initial snapshot for anonymous publication(s). New subscriptions must wait for the next scheduled snapshot.
- 21078 — Table '%s' does not exist in the Subscriber database.
- 21079 — The RPC security information for the Publisher is missing or invalid. Use sp_link_publication to specify it.
- 21080 — The 'msrepl_tran_version' column must be in the vertical partition of the article that is enabled for updatable subscriptions; it cannot be dropped.
- 21081 — Server setting 'Allow triggers to be fired which fire other triggers (nested triggers)' must exist on updatable Subscribers.
- 21082 — Database property 'IsRecursiveTriggersEnabled' has to be false for subscription databases at Subscribers that allow updatable subscriptions.
- 21083 — Database compatibility level at immediate updating Subscribers cannot be less than 70.
- 21084 — Publication '%s' does not allow anonymous subscriptions.
- 21085 — The retention period must be less than the retention period for the distribution database.
- 21086 — The retention period for the distribution database must be greater than the retention period of any existing non-merge publications.
- 21087 — Client subscriptions and anonymous subscriptions cannot republish data. To republish data from this database, the subscription to the root Publisher m…
- 21088 — The initial snapshot for the publication is not yet available.
- 21089 — Only members of the sysadmin fixed server role can perform this operation.
- 21090 — Cannot upgrade merge replication metadata. Attempt the upgrade again by running the Merge Agent for the Subscriber or by running the Snapshot Agent fo…
- 21091 — Global subscribers with priority 0 are not allowed to create merge publications.
- 21092 — The Change Tracking manual cleanup procedure for database %s has been executed
- 21093 — Only members of the sysadmin fixed server role or db_owner fixed database role or user with control db permission can perform this operation. Contact …
- 21094 — Distribution agent profile with id %d does not exist on this instance. If this instance is in an Availability group, sp_add_agent_profile should be ex…
- 21101 — The custom command name %s specified for parameter %s will be ignored. A system generated name will be used instead. The publication allows %s and com…
- 21105 — This edition of SQL Server cannot act as a Publisher or Distributor for replication.
- 21106 — This edition of SQL Server does not support publications.
- 21107 — '%ls' is not a table or view.
- 21108 — This edition of SQL Server does not support transactional publications.
- 21109 — The parameters @xact_seqno_start and @xact_seqno_end must be identical if @command_id is specified.
- 21110 — @xact_seqno_start and @publisher_database_id must be specified if @command_id is specified.
- 21111 — '%s' is not a valid parameter for the Snapshot Agent.
- 21112 — '%s' is not a valid parameter for the Log Reader Agent.
- 21113 — '%s' is not a valid parameter for the Distribution Agent.
- 21114 — '%s' is not a valid parameter for the Merge Agent.
- 21115 — %d is not a valid value for the '%s' parameter. The value must be a positive integer.
- 21116 — '%s' is not a valid value for the '%s' parameter. The value must be 1, 2, or 3.
- 21117 — '%s' is not a valid value for the '%s' parameter. The value must be 0, 1, or 2.
- 21118 — '%s' is not a valid value for the '%s' parameter. The value must be greater than or equal to 0 and less than or equal to 10,000.
- 21119 — %s is not a valid value for the '%s' parameter. The value must be a non-negative integer.
- 21120 — Only members of the sysadmin fixed server role or db_owner fixed database role, or the owner of the subscription can drop subscription '%s' to publica…
- 21121 — Only members of the sysadmin fixed server role and '%s' can drop the pull subscription to the publication '%s'.
- 21122 — Cannot drop the distribution database '%s' because it is currently in use.
- 21123 — The agent profile '%s' could not be found at the Distributor.
- 21124 — Cannot find the table name or the table owner corresponding to the alternative table ID(nickname) '%d' in sysmergearticles.
- 21125 — A table used in merge replication must have at least one non-computed column.
- 21126 — Pull subscriptions cannot be created in the same database as the publication.
- 21127 — Only global merge subscriptions can be added to database '%s'.
- 21128 — Terminating immediate updating or queued updating INSERT trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set …
- 21129 — Terminating immediate updating or queued updating UPDATE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set …
- 21130 — Terminating immediate updating or queued updating DELETE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set …
- 21131 — There are existing subscriptions to heterogeneous publication '%s'. To add new articles, first drop the existing subscriptions to the publication.
- 21132 — Cannot create transactional subscription to merge publication '%s'. The publication type should be either transactional(0) or snapshot(1) for this ope…
- 21133 — Publication '%s' is not enabled to use an independent agent.
- 21134 — The specified job ID must identify a Distribution Agent or a Merge Agent job.
- 21135 — Detected inconsistencies in the replication agent table. The specified job ID does not correspond to an entry in '%ls'.
- 21136 — Detected inconsistencies in the replication agent table. The specified job ID corresponds to multiple entries in '%ls'.
- 21137 — This procedure supports only remote execution of push subscription agents.
- 21138 — The 'offload_server' property cannot be the same as the Distributor name.
- 21139 — Could not determine the Subscriber name for distributed agent execution.
- 21140 — Agent execution cannot be distributed to a Subscriber that resides on the same server as the Distributor.
- 21141 — The @change_active flag may not be specified for articles with manual filters or views.
- 21142 — The SQL Server '%s' could not obtain Windows group membership information for login '%s'. Verify that the Windows account has access to the domain of …
- 21143 — The custom stored procedure schema option is invalid for a snapshot publication article.
- 21144 — Cannot subscribe to publication of sync_type 'dump database' because the Subscriber has subscriptions to other publications.
- 21145 — Cannot subscribe to publication %s because the Subscriber has a subscription to a publication of sync_type 'dump database'.
- 21146 — @use_ftp cannot be 'true' while @alt_snapshot_folder is neither NULL nor empty.
- 21147 — The '%s' database is not published for merge replication.
- 21148 — Both @subscriber and @subscriberdb must be specified with non-null values simultaneously, or both must be left unspecified.
- 21149 — The '%s' database is not published for transactional or snapshot replication.
- 21150 — Unable to determine the snapshot folder for the specified subscription because the specified Subscriber is not known to the Distributor.
- 21151 — Pre- and post-snapshot commands are not supported for a publication that may support non-SQL Server Subscribers by using the character-mode bcp as the…
- 21152 — Cannot create a subscription of sync_type 'none' to a publication using the 'concurrent' or 'concurrent_c' synchronization method.
- 21153 — Cannot create article '%s'. All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the …
- 21154 — Cannot change article '%s'. All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the …
- 21155 — Cannot change article '%s'. articles that are part of a concurrent synchronization publication can not have ins_cmd/del_cmd which exceeds %d character…
- 21156 — The @status parameter value must be 'initiated' or 'active'.
- 21157 — The snapshot compression option can be enabled only for a publication having an alternate snapshot generation folder defined.
- 21158 — For a publication to be enabled for the Internet, the 'ftp_address' property must not be null.
- 21159 — If a publication is enabled for the Internet, the 'alt_snapshot_folder' property must be non-empty.
- 21160 — The 'ftp_port' property must be a non-negative integer < 65536.
- 21161 — Could not change the Publisher because the subscription has been dropped. Use sp_subscription_cleanup to clean up the triggers.
- 21162 — It is invalid to exclude the rowguid column for the table from the partition.
- 21163 — It is not possible to add column '%s' to article '%s' because the snapshot for publication '%s' has been run.
- 21164 — Column '%s' cannot be included in a vertical partition because it is neither nullable nor defined with a default value.
- 21165 — Column '%s' cannot be excluded from a vertical partition because it is neither nullable nor defined with a default value.
- 21166 — Column '%s' does not exist.
- 21167 — The specified job ID does not represent a %s agent job for any push subscription in this database.
- 21168 — Only members of the sysadmin fixed server role, members of the db_owner fixed database role, and owners of subscriptions served by the specified repli…
- 21169 — Could not identify the Publisher '%s' at the Distributor '%s'. Make sure that the server '%s' is registered at the Distributor.
- 21170 — The specified Subscriber cannot use transformable subscriptions using Data Transformation Services. Only SQL Server 2000, SQL Server 2005, and OLE DB …
- 21171 — Could not find package '%s' in msdb at server '%s'.
- 21172 — The publication has to be in 'character', 'concurrent_c', or 'database snapshot character' bcp mode to allow DTS.
- 21173 — The publication has to be 'independent_agent type' to allow DTS.
- 21174 — Because this publication allows transformable subscriptions using DTS, it requires autogenerated stored procedures and parameterized commands, which a…
- 21175 — You cannot change the ins_cmd, upd_cmd, or del_cmd article properties because the publication allows Data Transformation Services or updatable subscri…
- 21176 — Only members of the sysadmin fixed server role, db_owner fixed database role, or the creator of the subscription can change the subscription propertie…
- 21177 — Could not create column list because it is too long. Create the list manually.
- 21178 — Data Transformation Services (DTS) properties cannot be set because the publication does not allow transformable subscriptions using DTS. To allow tra…
- 21179 — Invalid @dts_package_location parameter value. Valid options are 'Distributor' or 'Subscriber'.
- 21180 — A publication that allows DTS cannot be enabled for updatable subscriptions.
- 21181 — @dts_package_name can be set for push subscriptions only.
- 21182 — The @agent_type parameter must be one of 'distribution', 'merge', or NULL.
- 21183 — Invalid property name '%s'.
- 21184 — %s parameter is incorrect: it should be '%s', '%s' or '%s'.
- 21185 — The subscription is not initialized or not created for failover mode operations.
- 21186 — Subscription for Publisher '%s' does not have a valid queue_id.
- 21187 — The current mode is the same as the requested mode.
- 21188 — Changed update mode from [%s] to [%s].
- 21189 — The queue for this subscription with queue_id = '%s' is not empty. Run the Queue Reader Agent to make sure the queue is empty before setting mode from…
- 21190 — Overriding queue check for setting mode from [%s] to [%s].
- 21192 — MSrepl_tran_version column is a predefined column used for replication and can be only of data type uniqueidentifier
- 21193 — @identity_range , @pub_identity_range , or @threshold cannot be NULL when @identityrangemanagementoption is set to AUTO.
- 21194 — Cannot support identity range management because this table does not have an identity column.
- 21195 — A valid identity range is not available. Check the data type of the identity column.
- 21196 — Identity automation failed.
- 21197 — Failed to allocate new identity range.
- 21198 — Schema replication failed.
- 21199 — This change cannot take effect until you run the snapshot again.
- 21200 — Publication '%s' does not exist.
- 21201 — Dropping a column that is being used by a merge filter clause is not allowed.
- 21202 — It is not possible to drop column '%s' to article '%s' because the snapshot for publication '%s' has already been run.
- 21203 — Duplicate rows found in %s. Unique index not created.
- 21204 — The publication '%s' does not allow subscription copy or its subscription has not been synchronized.
- 21205 — The subscription cannot be attached because the publication does not allow subscription copies to synchronize changes.
- 21206 — Cannot resolve load hint for object %d because the object is not a user table.
- 21207 — Cannot find source object ID information for article %d.
- 21208 — This step failed because column '%s' exists in the vertical partition.
- 21209 — This step failed because column '%s' does not exist in the vertical partition.
- 21210 — The publication must be immediate_sync type to allow subscription copy.
- 21211 — The database is attached from a subscription copy file without using sp_attach_subscription. Drop the database and reattach it using sp_attach_subscri…
- 21212 — Cannot copy subscription. Only single file subscription databases are supported for this operation.
- 21213 — Subscribers cannot subscribe to publications that allow DTS without using a DTS package.
- 21214 — Cannot create file '%s' because it already exists.
- 21215 — An alternate synchronization partner can be configured only at the Publisher.
- 21216 — Publisher '%s', publisher database '%s', and publication '%s' are not valid synchronization partners.
- 21217 — Publication of '%s' data from Publisher '%s'.
- 21218 — The creation_script property cannot be NULL if a schema option of 0x0000000000000000 is specified for the article.
- 21219 — The specified source object must be a stored procedure object if it is published as a 'proc schema only' type article.
- 21220 — Unable to add the article '%s' because a snapshot has been generated for the publication '%s'.
- 21221 — The specified source object must be a view object if it is going to be as a 'view schema only' type article.
- 21222 — The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, 0x00001000, 0x00002000, 0x00…
- 21223 — The @pre_creation_command parameter for a schema only article must be either 'none' or 'drop'.
- 21224 — '%s' is not a valid property for a schema only article.
- 21225 — The 'offload_server' property cannot be NULL or empty if the pull subscription agent is to be enabled for remote activation.
- 21226 — The database '%s' does not have a pull subscription to the specified publication.
- 21227 — The 'offload_server' property cannot be the same as the Subscriber server name.
- 21228 — The specified source object must be a user-defined function object if it is going to be published as a 'func schema only' type article.
- 21229 — The schema options available for a view schema article are: 0x00000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, 0x00002000, 0x0004…
- 21230 — Do not call this stored procedure for schema change because the current database is not enabled for replication.
- 21231 — Automatic identity range support is useful only for publications that allow updating subscribers.
- 21232 — Identity range values must be positive integers that are greater than 1.
- 21233 — Threshold value must be from 1 through 100.
- 21234 — Cannot use the INSERT command because the table has an identity column. The insert custom stored procedure must be used to set 'identity_insert' setti…
- 21235 — Article property '%s' can be set only when the article uses automatic identity range management.
- 21236 — The subscription(s) to Publisher '%s' does not allow subscription copy or it has not been synchronized.
- 21237 — There is a push subscription to Publisher '%s'. Only pull and anonymous subscriptions can be copied.
- 21238 — This database either is a publisher, or there is a push subscription to publication '%s'. Only pull and anonymous subscriptions can be copied.
- 21239 — Cannot copy subscriptions because there is no synchronized subscription found in the database.
- 21240 — The table '%s' is already published as another article with a different automatic identity support option.
- 21241 — The threshold value should be from 1 through 100.
- 21242 — Conflict table for article '%s' could not be created successfully.
- 21243 — Publisher '%s', publication database '%s', and publication '%s' could not be added to the list of synchronization partners.
- 21244 — Character mode publication does not support vertical filtering when the base table does not support column-level tracking.
- 21245 — Table '%s' is not part of publication '%s'.
- 21246 — This step failed because table '%s' is not part of any publication.
- 21247 — Cannot create file at '%s'. Ensure the file path is valid.
- 21248 — Cannot attach subscription file '%s'. Ensure the file path is valid and the file is updatable.
- 21249 — OLE DB or ODBC Subscribers cannot subscribe to article '%s' in publication '%s' because the article has a timestamp column and the publication is 'all…
- 21250 — Primary key column '%s' cannot be excluded from a vertical partition.
- 21251 — Publisher '%s', publisher database '%s', publication '%s' could not be removed from the list of synchronization partners.
- 21252 — It is invalid to remove the default Publisher '%s', publication database '%s', and publication '%s' from the list of synchronization partners
- 21253 — Parameter '@add_to_active_directory' cannot be set to TRUE because Active Directory client package is not installed properly on the machine where SQL …
- 21254 — The Active Directory operation on publication '%s' could not be completed because Active Directory client package is not installed properly on the mac…
- 21255 — Column '%s' already exists in table '%s'.
- 21256 — A column used in filter clause '%s' either does not exist in the table '%s' or cannot be excluded from the current partition.
- 21257 — Invalid property '%s' for article '%s'.
- 21258 — You must first drop all existing merge publications to add an anonymous or local subscription to database '%s'.
- 21259 — Invalid property value '%s'. See SQL Server Books Online for a list of valid parameters for sp_changemergearticle.
- 21260 — Schema replication failed because database '%s' on server '%s' is not the original Publisher of table '%s'.
- 21261 — The offload server must be specified if the agent for this subscription is to be offloaded for remote execution.
- 21262 — Failed to drop column '%s' from the partition because a computed column is accessing it.
- 21263 — Parameter '%s' cannot be NULL or an empty string.
- 21264 — Column '%s' cannot be dropped from table '%s' because it is a primary key column.
- 21265 — Column '%s' cannot be dropped from table '%s' because there is a unique index accessing this column.
- 21266 — Cannot publish table '%s' for both a merge publication and a publication with the updatable subscribers option.
- 21267 — Invalid value for queue type was specified. Valid values = (%s).
- 21268 — Cannot change the parameter %s while there are subscriptions to the publication.
- 21269 — Cannot add a computed column or a timestamp column to a vertical partition for a character mode publication.
- 21270 — Queued snapshot publication property '%s' cannot have the value '%s'.
- 21272 — Cannot clean up the meta data for publication '%s' because other publications are using one or more articles in this publication.
- 21273 — You must upgrade the Subscriber to SQL Server 2000 to create updatable subscriptions when the Publisher is SQL Server 2000 or higher.
- 21274 — Invalid publication name '%s'.
- 21275 — Cannot publish the schema-bound view '%ls'. The value specified for the @type parameter must be "indexed view schema only" (for snapshot or transactio…
- 21276 — The type must be 'table' or '( view | indexed view | proc | func ) schema only'.
- 21277 — Cannot publish the source object '%ls'. The value specified for the @type parameter ("indexed view schema only" or "indexed view logbased") can be use…
- 21278 — Cannot publish the source object '%ls'. The value specified for the @type parameter ("indexed view logbased") requires that the view be schema bound w…
- 21279 — The 'schema_option' property for a merge article cannot be changed after a snapshot is generated for the publication. To change the 'schema_option' pr…
- 21280 — Publication '%s' cannot be subscribed to by Subscriber database '%s' because it contains one or more articles that have been subscribed to by the same…
- 21281 — Publication '%s' cannot be subscribed to by Subscriber database '%s' because it contains one or more articles that have been subscribed to by the same…
- 21282 — @identity_range , @pub_identity_range , and @threshold must be NULL when @identityrangemanagementoption is set to 'none' or 'manual'.
- 21283 — Column '%s' of table '%s' cannot be excluded from a vertical partition because there is a computed column that depends on it.
- 21284 — Failed to drop column '%s' from table '%s'.
- 21285 — Failed to add column '%s' to table '%s'.
- 21286 — Conflict table '%s' does not exist.
- 21287 — The specified @destination_folder is not a valid path of an existing folder.
- 21288 — Could not create the snapshot directory structure in the specified @destination_folder .
- 21289 — Either the snapshot files have not been generated or they have been cleaned up.
- 21290 — The identity range value provided has exceeded the maximum value allowed.
- 21291 — The specified automatic identity support parameters conflict with the settings in another article.
- 21292 — Object '%s' cannot be published twice in the same publication.
- 21293 — Warning: adding updatable subscription for article '%s' may cause data inconsistency as the source table is already subscribed to '%s'
- 21294 — Either @publisher (and @publisher_db) or @subscriber (and @subscriber_db) must be specified, but both cannot be specified.
- 21295 — Publication '%s' does not contain any article that uses automatic identity range management.
- 21296 — Parameter @resync_type must be either 0, 1, 2.
- 21297 — Invalid resync type. No validation has been performed for this subscription.
- 21298 — Failed to resynchronize this subscription.
- 21299 — Invalid Subscriber partition validation expression '%s'.
- 21300 — The resolver information was specified without specifying the resolver to be used for article '%s'. The default resolver will be used.
- 21301 — The resolver information should be specified while using the '%s' resolver.
- 21302 — The resolver information should specify a column with data type, datetime, or smalldatetime while using the '%s' resolver.
- 21303 — The article '%s' should enable column tracking to use the '%s' resolver. The default resolver will be used to resolve conflicts on this article.
- 21304 — The merge triggers could not be created on the table '%s'.
- 21305 — The schema change information could not be updated at the subscription database.
- 21306 — The copy of the subscription could not be made because the subscription to publication '%s' has expired.
- 21307 — The subscription could not be attached because the subscription to publication '%s' has expired.
- 21308 — Rowcount validation profile.
- 21309 — Profile used by the Merge Agent to perform rowcount validation.
- 21310 — Rowcount and checksum validation profile.
- 21311 — Profile used by the Merge Agent to perform rowcount and checksum validation.
- 21312 — Cannot change this publication property because there are active subscriptions to this publication.
- 21313 — Subscriber partition validation expression must be NULL for static publications.
- 21314 — There must be one and only one of '%s' and '%s' that is not NULL.
- 21315 — Failed to adjust Publisher identity range for table '%s'.
- 21316 — Failed to adjust Publisher identity range for publication '%s'.
- 21317 — A push subscription to the publication '%s' already exists. Use sp_mergesubscription_cleanup to drop defunct push subscriptions.
- 21318 — Table '%s' must have at least one column that is included in the vertical partition.
- 21319 — Could not find the Snapshot Agent command line for the specified publication. Check that a valid regular snapshot job exists on the distributor.
- 21320 — The version of the Distributor cannot be lower than the version of the Publisher.
- 21321 — The parameter @dynamic_snapshot_location cannot be an empty string.
- 21322 — This publication logs conflicts on both replicas. Pre-SQL Server 2005 subscribers will not honor this setting.
- 21323 — A dynamic snapshot job can be scheduled only for a publication with dynamic filtering enabled.
- 21324 — A Snapshot Agent must be added for the specified publication before a dynamic snapshot job can be scheduled.
- 21325 — Could not find the Snapshot Agent ID for the specified publication.
- 21326 — Could not find the dynamic snapshot job with a '%ls' of '%ls' for the specified publication.
- 21327 — '%ls' is not a valid dynamic snapshot job name.
- 21328 — The specified dynamic snapshot job name '%ls' is already in use. Try the operation again with a different job name.
- 21329 — Only one of the parameters, @dynamic_snapshot_jobid or @dynamic_snapshot_jobname , can be specified with a nondefault value.
- 21330 — Cannot create a sub-directory under the snapshot folder (%ls). Ensure that there is enough disk space available, and that the account under which the …
- 21331 — Cannot copy user script file to the snapshot folder at the Distributor (%ls). Ensure that there is enough disk space available, and that the account u…
- 21332 — Failed to retrieve information about the publication : %ls. Check the name again.
- 21333 — A generation that was expected to be in %s.dbo.MSmerge_genhistory could not be found. If this error occurred in a subscription database, reinitialize …
- 21334 — Cannot initialize Message Queuing-based subscription because the platform is not Message Queuing %s compliant
- 21335 — Warning: column '%s' already exists in the vertical partition.
- 21336 — Warning: column '%s' does not exist in the vertical partition.
- 21337 — Invalid @subscriber_type value. Valid options are 'local' and 'global'.
- 21338 — Cannot execute sp_dropmergearticle if the publication has a Subscriber that is running on a version of SQL Server 2000 or earlier. Drop and re-create …
- 21339 — Warning: the publication uses a feature that is only supported only by subscribers running '%s' or higher.
- 21340 — On Demand user script cannot be applied to the snapshot publication.
- 21341 — @dynamic_snapshot_location cannot be a non-empty string while @alt_snapshot_folder is neither empty nor null.
- 21342 — @dynamic_snapshot_location cannot be a non-empty string while @use_ftp is 'true'.
- 21343 — Could not find stored procedure '%s'.
- 21344 — Invalid value specified for %ls parameter.
- 21345 — Excluding the last column in the partition is not allowed.
- 21346 — Failed to change the owner of '%s' to '%s'.
- 21347 — Column '%s' cannot be excluded from the vertical partitioning because there is a unique index accessing this column.
- 21348 — Invalid property name '%s'.
- 21349 — Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because decentralized conflict logging …
- 21350 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because a compressed snapshot is used.
- 21351 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because vertical filters are being used.
- 21352 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because schema replication is performed.
- 21353 — Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide reinitializati…
- 21354 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because publication wide reinitialization is performe…
- 21355 — Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because merge metadata cleanup task is …
- 21356 — Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide validation tas…
- 21357 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because data types new in SQL Server 2000 exist in on…
- 21358 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because at least one timestamp column exists in one o…
- 21359 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because automatic identity ranges are being used.
- 21360 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because a new article has been added to the publicati…
- 21361 — The specified @agent_jobid is not a valid job id for a '%s' agent job.
- 21362 — Merge filter '%s' does not exist.
- 21363 — Failed to add publication '%s' to Active Directory. %s
- 21364 — Could not add article '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snap…
- 21365 — Could not add article '%s' because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reinitialize the active subsc…
- 21366 — Could not add filter '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snaps…
- 21367 — Could not add filter '%s' because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reinitialize the active subscr…
- 21368 — The specified offload server name contains the invalid character '%s'.
- 21369 — Could not remove publication '%s' from Active Directory.
- 21370 — The resync date specified '%s' is not a valid date.
- 21371 — Could not propagate the change on publication '%s' to Active Directory.
- 21372 — Cannot drop filter '%s' from publication '%s' because its snapshot has been run and this publication could have active subscriptions. Set @force_reini…
- 21373 — Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_re…
- 21374 — Upgrading distribution settings and system objects in database %s.
- 21375 — Upgrading publication settings and system objects in database %s.
- 21376 — Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_re…
- 21377 — Upgrading subscription settings and system objects in database %s.
- 21378 — Could not open distribution database %s because it is offline or being recovered. Replication settings and system objects could not be upgraded. Be su…
- 21379 — Cannot drop article '%s' from publication '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalida…
- 21380 — Cannot add timestamp column without forcing reinitialization. Set @force_reinit_subscription to 1 to force reinitialization.
- 21381 — Cannot add (drop) column to table '%s' because the table belongs to publication(s) with an active updatable subscription. Set @force_reinit_subscripti…
- 21382 — Cannot drop filter '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapsho…
- 21383 — Cannot enable a merge publication on this server because the working directory of its Distributors is not using a UNC path.
- 21384 — The specified subscription does not exist or has not been synchronized yet.
- 21385 — Snapshot failed to process publication '%s'. Possibly due to active schema change activity or new articles being added.
- 21386 — Schema change failed on object '%s'. Possibly due to active snapshot or other schema change activity.
- 21387 — The expanded dynamic snapshot view definition of one of the articles exceeds the system limit of 3499 characters. Consider using the default mechanism…
- 21388 — The concurrent snapshot for publication '%s' is not available because it has not been fully generated or the Log Reader Agent is not running to activa…
- 21389 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because column-level collation is scripted out with t…
- 21390 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because extended properties are scripted out with the…
- 21391 — Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because it contains schema-only articles.
- 21392 — Row filter(%s) is invalid for column partition(%s) for article '%s' in publication '%s'.
- 21393 — Dropping row filter(%s) for article '%s' in '%s'. Reissue sp_articlefilter and sp_articleview to create a row filter.
- 21394 — Invalid schema option specified for publication that allows updating subscribers. Need to set the schema option to include DRI constraints.
- 21395 — This column cannot be included in a transactional publication because the column ID is greater than 255.
- 21396 — The value specified for the @type parameter of sp_addsubscriber or the @subscriber_type parameter of sp_addsubscription is not valid. See SQL Server B…
- 21397 — The transactions required for synchronizing the nosync subscription created from the specified backup are unavailable at the Distributor. Retry the op…
- 21398 — Could not complete setting up the no-sync subscription at the Distributor while the distribution cleanup agent is running. The operation has a greater…
- 21399 — The transactions required for synchronizing the subscription with the specified log sequence number (LSN) are unavailable at the Distributor. Specify …
- 21400 — Article property must be changed at the original Publisher of article '%s'.
- 21401 — Article name cannot be 'all'.
- 21402 — Incorrect value for parameter '%s'.
- 21403 — The 'max_concurrent_dynamic_snapshots' publication property must be greater than or equal to zero.
- 21404 — '%s' is not a valid value for the '%s' parameter. The value must be a positive integer greater than 300 or 0.
- 21405 — '%s' is not a valid value for the '%s' parameter. The value must be an integer greater than or equal to %d.
- 21406 — '%s' is not a valid value for the '%s' parameter. The value must be 0 or 1.
- 21407 — Cannot create the subscription. If you specify a value of "initialize with backup" for the @sync_type parameter, you must subscribe to all articles in…
- 21408 — Cannot create the subscription. You must specify a value of "Active" or "Subscribed" for the @status parameter. This is because the value specified fo…
- 21409 — Only one of parameters %s and %s can be set.
- 21410 — Snapshot Agent startup message.
- 21411 — Distribution Agent startup message.
- 21412 — Merge Agent startup message.
- 21413 — Failed to acquire the application lock indicating the front of the queue.
- 21414 — Unexpected failure acquiring an application lock. Ensure that the account under which the Merge Agent runs is a member of the publication access list.…
- 21415 — Unexpected failure releasing an application lock. Ensure that the account under which the Merge Agent runs is a member of the publication access list.…
- 21416 — Property '%s' of article '%s' cannot be changed.
- 21417 — Having a queue timeout value of over 12 hours is not allowed.
- 21419 — Filter '%s' of article '%s' cannot be changed.
- 21420 — Subscription property '%s' cannot be changed.
- 21421 — Article '%s' cannot be dropped because there are other articles using it as a join article.
- 21422 — Queue Reader Agent startup message.
- 21423 — Either the publication '%s' does not exist or you do not have sufficient permissions to access it. Ensure that the publication exists and that the acc…
- 21424 — The @publisher parameter must be NULL for SQL Server publishers.
- 21425 — The @publisher parameter may not be NULL for heterogeneous publishers.
- 21426 — No shared agent subscription exists for publication '%s' and the subscriber/subscriber database pair '%s'/'%s'.
- 21428 — 'memory_optimized' property can be enabled only for SQL Server Subscriber.
- 21429 — Changing from sql subscriber to a non-sql subscriber is not allowed when the memory-optimized property is enabled.
- 21430 — The use of P2P Replication is not supported for subscription with memory-optimized tables.
- 21431 — Cannot add more %s agent in MI, number of continuous mode agents has hit limits of %d. Otherwise some agents may not running due to desktop heap used …
- 21432 — Cannot allow ReplDistpatcherUsers connect to NamePipe with error msg: %s
- 21450 — The replication %s could not be upgraded for %s databases. Ensure that %s is upgraded and execute %s again.
- 21451 — The %s %s (%s) login (%s) password has been changed.
- 21452 — Warning: The %s agent job has been implicitly created and will run under the SQL Server Agent Service Account.
- 21454 — The internal procedure sp_MStran_is_snapshot_required must be executed at the Distributor if the @run_at_distributor parameter has a value of 1. If th…
- 21456 — Value provided for parameter %s is not valid.
- 21460 — The primary key for source table "%s" includes the timestamp column "%s". Cannot create the article for the specified publication because it allows up…
- 21481 — Cannot create replication subscription(s) in the master database. Choose another database for creating subscriptions.
- 21482 — %s can only be executed in the "%s" database.
- 21484 — Article validation was requested for snapshot publication "%s". Article validation is only valid for transactional publications.
- 21485 — Tracer tokens cannot be posted for a snapshot publication.
- 21486 — An error occurred while logging the tracer token history information. The tracer token could not be posted.
- 21487 — An error occurred while inserting the tracer token to the log. The tracer token could not be posted.
- 21488 — No active subscriptions were found. The publication must have active subscriptions in order to post a tracer token.
- 21489 — A database '%s' already exists. If you intend this to be your distribution database set @existing_db = 1.
- 21490 — The value specified for the %s parameter of sp_mergearticlecolumn must be '%s'. A value of 'true' is allowed only when this procedure is called by ano…
- 21499 — The procedure %s failed to %s the resource %s. Server error = %d.
- 21500 — Invalid subscription type is specified. A subscription to publication '%s' already exists in the database with a different subscription type.
- 21501 — The supplied resolver information does not specify a valid column name to be used for conflict resolution by '%s'.
- 21502 — The publication '%s' does not allow the subscription to synchronize to an alternate synchronization partner.
- 21503 — Cleanup of merge meta data cannot be performed while merge processes are running. Retry this operation after the merge processes have completed.
- 21504 — Cleanup of merge meta data at republisher '%s'.'%s' could not be performed because merge processes are propagating changes to the republisher. All sub…
- 21505 — Changes to publication '%s' cannot be merged because it has been marked inactive.
- 21506 — sp_mergecompletecleanup cannot be executed before sp_mergepreparecleanup is executed. Use sp_mergepreparecleanup to initiate the first phase of merge …
- 21507 — All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final phase of merge meta data …
- 21508 — Cleanup of merge meta data cannot be performed while merge processes are running. Cleanup will proceed after the merge processes have completed.
- 21509 — Cleanup of merge meta data cannot be performed because some republishers have not quiesced their changes. Cleanup will proceed after all republishers …
- 21510 — Data changes are not allowed while cleanup of merge meta data is in progress.
- 21511 — Neither MSmerge_contents nor MSmerge_tombstone contain meta data for this row.
- 21512 — %ls: The %ls parameter is shorter than the minimum required size.
- 21514 — Cannot complete the requested operation in the subscription database because a snapshot is currently being delivered to the database. Perform the oper…
- 21515 — Replication custom procedures will not be scripted because the specified publication '%s' is a snapshot publication.
- 21516 — Transactional replication custom procedures for publication '%s' from database '%s':
- 21517 — Replication custom procedures will not be scripted for article '%s' because the auto-generate custom procedures schema option is not enabled.
- 21518 — Replication custom procedures for article '%s':
- 21519 — Custom procedures will not be scripted for article update commands based on direct INSERT, UPDATE, or DELETE statements.
- 21520 — Custom procedure will not be scripted because '%s' is not a recognized article update command syntax.
- 21521 — Some generation values are above the upper limit of %d used in SQL Server 2000. Change the publication_compatibility_level of the publication to 90 to…
- 21522 — This article cannot use the '%s' feature because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publica…
- 21523 — Adding column '%s' to table '%s' failed. Articles can have at most %d columns, including columns that have been filtered.
- 21525 — A lightweight replica must be anonymous.
- 21526 — Article '%s' already belongs to a subscription with a different value for the @lightweight property.
- 21527 — Publication '%s' cannot be added to database '%s', because a publication with a lower compatibility level already exists. All merge publications in a …
- 21528 — Publication '%s' cannot be added to database '%s', because a publication with a higher compatibility level already exists. All merge publications in a…
- 21530 — The schema change failed during execution of an internal replication procedure. For corrective action, see the other error messages that accompany thi…
- 21531 — The data definition language (DDL) command cannot be executed at the Subscriber. DDL commands can only be executed at the Publisher. In a republishing…
- 21532 — Cannot add a data definition language trigger for replicating '%.*ls' events.
- 21533 — Cannot insert information into the schema change tracking table sysmergeschemachange.
- 21535 — The article '%s' is already published in another publication, and is set to use nonoverlapping partitions with multiple subscribers per partition (@pa…
- 21537 — The column '%s' in table '%s' is involved in a foreign key relationship with a column in table '%s', but this column was not found in the specified jo…
- 21538 — Table '%s' cannot have table '%s' as a parent in a logical record relationship because it already has a different parent table. A logical record relat…
- 21539 — A logical record relationship, specified by the @filter_type parameter, requires a one-to-one or a one-to-many join from the parent table to the child…
- 21540 — You cannot drop a column defined as data type uniqueidentifier with the rowguidcol property because merge replication uses this column for tracking. T…
- 21541 — Cannot complete ALTER TABLE command. Do not execute the command 'ALTER TABLE table_name DISABLE TRIGGER ALL' on a published table. Reissue multiple 'A…
- 21542 — Encountered server error %d while executing <%s>.
- 21543 — The schema for the article %s was either not generated properly or was not applied properly during initial synchronization. This may be due to permiss…
- 21544 — Value specified for the publication property replicate_ddl is not valid. The value must be 1 or 0.
- 21545 — You cannot disable a trigger used by merge replication on a published table. To drop the trigger, drop the table from the publication.
- 21546 — Cannot replicate the ALTER TABLE command. It contains multiple DROP commands, including a DROP command for a column that is not included in all subscr…
- 21547 — Encountered server error %d while restoring the log for database %s.
- 21548 — Cannot execute sp_change_subscription_properties. This stored procedure can only be used for publications that have at least one pull subscription.
- 21549 — Cannot add the computed column '%s' to the publication. You must first add all columns on which this column depends; you cannot filter any of these co…
- 21550 — Before you drop the column from the publication, all computed columns that depend on column '%s' must be dropped.
- 21551 — Only members of the sysadmin or db_owner or db_ddladmin roles can perform this operation.
- 21552 — Merge data definition language (DDL) error: Dropping a column used in a row filter or a join filter is not allowed. To drop a column used in a row fil…
- 21553 — '%s' must be a valid Active Directory login in the form 'DOMAIN\Login' or 'Login@DOMAIN' for SQL Server on Linux. See the documentation for '%s'.
- 21561 — The value specified for parameter %s = %d is not valid.
- 21564 — The table %s contains the column msrepl_tran_version, which is used by replication. The column is set to NULL, but it must be set to NOT NULL. Replica…
- 21567 — The call format VCALL cannot be used for the specified article. VCALL format can be used only for articles in publications that allow updating subscri…
- 21569 — The article %s in the publication %s does not have a valid conflict table entry in the system table sysarticleupdates. This entry is required for publ…
- 21570 — Cannot create the logical record relationship. Table '%s' does not have a foreign key referencing table '%s'. A logical record relationship requires a…
- 21571 — Cannot create the logical record relationship in publication '%s'. The use_partition_groups option for the publication must be set to "true" in order …
- 21572 — Cannot add a logical record relationship because the foreign key constraint '%s' on table '%s' is disabled. To create the logical record relationship,…
- 21573 — Cannot add a logical record relationship because the foreign key constraint '%s' on table '%s' is defined with the NOT FOR REPLICATION option. To add …
- 21574 — Cannot add a logical record relationship because the article '%s' is published in publication '%s', which has a compatibility level lower than 90RTM. …
- 21575 — The value specified for the property filter_type is not valid. Valid values are 1 (join filter only), 2 (logical record relation only), and 3 (join fi…
- 21576 — Cannot add a logical record relationship between tables '%s' and '%s' because the foreign key column '%s' in table '%s' allows NULL values. Alter the …
- 21578 — In order to use partition_options of 2 (non overlapping partitions with multiple subscriptions per partition) or 3 (non overlapping partitions one sub…
- 21579 — Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping pa…
- 21580 — Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping pa…
- 21581 — Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping pa…
- 21582 — Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping pa…
- 21583 — Cannot update the column in article '%s'. The article has a value of 2 or 3 (nonoverlapping partitions) for the partition_options property, and the co…
- 21584 — Cannot insert the row for article '%s'. The row does not belong to the Subscriber's partition, and the article has a value of 2 or 3 (nonoverlapping p…
- 21585 — Cannot specify custom article ordering in publication '%s' because the publication has a compatibility level lower than 90RTM. Use sp_changemergepubli…
- 21596 — Cannot execute the stored procedure '%s' because it is not a Microsoft-shipped system object. Merge replication only executes Microsoft-shipped genera…
- 21597 — The article includes only the rowguidcol column. You must publish at least one other column.
- 21598 — Modifying DDL triggers created by replication is disallowed since these are required to track DDL changes.
- 21599 — The parameters @article and @join_articlename cannot have the same value. Specify different articles for the two parameters; self-joins are not permit…
- 21600 — Non-SQL Server Publisher [%s] cannot be found. Execute sp_helpdistpublishers to view a list of available Publishers.
- 21601 — The value of the parameter @type must be 'logbased' for Oracle publications.
- 21603 — The refresh of Oracle publisher '%s' by sp_refresh_heterogeneous_publisher was not successful. The Oracle publisher meta data has been retained in its…
- 21604 — The non-SQL Server Publisher vendor is not valid. Attempt to add the Publisher again. If the problem persists, contact Microsoft Customer Support Serv…
- 21605 — Non-SQL Server Publishers must be configured in the context of the distribution database. Execute sp_adddistpublisher in the context of the distributi…
- 21606 — Parameter "%s" is for non-SQL Server Publishers only. The value of this parameter must be "%s" for a SQL Server Publisher.
- 21607 — sp_refresh_heterogeneous_publisher was unable to obtain publisher information for Oracle publisher '%s'. sp_refresh_heterogeneous_publisher may only b…
- 21608 — Cannot use a value of TRUE for the parameter @ignore_distributor . The value must be FALSE for a non-SQL Server Publisher.
- 21609 — Non-SQL Server publications do not support updatable subscriptions. The properties allow_sync_tran and allow_queued_tran must be "false".
- 21610 — The failed attempt by sp_refresh_heterogeneous_publisher to refresh publisher '%s' did not alter any meta data at the Oracle publisher. Make certain t…
- 21611 — Cannot drop the distribution Publisher "%s" because it has publications defined. Drop the publications first.
- 21612 — For non-SQL Server Publishers, the value of the @sync_method parameter must be "character" or "concurrent_c".
- 21613 — Constraint column '%s' not found in table '%s'.
- 21614 — Index column '%s' not found in table '%s',
- 21615 — Unable to find table information for article %s. Local distributor cache may be corrupt.
- 21616 — Cannot find column [%s] in the article. Verify that the column exists in the underlying table, and that it is included in the article.
- 21617 — Unable to run SQL*PLUS. Make certain that a current version of the Oracle client code is installed at the distributor. For addition information, see S…
- 21618 — The Publisher '%s' does not exist. To view a list of Publishers, use the stored procedure sp_helpdistpublisher.
- 21619 — Must provide both @SelectColumnList and @InsColumnList .
- 21620 — The version of SQL*PLUS that is accessible through the system Path variable is not current enough to support Oracle publishing. Make certain that a cu…
- 21621 — Unable to create the public synonym %s. Verify that the replication administrative user has been granted the CREATE SYNONYM permission.
- 21622 — Unable to grant SELECT permission on the public synonym %s. Verify that the replication administrative user has sufficient permissions.
- 21623 — Unable to update the public synonym 'MSSQLSERVERDISTRIBUTOR' to mark Oracle instance '%s' as a SQL Server publisher.
- 21624 — Unable to locate the registered Oracle OLEDB provider, OraOLEDB.Oracle, at distributor '%s'. Make certain that a current version of the Oracle OLEDB p…
- 21625 — Unable to update the publisher table HREPL_PUBLISHER at the Oracle instance '%s'.
- 21626 — Unable to connect to Oracle database server '%s' using the Oracle OLEDB provider OraOLEDB.Oracle. For addition information, see SQL Server Error 21626…
- 21627 — Unable to connect to Oracle database server '%s' using the Microsoft OLEDB provider MSDAORA. For addition information, see SQL Server Error 21627 in T…
- 21628 — Unable to update the registry of distributor '%s' to allow Oracle OLEDB provider OraOLEDB.Oracle to run in process with SQL Server. Make certain that …
- 21629 — The CLSID registry key indicating that the Oracle OLEDB Provider for Oracle, OraOLEDB.Oracle, has been registered is not present at the distributor. M…
- 21630 — Unable to determine whether the table '%s' is still being published. Contact Customer Support Services.
- 21631 — Cannot unpublish table '%s'; the remote call to the Oracle Publisher failed. Verify that the replication administrative user login can connect to the …
- 21632 — The parameter %s is not supported for non-SQL Server publications. The value specified for this parameter must be %s.
- 21633 — The publication '%s' could not be added because non-SQL Server Publishers only support the @sync_method parameter values "character" or "concurrent_c"…
- 21634 — The parameter %s does not support the value '%s' when using non-SQL Server publications. The value must be %s.
- 21635 — An unsupported schema option combination was specified. Non-SQL Server publications only support the following schema options: 0x01, 0x02, 0x10, 0x40,…
- 21637 — %s is required for heterogeneous publications.
- 21638 — You have specified a value of '%s' for the @repl_freq parameter of sp_addpublication. For non-SQL Server publications, this requires one of the follow…
- 21639 — Heterogeneous publishers can not use trusted connections, set @trusted to false.
- 21640 — Non-SQL Server Publishers do not support a value of 1 for the parameter @thirdparty_flag . When executing the stored procedure sp_adddistpublisher, sp…
- 21641 — The "%s" parameter is for non-SQL Server Publishers only. It must be NULL for SQL Server Publishers.
- 21642 — Heterogeneous publishers require a linked server. A linked server named '%s' already exists. Please remove linked server or choose a different publish…
- 21643 — The value specified for the parameter '%s' must be MSSQLSERVER, ORACLE, or ORACLE GATEWAY.
- 21644 — %s value of '%s' is not supported for heterogeneous subscribers, must be %s.
- 21645 — The value '%s' is not a valid non-SQL Server Publisher type. For SQL Server 2005, the value must be ORACLE or ORACLE GATEWAY.
- 21646 — The Oracle server [%s] is already defined as the Publisher [%s] on the Distributor [%s].[%s]. Drop the Publisher or drop the public synonym [%s].
- 21647 — The Oracle Publisher support package could not be loaded. Drop the replication administrative user schema and re-create it; ensure it is granted the d…
- 21649 — Cannot change the property '%s'. Non-SQL Server Publishers do not support this property.
- 21650 — The value specified for @rowcount_only for the article '%s' is not 1. For an article in a publication from a non-SQL Server Publisher, 1 is the only v…
- 21651 — Failed to execute the HREPL.%s request to Oracle Publisher '%s'. Verify that the Oracle package code exists on the Publisher, and that the replication…
- 21653 — The database management system (DBMS) %s %s does not exist. Verify the supported DBMS and versions by querying msdb.dbo.MSdbms.
- 21654 — The data type %s does not exist. Verify the supported data types and mappings by querying msdb.dbo.sysdatatypemappings.
- 21655 — The data type %s already exists.
- 21656 — The data type mapping for %s does not exist. Verify the list of available mappings by querying msdb.dbo.sysdatatypemappings.
- 21657 — The data type mapping for %s already exists.