Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
WillBooker
Partner - Contributor
Partner - Contributor

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

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.

Labels (1)
5 Solutions

Accepted Solutions
Mario_Petre
Support
Support

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

View solution in original post

Albert_Candelario

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

Please, remember to mark the thread as solved once getting the correct answer

View solution in original post

Albert_Candelario

Hello all,

We have confirmed the issue has been introduced as of February 2022 Patch5 and above on such February 2022 track.

We will keep you posted.

Cheers,

Albert

Please, remember to mark the thread as solved once getting the correct answer

View solution in original post

Albert_Candelario

Hello @RafaelBarrios ,

The fix are expected if all goes well on next patches:

  • August 2022 Patch2
  • May 2022 Patch7
  • February 2022 Patch10
  • November 2022 IR

Cheers,

Albert

Please, remember to mark the thread as solved once getting the correct answer

View solution in original post

RafaelBarrios
Partner - Specialist
Partner - Specialist

Great @Albert_Candelario !!!

Thanks for the info 🤞

View solution in original post

26 Replies
WillBooker
Partner - Contributor
Partner - Contributor
Author

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
Partner - Creator III
Partner - Creator III

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
Partner - Contributor III
Partner - Contributor III

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
Support
Support

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

Albert_Candelario

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

Please, remember to mark the thread as solved once getting the correct answer
giociva
Partner - Creator
Partner - Creator

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
Partner - Specialist
Partner - Specialist

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

Please, remember to mark the thread as solved once getting the correct answer