It looks like that's possibly an on-Prem solution. We're in the Cloud. The oddest thing is we have several failures - fine, time to reauthenticate, right? But some allowed me to do that and others did not. This one really has me stumped.
I don't see a place to clear settings in the Cloud. I'll check with our partners, and we may have to escalate to Qlik in a ticket. Thanks!
Update: The issue has been resolved, although the original cause remains unclear.
During troubleshooting we attempted creating a new connection and testing with a different user account, but neither resolved the problem. The successful fix occurred when our partner edited the existing data connection and reauthenticated it using the service account credentials.
Our current theory is that reauthentication from a different environment/network forced Qlik to refresh the connection state, which had not been updating previously. It appears the authentication was created, it tested fine, but Qlik was not saving it at the update/edit screen.
It looks like that's possibly an on-Prem solution. We're in the Cloud. The oddest thing is we have several failures - fine, time to reauthenticate, right? But some allowed me to do that and others did not. This one really has me stumped.
I don't see a place to clear settings in the Cloud. I'll check with our partners, and we may have to escalate to Qlik in a ticket. Thanks!
Update: The issue has been resolved, although the original cause remains unclear.
During troubleshooting we attempted creating a new connection and testing with a different user account, but neither resolved the problem. The successful fix occurred when our partner edited the existing data connection and reauthenticated it using the service account credentials.
Our current theory is that reauthentication from a different environment/network forced Qlik to refresh the connection state, which had not been updating previously. It appears the authentication was created, it tested fine, but Qlik was not saving it at the update/edit screen.
