For example, this issue occurs in the following scenario:
- You publish a table in a transactional publication, and then you set the @allow_drop property to True.
- You remove the published table.
- Before the Log Reader agent processes the records that are related to the drop table command, you clean up the obsolete article by using one the following stored procedures:
The process could not execute 'sp_MSadd_replcmds' on 'SQL_SERVER_INSTANCE'.
Repl Agent Status: 6
Status: 0, code: 1007, text: 'The remote server "(null)" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.'.
Status: 4, code: 6001, text: 'Background thread for 'Command Loader' is exiting.'.
Status: 0, code: 22020, text: 'Batches were not committed to the Distributor.'.
Status: 0, code: 22037, text: 'The last step did not log any message!'.
Note Drop table support (DROP TABLE DDL) was added in SQL Server 2014 Service Pack 2. For information about drop table support, see the following article in the Microsoft Knowledge Base:
Article ID: 3184227 - Last Review: Sep 22, 2016 - Revision: 1