SQL Server Connection Broken

[matthewharrison]

Overnight, our Qlik Cloud connection to our local SQL Server has broken, yet we have not changed any networking or infrastructure settings.  No one has edited the SQL server connection settings in months.  Our production environment is currently unable to load new data.

We are running SQL Server 2016 on a Windows Server 2012 R2 VM.  We are using the built in SQL Server connection in Qlik Cloud and this has worked for months with no problems.
The error we are receiving is : error [08001] [qlik][sqlserver] problem establishing connection to the server.

What we have done so far:

We have doublechecked that the IP addresses in this article are properly whitelisted. https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Introduction/qlik-cloud-...

We have verified that other outside integrations are successfully using the same credentials as Qlik Cloud, so this is not a password/credential issue.

We have updated the server to TLS 1.2 per the recommendation of this article and have confirmed that this has taken effect. https://community.qlik.com/t5/Official-Support-Articles/Outdated-out-of-support-versions-of-Microsof...

Any guidance on troubleshooting or insight into possible changes that have been made on the product side are greatly appreciated.  Thank you.

[matthewharrison · Accepted solution]

While we still suspect that the issues arise from TLS support mentioned in this article https://community.qlik.com/t5/Official-Support-Articles/Outdated-out-of-support-versions-of-Microsof... , we solved this issue by standing up an entirely new DW server.  Instead of Windows Server 2012 R2, it is Windows Datacenter 2022 and instead of SQL Server 2016, it is SQL Server 2019.  We were planning to do this anyway in the coming months.  Whether related to TLS or otherwise, this has fixed the issue.

[Bolijay00]

Any solution, i was wondering if it was a glitch from us , have you emailed support

[matthewharrison]

We have worked closely with a technical team from support over several days.  Their language seems to imply that this was an unintended consequence of backend changes made at Qlik.  After speaking with us, a partner from Qlik posted that our above "fix" is now "Qlik's support solution".  https://community.qlik.com/t5/Support-Updates/Qlik-Cloud-Analytics-will-no-longer-function-with-outd...

Qlik seems to be aware of the issue and working on it, but have not supplied us with any timeframe on a possible fix.  Our team is continuing on with the full SQL Server migration mentioned above due to business urgency.