If the above fails, then clearing manually the queue might be the last option.
For more information, see You can fail over from immediate to queued updating at any time.
After you do, however, you cannot return to immediate updating until the Subscriber and Publisher are connected and the Queue Reader Agent has applied all pending messages in the queue to the Publisher.
We recommend that you use peer-to-peer transactional replication instead.
However, I just can't find the replication type Transactional publication with updatable subscriptions on the publication type page in SQL Server 2012, see the image below: Anyone can confirm, whether we have this feature in SQL Server 2012?
The following conflicts can occur: When creating a publication and enabling queued updating, replication adds a uniqueidentifier column (msrepl_tran_version) with the default of newid() to the underlying table.
When published data is changed at either the Publisher or the Subscriber, the row receives a new globally unique identifier (GUID) to indicate that a new row version exists.Quickest way to do this is to use CRXDE Lite ( and delete the node: /var/eventing/jobs/assigned/%INSTANCE-SLING-ID%/%REPLICATION-AGENT-FULL-ID% So for example with the default publish agent: /var/eventing/jobs/assigned/e23dd09d-83f1-4735-a77c-394df479214c/cq.publish Note this is considered as an exceptional workaround action In versions of AEM 5.4 and earlier, replication queues can sometimes be polluted by entries that cannot be removed through the OOTB Clear Queue link.In this case, you can use the Replication Queue Cleaning tool attached here.This topic describes how to switch between update modes for an updatable transaction subscription in SQL Server 2017 by using SQL Server Management Studio or Transact-SQL.Specify the mode for updatable subscriptions using the New Subscription Wizard.For information about setting the mode when using this wizard, see View and Modify Pull Subscription Properties.