Skip to main content
Announcements
UPGRADE ADVISORY for Qlik Replicate 2024.5: Read More
cancel
Showing results for 
Search instead for 
Did you mean: 
ramu123
Contributor III
Contributor III

In qlik replicate, Unable to connect to source database(MS sql server):- SYS-E-HTTPFAIL, Failed to connect. SYS,GENERAL_EXCEPTION,Failed to connect,Re

Hi All,

I would like to change my qlik replicate connection to  source database(MS sql server), but I'm unable to connect to source database and I'm getting this error message. I tried with other test and pre-prod environments but I'm getting same error.

SYS-E-HTTPFAIL, Failed to connect.
SYS,GENERAL_EXCEPTION,Failed to connect,RetCode: SQL_ERROR SqlState: 08001 NativeError: 258 Message: [Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: The wait operation timed out.

 

Could you please share your suggestions

Thanks

Ramu

Labels (1)
7 Replies
Steve_Nguyen
Support
Support

@ramu123 where is the Replicate server, on a windows server or Linux server ?

on the Replicate server, outside of Replicate are you able to connect to the SQL server ?

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!
ramu123
Contributor III
Contributor III
Author

Hi Steve,

After Vnet peering is done, I'm able to connect to source DB. Thanks for your suggestion.

 

Thanks

Ramu 

MoeE
Partner - Creator III
Partner - Creator III

Hi Ramu,

We are experiencing the same issue. Can you by any chance elaborate on what was done to fix the issue?

Regards,

Mohammed

john_wang
Support
Support

Hello Mohammed, @MoeE 

Not sure what's the Replicate version and SQL Server version, however I do not think ODBC Driver 17 is a better one, we support ODBC Driver 18 (please check UG for detailed version number).

BTW, how about the 64-bit ODBC DSN, does it work? 

thanks,

John.

 

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

Hi @MoeE 

It looks like the issue was due to networking reasons and Ramu fixe it by allowing the Replicate Server VM and SQL Server VM to talk to each other.

Thanks

Kent

*** Greetings from Down Under ***
MoeE
Partner - Creator III
Partner - Creator III

Hi @Kent_Feng@john_wang,

For informational purposes in case someone has this issue in the future. Our case was due to the connection string being incorrect for a high availability cluster. Also, double check that your user still has the necessary permissions in each DB/node in the cluster.

Regards,

Mohammmed

john_wang
Support
Support

Thank you so much for your amazing support! Mohammed @MoeE 

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