Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
alex_rosu
Contributor III
Contributor III

Qlik Sense Apps fail to reload with "Access credentials are not valid for this connection."

Hello everyone,

We are currently facing this type of issue with one of the Azure SQL Databases:

Error: Connector reply error: Unable to connect to database:
Error message:
Please check the values for Username‚ Password‚ Host and other properties.
Description: Client unable to establish connection

However, this error is intermittent, it fails only sometimes. I manually tested the connection from the Data load editor and we have for example 3 consecutive successful tests and the 4th fails with this error. The same thing happens when the app is triggered, it fails from time to time.

What could be the root cause?

How can we investigate this?

Thank you in advance.

Labels (1)
1 Solution

Accepted Solutions
Francisco_Fernandez

Hello @alex_rosu ,

That's a generic error message and there might be multiple root causes.

I would start by checking the "Resource health" in azure where it shows if the database availability, within the resource health page there are some Azure resources to troubleshoot.

Francisco_Fernandez_0-1644307032641.png

Checking the Azure's firewall is also recommended.

You can also increase the logging level on the logs. It will probably show more information about the problem.

https://help.qlik.com/en-US/connectors/Subsystems/ODBC_connector_help/Content/Connectors_ODBC/ODBC-l...

 

Best regards,

Francisco

View solution in original post

1 Reply
Francisco_Fernandez

Hello @alex_rosu ,

That's a generic error message and there might be multiple root causes.

I would start by checking the "Resource health" in azure where it shows if the database availability, within the resource health page there are some Azure resources to troubleshoot.

Francisco_Fernandez_0-1644307032641.png

Checking the Azure's firewall is also recommended.

You can also increase the logging level on the logs. It will probably show more information about the problem.

https://help.qlik.com/en-US/connectors/Subsystems/ODBC_connector_help/Content/Connectors_ODBC/ODBC-l...

 

Best regards,

Francisco