topic Re: Not able to assign a document CAL in QlikView

Not able to assign a document CAL

Jagveer — Mon, 26 Jan 2026 18:19:17 GMT

Hi,

I am trying to assign a user a document CAL on QMC. I've been doing this for past 3 years with no issues. But today, when I am assigning a new user in Document CALs, it appears in the list and the "Document CALs assigned to Users" increase. But, the moment, i hit apply the number goes back to the previous value, even though the name of the user stays in the assigned users list and the user doesn't see anything on the access point.

Re: Not able to assign a document CAL

Chip_Matejowsky — Thu, 10 Oct 2019 19:22:53 GMT

Hello @Jagveer,

Without being able to see your QMC, I suggest we start with basics here. Do you have any available Doc CALs allocated to this document? Check QMC > Documents > User Documents > select the QVW you want to assign a Doc CAL to user > Document CALs tab and look at what's listed for Number of CALs allocated to this Document.

If you could post a screen capture of what you're seeing in the QMC, that'd be helpful.

Re: Not able to assign a document CAL

Jagveer — Thu, 10 Oct 2019 19:38:14 GMT

Hi Chip,

Sorry for not being detailed earlier.

I have 19 Document CALs assigned to this document. 18 of which are assigned to Users. I am trying to add 19th User There are 4 Unallocated Document CALs on the server as well apart from the 19 assigned to this document. The Security Authorization on the QVS is NTFS authorization and i have given the required rights to the user over the document at windows level.

I have attached the screen capture for reference

Re: Not able to assign a document CAL

Chip_Matejowsky — Fri, 11 Oct 2019 12:14:46 GMT

Ok, so you have one additional Doc CAL allocated to this QVW and when you attempt to assign it to an end user you experience the issue described in the initial post on this thread - you are able to perform the typical steps to assign, but when you click the Apply button, the assignment doesn't complete.

What is the full build version of QVS you're running (i.e. 12.30. 20300)?

Re: Not able to assign a document CAL

Jagveer — Fri, 11 Oct 2019 12:24:59 GMT

Hi Chip,

the build version is 12.10.10000.0

Re: Not able to assign a document CAL

Albert_Candelario — Fri, 11 Oct 2019 14:35:19 GMT

Hi Jagveer,

Is any message pop-up when doing this? or any error in the QVS/QMC logs when doing this action?
Did you check the license information if you tick the limitation box and you added any value there?
Cheers!

Re: Not able to assign a document CAL

Jagveer — Fri, 11 Oct 2019 14:46:46 GMT

Hi Chip,

I don't get any pop error or in log. Also, the Limit number of CAls is unchecked

Re: Not able to assign a document CAL

Jagveer — Tue, 15 Oct 2019 13:35:44 GMT

Hi Chip,

Any Suggestions on this?

Re: Not able to assign a document CAL

Brett_Bleess — Tue, 15 Oct 2019 15:27:17 GMT

Jagveer, per Albert's comment, are there any entries in the QVServer Event log or the QMS log to point to an issue? The only thing that comes to mind for me is the following setting in the QMS exe.config file located here:

C:\Program Files\QlikView\Management Service\QVManagementService.exe.config

The following setting is the one to check:

If that value of 262144 is what you have, try doubling that to see if that allows you to save things. Check that and the logs and shout back. If you change the setting value, do not forget to bounce the QMS service for it to get picked up...

Regards,
Brett

Re: Not able to assign a document CAL

Jagveer — Tue, 15 Oct 2019 18:25:30 GMT

Hi Brett,

I couldn't find the file you mentioned. I have attached a screenshot of the Managementservice folder for your reference

Re: Not able to assign a document CAL

Brett_Bleess — Tue, 15 Oct 2019 18:33:11 GMT

Recheck the path, you are in ProgramData.... 🙂 It is in Program Files...

Regards,
Brett

Re: Not able to assign a document CAL

