topic Re: Qlik replicate comm link failure in logs in Qlik Replicate

Qlik replicate comm link failure in logs

HVPR — Tue, 12 Jul 2022 19:24:09 GMT

Can someone help with this error popping up in the logs for a full load task. unable to find what the issue is.

[TARGET_LOAD ]E: RetCode: SQL_ERROR SqlState: 08S01 NativeError: 0 Message: [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure [1022502] (ar_odbc_conn.c:2029)
[TARGET_LOAD ]E: Failed to get table qlik.ods_lcm_prdct definition [1022506] (odbc_util.c:994)
[TARGET_LOAD ]E: Endpoint is disconnected [1020414] (endpointshell.c:3971)
[TARGET_LOAD ]E: Error executing data handler [1020414] (streamcomponent.c:1998)
[TASK_MANAGER ]E: Stream component failed at subtask 20, component st_20_Test - TxnlData [1020414] (subtask.c:1396)
[TARGET_LOAD ]E: Stream component 'st_20_Test - TxnlData' terminated [1020414] (subtask.c:1565)
[SOURCE_UNLOAD ]I: Unload finished for segment #17 of segmented table 'ODS'.'ODS_LCM_PRDCT' (Id = 22). 806854 rows sent. (streamcomponent.c:3674)

Re: Qlik replicate comm link failure in logs

shashi_holla — Tue, 12 Jul 2022 19:28:35 GMT

Hi @HVPR

Looks like the connection cannot be established, couple of messages in the log which shows that:

"Communication link failure"

"Endpoint is disconnected"

Can you please test the endpoint connection and check if you get green checkbox.

Thank you,

Re: Qlik replicate comm link failure in logs

HVPR — Tue, 12 Jul 2022 19:34:53 GMT

Hi Shashi,,Thanks for the reply.

Yes endpoint test connection was successfull. This task runs for a while and throws this error in the logs. and the state of the task is confusing (attached image) and the stop task will not be available for couple days. Its something like got stuck somewhere.

Re: Qlik replicate comm link failure in logs

Michael_Litz — Tue, 12 Jul 2022 19:35:28 GMT

Hi @HVPR ,

Please let us know what the exact version of replicate you are running.

Also can you please increase logging for components Communication & Target_Load to Trace, then zip and attach the resulting task log the next time this error happens? I am hoping with the additional logging that it will give us a direction toward the root cause.

Thanks,
Michael

Re: Qlik replicate comm link failure in logs

shashi_holla — Tue, 12 Jul 2022 19:43:10 GMT

Based on the screenshot task is still trying to start but unable to. Does it have many tables or just qlik.ods_lcm_prdct?

If there are other tables then let's try remove qlik.ods_lcm_prdct and see if it's able to start.

Thank you,

Re: Qlik replicate comm link failure in logs

HVPR — Tue, 12 Jul 2022 20:22:33 GMT

It has other tables too. and the other tables have the same error.

as you asked will increase the logging and will attach the logs here.

Re: Qlik replicate comm link failure in logs

Bill_Steinagle — Thu, 14 Jul 2022 15:04:58 GMT

Hello,

Thank you for the post on the Replicate Forums. I would also suggest have the Target DB check the DB system logs to see why the connection was disconnected as this appears to be from the DB closing the connection. The DB system logs would also give some more details as to why the disconnected the session/thread for the Replicate Task writing to this Target DB.

Using SQL Management Studio you can click on View and Registered Servers DB Engine and the DB Shown in the List can right click and View SQL Server Log

The right click on the DB and View SQL Server Log

Check the logs at the time shown from the Replicate Log to help determine root cause from the Target DB. Hope this information is also helpful to your post.

Thanks!

Bill

Re: Qlik replicate comm link failure in logs

lyka — Fri, 15 Jul 2022 17:46:18 GMT

Hello,

I've seen this happen when there is a network error usually related to TCP/IP errors. Did the task failed with a fatal error or it recovered?

When we see these types of connection closed messages the culprit can sometimes be a router or firewall closing what appears to be an inactive TCP/IP connection. Since Replicate will open many connections, some of those connection may not be used for a long time, like schema changes.

You can try this:

The first thing we suggest is to modify the Replicate server and set the TCP/IP Keep Alive.

Add the following dword keys and the specified decimal values:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpWindowSize=256000

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\GlobalMaxTcpWindowSize=16777216

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveInterval=1000

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime=60000

Thanks

Lyka