SQL Server Errors or Failures from Error: 21746 to Error: 21765
Error: 21746, Severity: 16, The ‘%s’ character length must not exceed %d.
Error: 21747, Severity: 16, Cannot establish a connection to the Oracle Publisher ‘%s’. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS.
Error: 21748, Severity: 16, The article was dropped at the Distributor, but information at the Publisher ‘%s’ was not dropped. No action is required; the information is cleaned up if the Publisher is dropped.
Error: 21749, Severity: 16, The Publisher was dropped at the Distributor, but information on the Publisher ‘%s’ was not dropped. Connect to the Oracle Publisher with SQL*PLUS and
drop the replication administrative user.
Error: 21750, Severity: 16, The table %s does not have a primary key, which is required for transactional replication. Create a primary key on the table.
Error: 21751, Severity: 16, Cannot publish view %s as a table because it does not have a unique clustered index. Publish the view as a view, or add a unique clustered index.
Error: 21752, Severity: 16, The current user %s does not have SELECT permission on the table %s. The user must have SELECT permission to retrieve rows at the Subscriber that
have updates pending in the queue.
Error: 21753, Severity: 16, The table %s, which is specified in the @tablename parameter of sp_getqueuedrows, is not part of any active initialized queued subscription. Ensure your queued subscriptions are properly initialized by running the Snapshot Agent, Distribution Agent, and Q
Error: 21754, Severity: 16, Processing has been terminated. The resultset for sp_getqueuedrows is larger than 16,000, the maximum size that the procedure can return. Run the Queue Reader Agent to flush the queue at the Subscriber before executing this procedure again.
Error: 21755, Severity: 16, Failed to mark ‘%s’ as a system object.
Error: 21756, Severity: 16, Based on article settings, table %s should have an identity column, but it does not have one. Verify article settings with sp_helparticle and change them if necessary with sp_changearticle.
Error: 21757, Severity: 16, The subscription is read-only. The publication that this subscription synchronizes with allows updates at the Subscriber, but a value of ‘read-only’ was specified for the @update_mode parameter of sp_addsubscription. To allow updates, you must drop and th
Error: 21758, Severity: 16, Cannot find a valid Queue Reader Agent ID for the subscription to Publisher %s, database %s, publication %s. The specified subscription to an updating Subscriber publication is not initialized. Run the Snapshot Agent, Distribution Agent, and Queue Reader
Error: 21759, Severity: 16, Cannot add the column ‘%s’ to the table ‘%s’. The table already contains the maximum number of columns allowed for an article in a merge publication (246 columns).
Error: 21760, Severity: 11, Cannot execute the replication script in the ‘master’ database; the current session will be terminated. The script must be executed in the distribution database, and the master database cannot serve as the distribution database.
Error: 21761, Severity: 20, Cannot execute the replication script; the current session will be terminated. Check for any errors returned by SQL Server during execution of the script.
Error: 21762, Severity: 10, The distribution database ‘%s’ has a compatibility level of %d, which is different from that of the master database. The two compatibility levels must be the same, so the distribution database level is being changed to %d. This is an informational message
Error: 21763, Severity: 16, Message Queuing Service is not running. Start this service and retry the operation.
Error: 21764, Severity: 16, Cannot create the publication. Specifying a value of ‘msmq’ for the parameter @queue_type is supported only on Microsoft Windows NT platforms. Specify a value of ‘sql’ for this parameter.
Error: 21765, Severity: 10, The column msrepl_tran_version has been predefined and allows NULLs. This column will be dropped and recreated to not allow NULLs for updating subscribers.
This is applicable on below versions of SQL Server
SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.