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

[Sonja_Bauernfeind]

A Qlik Sense app fails to reload with the following error in the script log: 

Error: Connector reply error: Unable to connect to database: 
Error message: 
Please check the values for Username‚ Password‚ Host and other properties. 
Description: Access credentials are not valid for this connection. 

Even though the same error may be registered for other issues, in most cases this is due to the user account used in the connection or incorrect credentials.

Resolution:

Verify the user configured in the connection is granted the proper permissions, is enabled, and the password is correctly typed.

Environment:

Qlik Sense Enterprise on Windows 

[Sonja_Bauernfeind]

Hello @ricardoValadez 

The error message documented in this article refers to credentials being incorrect when Qlik Sense attempts to load from a data source. This can be any source (MySQL, etc). The solution is to verify the credentials (username and password) used when setting up the data connection.

All the best,
Sonja 

[adicostar_TP]

I can see that the resolution is quite generic and it doesn't help anyone.

We started to have this problem on a new QlikSense Server. There are no issue with the credentials. They work fine on the other Qlik server.

Also it is not a database related issue because, we have the same issue on connections to SQL Server and on an Oracle connection.

After getting the error we just re-input the credentials and it starts working again but they stop working  again after a day or two.

Our error is below:

"The following error occurred:

Connector reply error: Connection failed: Please check the values for Username‚ Password‚ Host and other properties."

[Sonja_Bauernfeind]

Hello @adicostar_TP 

I've reviewed previous instances of this error with similar behaviour (re-run of reload, re-entering of credentials) and customers had success with reviewing their database side logs to give them additional insight, such as network connectivity errors or database-specific error codes. 

Qlik, in this instance, only reports back the error it is returned itself.

Another instance I found was a setup with multiple nodes, in which it depended on which node established the connection whether or not it succeeded, with a DNS issue being the root cause.

If the database logs do not help you further, I recommend posting this query directly in our forums where you can benefit from out active community and engineers monitoring the situation (as this will require investigation which we cannot do in an article).

The best forum is: Connectivity Forum.

Make sure to include Sense version, setup details, and errors that you have found.

All the best,
Sonja