Error Accessing QMC - cannot read properties of undefined (reading 'userid')

[WillBooker]

When opening the QMC we are experiencing the error "cannot read properties of undefined (reading 'userid')".

Sometimes it can be cleared by clicking Refresh but sometimes it persists.

[Alan_Slaughter]

Hi WillBooker, can you apply this article:

https://community.qlik.com/t5/Knowledge/How-to-configure-the-WebSocket-origin-allow-list-and-best/ta...

[WillBooker]

Thanks for your reply Alan but I'm afraid the Host Allow List already had the correct addresses.

Any other advice greatly appreciated.

[marcos_herrera]

Hi Dear Will

I had the same issue yesterday, Did you to solve it? I tried clear all Additional response headers but not worked

[afuruya]

Hi Will
I am facing the same problem. I am not certain, but it seems to have occurred since the upgrade to August 2022.

[Mario_Petre · Accepted solution]

Qlik Support is currently investigating this issue as it seems to impact several customers. 

[Albert_Candelario · Accepted solution]

Hello all,

As @Mario_Petre  said, as of now there is a defect with our engineering team and is currently under investigation.

The defect id is QB-14353 for your reference.

Kindly, check the release notes for the defect id to ensure it has been resolved on later versions.

We will also update this topic once it has been resolved and we know where the fix will be delivered.

Cheers,

Albert

[Giovanni_Civardi]

Thank you @Mario_Petre and @Albert_Candelario , is this issue happening under particular condition? could you please give more info on this? we are going to plan some upgrades to aug 2022 SR1 and this could represent a reason to choose May 2022. Thanks in advance.

[RafaelBarrios]

Hi @WillBooker,

The same problem occurred to me when we updated to Feb2022, I also opened a case to Qlik and we are waiting to increase the resources but I don't think it is the cause.

in my case we had a multinode installation, central node, rim node and another just for qlik database and qvds.
This is a problem with the APIs or queries that the QMC uses in the back and the speed to get the response, as soon as I reduced the number of users (in my case more than 100,000), I checked also some custom properties and security rules that were not well implemented and its "temporarily solved".

Best,

[Albert_Candelario]

Hello @RafaelBarrios,

As of now, we could only reproduce in May and August 2022 tracks. Is the same exact issue the one you are experiencing on Feb 2022, maybe you are using a particular patch?

Cheers,

Albert