Qliksense Streams are not visible for any user for sometime. After sometime streams becomes available automatically

[Sarojani_B]

In our Dev environment, we have 2 nodes- central and RIM node.

When we open Qliksense hub, we are not able to see all streams. Qliksense Streams are not visible for any user for sometime. After sometime streams becomes available automatically. 

Version: Qliksense Nov 21, Patch 5

But at the same time when Hub is opened with service account, streams are visible for the service account.

Can someone please suggest what can be issue here? Is it security Rule issue?  any setting issue needs to be checked. 

Thanks

Sarojani

[RafaelBarrios · Accepted solution]

Hi @Sarojani_B 

i ran into a similar fault in may2022 and from what you describe it may be the same.

and got fixed following this post

https://community.qlik.com/t5/Official-Support-Articles/Stream-are-not-visible-or-available-on-the-h...

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.
   
   Note: 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

Hope this helps,

help users find answers! Don't forget to mark a solution that worked for you & to smash the like button!

[Albert_Candelario · Accepted solution]

Hello @Sarojani_B,

What @RafaelBarrios said is very true for the  newer version of Qlik Sense client managed, but might not be accurate for such an older version.

My recommendation is moving to a more newer version as yours will be out of support quite soon and afterwards check if the issue is still happening.

It could be a cache issue or a security rule depending on the node were you are lading.

In any case, I suggest the upgrade and then what Rafael mention will be much more relevant.

Cheers,

Albert

[Felipe_Violin]

Hi @RafaelBarrios , I was in the same situation but with the November 2023 version.
I followed your guidance and I succeeded in my environment.

Thank you for your support.