topic Error maximum message size in the qv-user-manager ‘power tool’ in QlikView

Error maximum message size in the qv-user-manager ‘power tool’

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

I tried to list out the CAL & DMS data for a report document, where there are up to 2000 entries.
cmd /c ""C:\QlikView\Tools\qv-user-manager\qv-user-manager.exe" --list dms > dms.csv";

It failed with the following:

The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.

I can add as many users as wanted but cannot then list them. I also get the same error when I try to delete them.
cmd /c ""C:\QlikView\Tools\qv-user-manager\qv-user-manager.exe" --remove dms --document qv_doc.qvw < dms.txt";

If anyone knows a way to work around this or fix it, I’d be very interested.

Error maximum message size in the qv-user-manager ‘power tool’

rwunderlich — Wed, 22 Feb 2012 22:32:56 GMT

I'm guessing that you can edit

qv-user-manager.exe.config

that's in the same dir as the exe -- and increase the maxReceivedMessageSize valule there.

-Rob

Error maximum message size in the qv-user-manager ‘power tool’

g_westaway — Thu, 23 Feb 2012 11:28:53 GMT

Thanks Rob!

I should have considered that. So we changed the following settings and it ran quick and did the job:

maxBufferSize="99999999" maxReceivedMessageSize="99999999"

Cheers Giles

Error maximum message size in the qv-user-manager ‘power tool’

Anonymous — Tue, 20 Mar 2012 21:24:05 GMT

Rob,

thanks for the tip.

Giles, did you get this removing Named User Cals? I received the same error messages as you then resolved this with the increase of buffer/message size. But it doesn't appear to be removing any Named User Cals.

and there are now no messages of any kind to tell me why not.

when i output the Named User Cal list to a csv file this works fine.

I think the key is with the removal type. it removes specified users (I'm not specifying any) or inactive CALs. I'm not sure what constitutes an inactive CAL but most of my CALs are only a couple of days old and I wouldn't consider them inactive.

I will have to experiment further.

Error maximum message size in the qv-user-manager ‘power tool’

g_westaway — Fri, 23 Mar 2012 11:18:27 GMT

For some reason the utility will not remove CALs that have been used within the last 30 days; this is hard-coded within the tool (would be nice if a future version this could be parameterised).

The shortcut we used was to advance the server clock by 30+ days, then repeat the full remove job; not ideal but it worked.

Error maximum message size in the qv-user-manager ‘power tool’

StefanBackstrand — Fri, 23 Mar 2012 12:01:52 GMT

Giles, Just be aware of the grace periods on Named User CALs, since that is a quarantine of 24 hours. You also have a 28 days turn around time on Usage CALs.

Just so that you're not engaging in accidental license abuse!

Error maximum message size in the qv-user-manager ‘power tool’

Anonymous — Mon, 26 Mar 2012 01:35:18 GMT

Stefan,

I find your comments confusing. The 24 hour quarantine period on Named User CAL's cannot be circumvented so we should be able to remove users from this list where their last activity is older than 24 hours yes?

What license abuse could come about when the QV Server has safeguards in place to stop premature removal of a user? I just want to be sure we don't do anything we shouldn't.

Regards,

John.

Error maximum message size in the qv-user-manager ‘power tool’

StefanBackstrand — Mon, 26 Mar 2012 07:46:24 GMT

janderson wrote:
The 24 hour quarantine period on Named User CAL's cannot be circumvented so we should be able to remove users from this list where their last activity is older than 24 hours yes?

Yes, definately. I understand your problem with the 30 day limit in the current code, but I would say that messing with the system time on a server just might be inappropriate when re-assigning CALs.

Error maximum message size in the qv-user-manager ‘power tool’

Anonymous — Tue, 27 Mar 2012 22:03:02 GMT

Anyone silly enough to mess with system time on a server is asking for trouble - and I don't just mean abuse of QV license agreements. Changing the system time is not something I'd touch in a production (or test) enviroment.

Error maximum message size in the qv-user-manager ‘power tool’

StefanBackstrand — Wed, 28 Mar 2012 09:06:44 GMT

Again - yes, definately. But that's what he did, and that's why I commented on it.

Error maximum message size in the qv-user-manager ‘power tool’

g_westaway — Wed, 28 Mar 2012 18:42:52 GMT

John, I'm not sure using abusive words is helpful here, we are all QlikView enthusiasts trying to make sense of it all.

Perhaps you could list a few reasons why changing the erver clock temporarily is not wise.

Actually I agree, but since we were migrating our license according to QlikTech requirements, we had to clean up a very long list of data in short time.

Ideally the utility would not have 30 days hardcoded.

Stefan - take on board your comments.

Error maximum message size in the qv-user-manager ‘power tool’

Anonymous — Wed, 28 Mar 2012 21:13:21 GMT

Hi Giles,

apologies if I caused offense, it struck me that Stefan might have thought i was either a) supporting the notion of changing system time on a server or b) that I was doing it myself.

I just wanted to clarify to him that I wouldn't do such a thing in a million years. if you do then that's your business.

In my experience, practically every program and service running on the server relies on the fact that the next second from now will be greater than the last. Log files updating, processes checking at scheduled times then performing this or that task. all in an order that at its most basic level is defined by the system time. If you go setting the system time to some point in the future, you are likely going to have to bring it back again. This could cause all sorts of havoc and its just not worth doing on a production machine.

If you feel that you were justified in doing so then thats totally not my business or concern.

I agree with your point that the code should not be set to 30 days. it can be set to zero days and does not affect the functionality of the Qlikview server's quarantine processes.

Regards,

John.

Error maximum message size in the qv-user-manager ‘power tool’

g_westaway — Thu, 29 Mar 2012 08:57:31 GMT

Hi John - no problem at all, thanks for the explanation.

Although I noted what we had done, it wasn't actually a recommendation and QlikCommunity is a great forum for sharing experience and knowledge, where the documentation is scarce. Any further discoveries on qv-user-manager I will try to share.

Cheers Giles