Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT
cancel
Showing results for 
Search instead for 
Did you mean: 
AKV0524
Contributor III
Contributor III

Qlik Replicate SQL Server error - The semaphore timeout period has expired.

Hi Team,

 

We are running CDC task and connecting to SQL Server (MS-CDC) but sometime we observed that cdc job disconnect for a minute and then connect again to SQL server with error :[Microsoft][SQL Server Native Client 11.0]TCP Provider: The semaphore timeout period has expired.

 

is there any way can we apply something in internal parameter for timeout issue.

 

Attaching error screenshot

 

Thanks

Amit

5 Replies
john_wang
Support
Support

Hello @AKV0524 ,

Thanks for reaching out to Qlik Community!

I'm not sure what's the Qlik Replicate version you are running now however the Native Client 11 is not support for long time. For example in Qlik Replicate 2023.11, the certified version is Microsoft ODBC Driver 18.1

BTW, please let us know the SQL Server server version, it's helpful to understand the environment.

Hope this helps.

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
AKV0524
Contributor III
Contributor III
Author

Hi John,

Currently we have 2022 May Replicate version which have ODBC Driver 11 FOR SQL SERVER 2014 version installed in the replicate server and connected to Microsoft SQL Server 14.00.3465 source database.

 

Thanks

Amit

Heinvandenheuvel
Specialist II
Specialist II

This is a generic network layer message where Replicate is 99.99% sure to merely be the messenger and have no control over the cause. Best Replicate can do is retry- did it?

You may want to google for "[Microsoft][SQL Server Native Client 11.0]TCP Provider: The semaphore timeout period has expired."

It could be a physical hardware issue, or some overly smart network switch trying to 'help'.

Is this a highly active session or a slow/infrequent actions? IN the latter case you may want to specifically look for tcpKeepalive style options and settings on servers / network interfaces / switches 

 Good luck.

Hein.

john_wang
Support
Support

Hello @AKV0524 ,

Totally agree with @Heinvandenheuvel .

You may troubleshoot the connectivity issue by using ODBC Manager, or 3rd ODBC Test Tool. If the DSN is accessible then Qlik Replicate should work. BTW, in Qlik Replicate 2022.5, the certified driver version is Microsoft ODBC Driver 17.6

Good Luck,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
SushilKumar
Support
Support

Hello team,

 

If our response has been helpful, please consider clicking "Accept as Solution". This will assist other users in easily finding the answer.

 

Regards,

Sushil Kumar