Recoverable Errors on replicate tasks

[Naga_vivek]

 Hi Team ,

we observed these recoverable errors in each of our Qlik replicate tasks but the tasks are in running state after getting these errors.

Can any one explain what are these errors about. Will there be any impact on the running task. Will there be any data loss .

Error 1 (Task 1)

ERRO-R_GENERAL "Encountered connection problems with the source endpoint.
SqlStat: 08S01 NativeError:64 [Microsoft][SQL Server Native Client 11.0]TCP Provider: The specified network name is no longer available.
(PcbMsg: 108)"

Error 2 (Task 2)

 WARNING_GENERAL Task '<Task name>' encountered a recoverable error
 ERROR_GENERAL "Stream component src_DB' terminated
Stream component failed at subtask 0, component src_DB
Error executing source loop"
 ERROR_GENERAL "Encountered an unexpeceted error. Aborting...
mssql_execute_log_lsn_peeper(...) failed upon SQLExecute with LSN parameters '<LSN>'"

Please let us know if these will effect the existing tasks and the below errors are anyway related to upgrade.

Note : we observed these errors at the same time in different replicate tasks.

Thanks

N Vivek

[Heinvandenheuvel]

These are (Network!) issues external to Replicate and have no relation to an upgrade.

Check with your network folks.

For desperate cases you may be able to set up a test tasks independent of Replicate which uses light query to the source DB every minute or 5 to potentially 'catch' instability.

Hein.

[john_wang]

Hello @Naga_vivek ,

Besides @Heinvandenheuvel comment, SQL Server Native Client 11 is not official support long time ago, if you've upgrade Replicate to supported versions, please install the corresponding support Microsoft ODBC versions, eg Microsoft ODBC Driver 18.1. Please restart Replicate Services after the ODBC Driver installation.

Hope this helps.

John.

[DesmondWOO]

Hi @Naga_vivek ,

For the ERROR 1, it should be network issue.

For the ERROR 2, Replicate encountered an error while it was getting changes from the SQL Server. It could be network issue, but you may check the task log whether timeout error occurred before.

In general, Replicate should retry when it encounters these errors. You can check task log for details.

Regards,
Desmond