Stream are not visible or available on the hub in Qlik Sense May 2022

[Benoit_C]

After upgrading or installing Qlik Sense Enterprise on Windows May 2022, users may not see all of their streams.

The streams appear only after an interaction or a click anywhere on the Hub.

This is caused by defect QB-10693, resolved in May 2022 Patch 4.

Environment

Qlik Sense Enterprise on Windows May 2022 

Workaround

To work around the issue without a patch:

1. Locate and open the file: C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   
   
2. Modify the following line:  
   
   {"contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874","originalClassName":"FeatureToggle","flag":"HUB_HIDE_EMPTY_STREAMS","enabled":true}
   
   Set it from true to false: 
   
   {"contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874","originalClassName":"FeatureToggle","flag":"HUB_HIDE_EMPTY_STREAMS","enabled":false}
   
   
3. Save the file.
   
   If you have a multi node, these changes need to be applied on all nodes. 
   
   Note 2: As these are changes to a configuration file, they will be reverted to default when upgrading. The changes will need to be redone after patching or upgrading Qlik Sense.
   
   
4. Restart the Qlik Sense Dispatcher service AND the Qlik Sense Proxy Service 
   
   Note: If you have a multi node, all nodes need to be restarted. 

Fix

A fix is available in May 2022, patch 4.

Streams will show up (after a few seconds) without the need to click or interact with the hub.

Important NOTE about feature HUB_HIDE_EMPTY_STREAMS:

When you activate HUB_HIDE_EMPTY_STREAMS, you will have an expected delay before all streams appear.

To improve this delay, from Patch 4, you can add HUB_OPTIMIZED_SEARCH (needs to be added manually as a new flag). As of now, HUB_OPTIMIZED_SEARCH tag will be available in the upcoming August 2022 release and is not planned for any patches (yet)

If this delay (seconds) is not acceptable, you will need to disable this HUB_HIDE_EMPTY_STREAMS capability.

Cause 

This defect was introduced by a new capability service. 

Internal Investigation ID(s) 

QB-10693

[Benoit_C]

Hello JHuis,

Your issue doesn't not seem to be related, it is probably a specific issue within your configuration.

[uwqliker]

We've upgraded to Enterprise on premise August 2022 Patch 5, and the problem seems to be reoccurring, although sporadic and infrequent.

 do we need to set the HUB_HIDE_EMPTY_STREAMS to false every time we upgrade?

[Benoit_C]

Hi @uwqliker,

Each time you'll perform a Qlik Sense upgrade/migration the config files will be overwritten. During upgrade, configuration files are overwritten with the default settings. If a configuration file was manually changed in your previous deployment, you must make sure to restore your customized settings after the upgrade.

Regards,

Benoit

[uwqliker]

So there isn't there a way to change the default permanently? Does this mean we need to change it every time there is a patch as well - not just on new versions?

I'm not sure why it would be necessary to hide empty streams anyway.  Having users missing streams is a far bigger problem than showing an empty stream. I can always hide a stream through a security rule or just not create it until there's content for the stream.

Do you have any more permanent fixes/workarounds that don't require manual workarounds?

[Benoit_C]

There is no way to permanently change this setting as it's now the default setting.

Those steps are described in the upgrade process help page:

https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployA...

[uwqliker]

Hi Benoit,

So are you saying Patches will overwrite all configuration type files the same as installing a new release would?

If I'm on August 2022 Patch 5 and run Patch 6, I have to re-create the capabilities.json file? Just like I would if I were going to a new release (for example December 2022).

[Ken_T]

there are some things that get over-written by patch install, I think my team has a list of some somewhere. That would make a very good new post / new topic / new question, to see if Qlik could give some guidance  about the types of workarounds and changes that are not carried forward and are overwritten by patch installs and/or upgrades.

This would be a very nice helpful add to all of the existing docs and posts, if there is a workaround /change provided, if Qlik could indicate if this is something will need to be re-done after patch/upgrade.

random totally unrelated example, I believe the setting for allow-nonselect-queries is one that we routinely have to re-do after patch installs. (in the configuration file QvOdbcConnectorPackage.exe.config).  

[Benoit_C]

Hi @uwqliker,

If you install August 2022 patch 6, yes capabilities.json will lose all your customizations.

[Sonja_Bauernfeind]

@Ken_T Thank you for your feedback, Ken! And you are correct, these notes should be included in the articles, and, in this case, we have failed to do so. 

I have added a note to the article now and will keep an eye out for other articles as they pass my review to adjust them accordingly.

All the best,
Sonja 

[xlzgz]

Even though I created the stream and authorized it, it was not visible. The problem was solved by changing the file and restarting the services. Thanks.

The version I use, Qlik Sense November 2023 Patch 7