Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Independent validation for trusted, AI-ready data integration. See why IDC named Qlik a Leader: Read the Excerpt!
cancel
Showing results for 
Search instead for 
Did you mean: 
craigbence
Contributor III
Contributor III

Qlik Sense Patch Causes Data Connections to load very slowly in Load Editor

We recently updated our Qlik Sense version to Qlik_Sense_update_Feb2024_Patch4. Now, each time we access the Load Editor in an application in our Personal Work Stream, takes roughly 2-3 minutes to load the Data Connections. Prior to the patch, these Data Connections would display within seconds. While the Data Connections are loading, the editor is basically at a standstill. 

Has anyone experienced this behavior? Any recommendations on how to correct this situation would be appreciated!!

38 Replies
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @henrikalmen @mikaelsc @Tool_Tip @salshute @shaun_lombard 

We have active investigations ongoing about the May 2025 patch 5 performance degradation, though how related they are, I am not sure. I'm looking into finding out more for you.

All the best,
Sonja

Don't forget to Like posts and use the "Accept as Solution" button on content that answered your question! Thanks 🙂
salshute
Partner - Contributor III
Partner - Contributor III

Thanks for the suggestion. I have taken your advice and it has resolved the issue for me for now.

Sonja_Bauernfeind
Digital Support
Digital Support

Hello everyone, 

After digging a little on our end: @henrikalmen, would it be possible for you to log a support ticket on this? Include a QSR DB backup.

We haven't found a ticket specific to this topic and need one so we can engage RnD properly. 

As for @mikaelsc and @Tool_Tip and @shaun_lombard: If you still have your environment up, could you test Henrik's solution? If it does not help, I've been asked to request a support ticket that includes a QSR DB backup (to allow us to see the volume of data connections and complexity of rules governing them).

Any cases you log for this, please send me the number in direct messages.

All the best,
Sonja

Don't forget to Like posts and use the "Accept as Solution" button on content that answered your question! Thanks 🙂
henrikalmen
Specialist II
Specialist II

I submitted a case and DM:ed you the case number.

SivenM2020
Partner - Contributor III
Partner - Contributor III

Hi,

We are also experiencing the same issue at a customer. QlikSense was upgraded from May2024 to May2025sr5 this past weekend, and data connections are very slow.

thumbnail_image.png

hugo_andrade
Partner - Specialist
Partner - Specialist

@SivenM2020 ,

In the past, this was caused because the Server had restricted access to the internet.

Do you know if this is the case? Perhaps a change was overwritten on the config files.

This procedure helped on this behavior: https://community.qlik.com/t5/Official-Support-Articles/Long-term-offline-use-for-Qlik-Sense-and-Qli... 

Please give it a try and let us know, ok?

Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

SivenM2020
Partner - Contributor III
Partner - Contributor III

Hi,

Central and Rim nodes has internet access.

hugo_andrade
Partner - Specialist
Partner - Specialist

Got it. Are you able to try implementing that change to see the result?

As a troubleshooting step, I would give it a try if possible.

Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

SivenM2020
Partner - Contributor III
Partner - Contributor III

This is an enterprise environment with 14000 pro licenses. Not a place to test changes.

We will need a definitive solution from Qlik.

henrikalmen
Specialist II
Specialist II

In my opinion, it's obvious that there is some kind of error related to the QvSapConnectorPackage. Until Qlik resolves this issue (support case has been submitted) I recommend trying to remove that connector (unless it is needed, of course) from all nodes. I didn't even have to restart the qlik services. It "solved" the problem for us.