-
Title
Capture on MS SQL Server source error out with Error Capture: [SP-COM01006] Exception Only one Log Reader Agent or log-related procedure -
Description
Capture stops due to Error [SP-COM01006] Exception : ::SQLExecDirect SQL_ERROR:[42000] [Microsoft][ODBC SQL Server
Event_log:
Error 2018-03-28 16:49:01.116000 1332 1816 Capture: [SP-COM01006] Exception : ::SQLExecDirect SQL_ERROR:[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure.(18752) query: EXEC sp_replcmds 1000. An exception has occurred. Contact Technical Support. See 'http://advice.shareplex.com/SP-COM01006' for additional advice and support. (capturing from r.splexdb2100) [module cap]Capture log:
capture 2018-03-28 16:49:01.116000 1332 1816 SQL_ERROR:[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. -
Cause
The SQL Server SERVERPROPERTY('server') is returning a server name in lowercase . The ' -Publisher []' in the command column has the server name in uppercase. SharePlex activation matches these two server names values in order to shutdown the native log reader process that is automatically invoked by SQL Server when native replication is enabled. This issue will be addressed in a future SharePlex release above version 9.1 through SPO-13202
-
Resolution
Workaround 1: (Preferred )
Disable "SQL Server Agent" in Object Explorer (right click on it, and select "Stop").
Workaround 2:
Disable the native log reader manually using sp_delete_job.
This requires running the query below to get the job ID, and would need to be executed after each SharePlex activation (so this methed isn't recommended). Example : EXEC msdb.dbo.sp_delete_job @job_id='4288338B-57A0-454D-B5EA-A96DD49214BF'
Workaround 3:
Find out how to configure SQL Server so that SERVERPROPERTY('servername') returns uppercase hostnames
-
Defect ID
SPO-13202