Data Connections Pane Takes 3 Minutes to Load and Web Connectors Are Missing in Create New Connection

[fabdulazeez]

We are facing an issue in Qlik Sense Enterprise on Windows (May 2025 Patch 17) where the Data Connections panel keeps spinning for 3 minutes after opening the data load editor. When it loads webconnectors and webstorage connectors are missing in the create new connection window .Below error is displayed in web console

connector: error executing connector method getConnectionInfo, retrying: QvWebConnectorPackage.exe undefined
connector: error executing connector method getConnectionInfo, retrying: QvWebStorageProviderConnectorPackage.exe undefined

In the custom connector logs C:\ProgramData\Qlik\Custom Data\QvWebConnectorPackage\Log  below is displayed 

09 Jun 2026 11:44:16,488 [1] - ERROR - PipeName=command_1437881e13dd5ca493b8ad2efc37aecd044f4d40 Source=QWC ReloadId=NA TenantId=NA UserIdType=NA UserId=NA EngineSessionId=NA AppId=NA RequestGuid=NA ConnectorId=NA Sender=Program Message=Unhandled exception.
APIConnectorInterfaces.Exceptions.QwcException: Could not get key with id prefix 'qseow_tmp' ---> System.Security.Cryptography.CryptographicException: Key not valid for use in specified state.

at System.Security.Cryptography.ProtectedData.Unprotect(Byte[] encryptedData, Byte[] optionalEntropy, DataProtectionScope scope)
at Qlik.Connectors.WebPackage.Startup.KeyProvider.ReadKey(String keyFilePath, Byte[] entropy)
at Qlik.Connectors.WebPackage.Startup.KeyProvider.GetKeyInternal(Boolean autoCreate)
--- End of inner exception stack trace ---
at Qlik.Connectors.WebPackage.Startup.KeyProvider.GetKeyInternal(Boolean autoCreate)
at Qlik.Connectors.WebPackage.Startup.ProductServices_QSEoW.Init(KeyState keyState, Boolean isWebStorageProvider)
at QvWebConnectorPackage.Program.Main(String[] args)

The same error is also observed for QvWebStorageProviderConnectorPackage

Has anyone encountered this issue before?

Admin has force updated Service account password recently.
All Qlik services were restarted with the new password.
Server has been rebooted.

[rubenmarin]

Hi, searching about your error the IA returns:

1. The Quick Workaround (Disable Publisher Evidence)

The most common and effective fix is to disable managed assembly publisher evidence verification in the .NET configuration file on the Qlik Sense server.

1. Stop all Qlik Sense services on all nodes of your environment.
2. Navigate to: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\
3. Locate and open machine.config in a text editor as an Administrator.
4. Under the <configuration> section, add or update the following runtime tags:

xml

<runtime>
  <generatePublisherEvidence enabled="false"/>
</runtime>

5.Save the file and restart your Qlik Sense services.

And I remember that years ago I edited this file in a customer to solve a similar issue. I don't remember if it was the same tag but I think it worth to give a try.

The 2nd point the IA returns is:

2. Remove Unused Connector Packages

If the issue persists or your server is entirely offline, Qlik Support recommends temporarily moving the problematic connector folders out of the common data directory to stop them from trying to load.

1. Go to: C:\Program Files\Common Files\Qlik\Custom Data\
2. Locate the folders for web connectors/data markets (such as QvWebStorageProviderConnectorPackage or QvOdbcConnectorPackage).
3. Move the folders to a backup location outside of the Program Files directory (do not just delete them, as they will be needed if you apply future patches).
4. Restart the Qlik Engine service to immediately apply the fix.

I've also done this some times but I don't remember any time that it solved the situation, but it's a quick test to do.

[davidwarner344]

The error points to an encryption key issue after the service account password change. It looks like the Web Connector keys can no longer be decrypted (Key not valid for use in specified state). I'd verify all Qlik services are running under the correct account and consider regenerating the connector keys/configuration. If that doesn't help, opening a Qlik Support case is probably the fastest path.

[vighnesh_gawad]

I encountered a similar issue and resolved it by recreating the encryption key for the affected connectors. You can find the steps in the article below:

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-on-Windows-Error-retri...

However some users have reported that this solution did not work for them. In that case, you can check alternative solution discussed in my previous thread here:

https://community.qlik.com/t5/Management-Governance/Data-Connections-in-Qlik-Sense-Hub-not-loading/t...