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

Trying to establish connection with Azure SQL

  • Cannot connect to SQL Server.
  • SYS,GENERAL_EXCEPTION,Cannot connect to SQL Server,RetCode: SQL_ERROR SqlState: 08001 NativeError: 26 Message: [Microsoft][ODBC Driver 18 for SQL Server]Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server

 

Qlik Replicate IP has been whitelisted in SQL server.

2 Replies
DesmondWOO
Support

Hi @chandraprakash_j_volvo ,

Could you try other tools to test the connection? On Windows platform, you may test the connection by defining the ODBC DSN. On Linux platform, you may use e.g. isql to test.

Regards,
Desmond

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

Hello @chandraprakash_j_volvo 

This error message indicates that there is an issue with establishing a connection to the Azure SQL Server using the Microsoft ODBC Driver version 18. The error message provides some potential causes for the problem:

1.) Please make sure you meet the prerequisites as per the User guide.


2.) Server too busy or resource limitations: The SQL Server might be experiencing high load or resource limitations, such as memory constraints or reaching the maximum allowed connections. In such cases, you may need to investigate the server's resource usage and make adjustments as necessary to handle the incoming connections.


Check server resources: Ensure that the SQL Server has sufficient resources available (CPU, memory, disk space) to handle new connections. If the server is running low on resources, consider optimizing queries, adding more resources, or limiting connections as needed.

Check for network issues: The error message suggests that the problem occurred during the handshake before login. It's possible that there might be network issues causing the connection problem. Check if the client can reach the SQL Server, and make sure there are no firewall or network configuration issues blocking the connection.

Test with other tools: Attempt to connect to the Azure SQL Server using other tools or methods to isolate if the issue is specific to the ODBC driver or more general.

If you have tried these steps and are still encountering the issue, it may be helpful to review the server and application logs for more detailed error information. Additionally, consulting with your database administrator or IT support team can also be beneficial in troubleshooting and resolving this type of connection problem.

 

Regards,

Suresh