Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
After server update users can't open Qlikview file and they get this error "Failed to open document, You don't have access to this document. 19"
It was working fine until server update. We're are using section access.
Hi @MK97
It seems you already verified the license contents, could you verify that the file access and Section Access are properly set?
Could you also let us know what was the previous QV version and current one on your server?
If any of the three suggestions in the article don't help to fix the issue, it will be probably better to open a case so we can reproduce with a copy of your app.
Hope it helps.
Hi @MK97,
Users are attempting to open QVW on AccessPoint? Or in QV Desktop? Is issue happening on all QVWs or a single/specific set of QVWs?
Use the Manual LEF Checker - http://lef1.qliktech.com/manuallef/default.aspx to enter your QVS license and check to see if you have the following provision in the license: NUMBER_OF_DOCUMENTS;XXX;; (XXX = number).
Best Regards
Hi Chip,
User attempt to open QV from Desktop. We have two different QVW, but only one is working.
NUMBER_OF_DOCUMENTSCALS;20;
Hi @MK97,
Thanks for the information. The provision from the license you provided (NUMBER_OF_DOCUMENTSCALS;20;) is for Document CALS, but not the same as the one I listed (NUMBER_OF_DOCUMENTS;XXX;;). So please check to see if the LEF contains the NUMBER_OF_DOCUMENTS;XXX;; provision.
Also, do you have Section Access applied to this specific QVW that cannot be opened?
Best Regards
LEF does not contain NUMBER_OF_DOCUMENTS;XXX;.
You can test by copying the app and temporarily removing Section Access on the copied app to see if issue is related to Section Access.
Hi @MK97
It seems you already verified the license contents, could you verify that the file access and Section Access are properly set?
Could you also let us know what was the previous QV version and current one on your server?
If any of the three suggestions in the article don't help to fix the issue, it will be probably better to open a case so we can reproduce with a copy of your app.
Hope it helps.