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

[g_westaway]

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.

[rwunderlich · Accepted solution]

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

[g_westaway]

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

[Anonymous]

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.

[g_westaway]

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.

[StefanBackstrand]

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!

[Anonymous]

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.

[StefanBackstrand]

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.

[Anonymous]

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.

[StefanBackstrand]

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