Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
skirdinsa
Contributor II
Contributor II

QSB: GET /v1/quotas/app_mem_size failed with status code 401. Error: Unauthorized

Hello!
I copied the working application for the revision, but I can't reload it, due to an error

{
    "duration": 392709,
    "endTime": "2020-01-14T05:38:20.921Z",
    "errors": [
        {
            "description": "GET /v1/quotas/app_mem_size failed with status code 401. Error: Unauthorized",
            "error": "General error",
            "line": "",
            "lineNumber": 549
        }
    ],
    "id": "b99bfcaf-8d42-4e79-91ab-1e658897060a",
    "peakMemoryBytes": 425097920,
    "reloadId": "3fda7d29-9a8c-4f63-a73f-2bb5fd757420",
    "size": {
        "file": 0,
        "memory": 0
    },
    "status": "error",
    "warnings": []
}


Perhaps this is due to memory limitations. The application seems to be not big.

And I can’t find where I can see how much memory it takes.

Labels (1)
  • SaaS

9 Replies
robert99
Specialist III
Specialist III

Hi @skirdinsa

I'm getting exactly the same error with Qlik Sense Business.

And like you the application is not that big

QSB has all sorts of 'reload data' errors now.

For example if I try to update twice it gives me an 401 error

Or with this example above I can't reload data. But debug runs on full load but shows no errors.

 

Sergey
Contributor II
Contributor II

The problem is still relevant.
But there is an option - reload through the hub (click on three points on the document and select reload)
Not very convenient, but it's better than nothing.

Michael_Tarallo
Employee
Employee

I have made a cloud dev aware of the situation.

Have you logged a case with support?

https://support.qlik.com/

https://support.qlik.com/QS_ContactUs

 

Select your region - I am assuming you did this and you could not get anyone you are saying?

 

click here to continue without logging in.

I logged case 01901874 for you - you can use that to follow up.

Regards,
Mike Tarallo
Qlik
robert99
Specialist III
Specialist III

Hi @Michael_Tarallo 

Thanks for doing this

The issue I have with logging a support call is its not possible to login to the support portal.

I can login to Qlik.Com. But then when I go to the portal it will not let me login. Or view my calls using my clients relevant email. So I log a service request without logging in. And give the email link. But then its impossible to see the support number details

I guess the support portal doesn't support Qlik Sense Business users. But if so QSB users need a way to log support calls and to see the progress.

At present QSB is becoming almost unusable (its worse today than yesterday). And its my clients end of year and they need a working QSB.

 
 

 

 

robert99
Specialist III
Specialist III

I've done some work to try and see why the above issue might be occurring?

I started removing script (loading data) from the above App. It finally updated without the above message

The App size was 82000 KB.The only way I could find this out was to download as QSB does not so the file size of the Apps (I use to always monitor before in QSCB. But can't now)

Before the data was removed. unsure (I can't download the backup App with data) but unlikely to be over 100KB,

 

 

 

skirdinsa
Contributor II
Contributor II
Author

Hi @Michael_Tarallo 

No, I don't report issue. When I select "a problem with the loading script," the support portal recommends describe problem here. 

skirdinsa
Contributor II
Contributor II
Author

Hi @robert99 

I completely agree with you.

Michael_Tarallo
Employee
Employee

Please check this out - this is how you log a case so it gets in the hands of the support staff:

https://community.qlik.com/t5/Qlik-Fix/Qlik-Fix-How-to-Log-a-Case-as-a-Guest-in-the-Support-Portal/t...

Regards,
Mike Tarallo
Qlik
skirdinsa
Contributor II
Contributor II
Author

Yes, I know how to use the portal. Today the problem is not reproduced. I don’t know why, we finished work with this environment.

For people, who are faced with similar problems, my tip: when I start loading from the script and got the dropbox error, I went to the hub and start loading from the hub. After that, loading from the script also worked fine.

It seems, when you sit in a script for a long time, the connections to the dropbox fall off.