Jagveer — Tue, 15 Oct 2019 18:47:15 GMT

I checked there because i couldn't find any folder named Managementservices in program files.

i have attached the screenshot for reference.

Re: Not able to assign a document CAL

Brett_Bleess — Tue, 15 Oct 2019 19:07:27 GMT

Ok, so I am guessing things may not all be on the same server in this case, go to the QMC\System\About the first entry in the list there is going to be the QMS, see what server that is running on, that is where you should find the file... Hopefully this makes sense.

Cheers,
Brett

Re: Not able to assign a document CAL

Jagveer — Tue, 15 Oct 2019 19:10:18 GMT

Hi Brett,

everything is on the same server. it occured to me as well and i checked in QMC. it is the same machine.

Re: Not able to assign a document CAL

Brett_Bleess — Tue, 15 Oct 2019 19:51:36 GMT

Ok, so the only thing left is you likely installed to a different directory when you ran the installer, hopefully you know where that would be, as the only other way I know to find it is to look at the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\QlikviewManagementService

Check the ImagePath string value there, that should confirm where things were installed and hopefully you can find the exe.config there.

Cheers,
Brett

Re: Not able to assign a document CAL

Jagveer — Tue, 15 Oct 2019 20:28:11 GMT

Hi Brett,

you were right, the installation path was different. However, even after changing the MaxReceivedMessageSize value to double like you said, the issue still remains. i have attached the screenshot from the log, from which it seems everything is perfect. However, on the server the issue persists as before.

Re: Not able to assign a document CAL

Brett_Bleess — Wed, 16 Oct 2019 13:31:47 GMT

Jagveer, ok, so you have confirmed worst case scenario here, thanks for the log snippet, that shows the QVS is doing things, the issue is it cannot update the CalData.pgo, and the only strange thing at this point is we are not getting any message in the log telling us as much. Can you check on all your CalData.pgo files to see if all the timestamps are relatively in sync, or if one of them may be way off? You are not getting any error when you are setting things up as well, which would indicate the read of the file is fine, it is the update/write that is having issues, so the best bet is to confirm the timestamps on all the copies of the CalData.pgo files, there will be one in the Root path of the QVS Folders tab settings in the QMC, and then each QVS node will have a local copy in C:\ProgramData\QlikTech\QlikViewServer as well. Best I have to try to keep moving forward here.

Regards,
Brett

Re: Not able to assign a document CAL

Jagveer — Wed, 16 Oct 2019 13:39:35 GMT

Hi Brett,

By timestamp for the file if you mean their last modified timestamp then they are in sync. Both at the root path and at the C:\ProgramData\QlikTech\QlikViewServer as well.

Re: Not able to assign a document CAL

Brett_Bleess — Wed, 16 Oct 2019 13:44:22 GMT

Hmmmm, that is quite puzzling to say the least, as if they are updating, it begs the question of why we cannot write the new Doc CAL out. The only thing of which I can think at this point would be to put the QVS into Debug log level, you have to go into the QVS Settings.ini and change the Verbosity setting there to 900 to get that, and then restart the service to have it kick in, you will then start seeing Debug messages in the logs, if you can do that at some point and then try things again, we can see if that tells us anything. The only other thing of which I can think is some other utility running on the server that is monitoring those files and rolling back the change on us for some reason.

Regards,
Brett

Re: Not able to assign a document CAL

Brett_Bleess — Wed, 16 Oct 2019 13:57:22 GMT

There is one other thing we could do to confirm the pgo contents, there is a setting we can add to the QVS Settings.ini:

PgoAsXmlAslo=1

Setting PgoAsXmlAlso setting

You do not really want to leave this running all the time, as it creates quite a bit of overhead in that every time there is an update to the .pgo, the .xml has to also be updated, but this would allow us to look at the matching .xml file and confirm contents....

If you see the entry you have entered in there, then I think that would confirm we have a corrupt file...

Regards,
Brett