Killed because Named User Cal was needed from another client

[wizardo]

hi,

I am running the sysmonitor QVW and I get this in the "exit reasons" of the new audit log in version 11

"Killed because Named User Cal was needed from another client"

I get this for both qv.exe clients and ajax clients.

does any one have an idea what its about?

or any documentation about the new entities presented in the  new LOG file of QVS 11

or any documentation other the the NOT full server reference guide?

[#2]

Sounds like the server has rejected a user from viewing a document because it has run out of named user licenses to give out.

Your license for QV server will allow a certain number of named users (user CALs or Client Access License) and / or document CALs. When an unrecognised user attempts to open a document from the AccessPoint, the server will look in it's pool of user CALs to see if it has any left. So if 4 have been assigned out of 5, the next user to open a document will be given a CAL, and they can open the document. If a 6th user comes along, there are no user CALs left, and they will be denied access, with the error message logged that you see.

This means you need to remove a user CAL from someone so there is one spare for whoever is trying to log in, or assign them a document CAL. This is all done via the server management console (QMC).

[Or]

User CALs are limited to one computer at a time (I think multiple instances of QV on the same computer are safe). I imagine that your error is reflecting the fact that a single user is trying to log in from multiple machines, and booting the older of the two sessions each time.

[wizardo]

Hi jdallen,

thanks for your answer.

i have a community license for 100 users on the document.

i have turned on "Allow dynamic CAL assignment"

but in actuality i only have about 30 active (assigned) users.

so the culprit is elsewhere i believe.

[wizardo]

Hi Or Shoham,

Thank you for your answer.

i think i need to clarify, this is not an error message.

i use the Logging options of version 11 server.

one of the output log file includes a field called "Exit Reason". (the name implies its contents but its content isn't documented )

one of the values is the phrase i stated in my post:

"Killed because Named User Cal was needed from another client"

now your reply still might apply except i get this very often and for all the active users (about 30 of 100 possible.)

now i could imagine one of my "super" users running all day from station to station and logging in with the same username

but according to the log i have got an entire building full of people running all day from station to station

i just wish there was some documentation of all the new logs and the meaning of the values written into them

(if there is such please share the secret...).

Daniel

*

(btw, i am using the QVsystemMonitor for version 10/11 which is a great tool here : http://community.qlik.com/qlikviews/1029).

[wizardo]

hmm,

well i stand (partially) corrected and apologizing for there is some documentation about the log files

in the "QlikView server documentation.pdf"

part 3

chapter 8

but  although there's a lot of info in the above mentioned documentation,

the answer to the specific topic of this thread is not to be found there. oh well can't win them all can you

[#7]

This happens to my Named CAL users and we do not utilize dynamic CAL assignment.  I think this guy's post explains what is happening to us.  It is annoying enough that it happens from machine to machine.  However, the browser to browser is ridiculous!

http://michaelellerbeck.com/2011/10/04/qlikview-the-annoying-server-communication-lost-closing-docum...

[pat_agen]

Hi,

I am bumping this up to the top because I see there has been no answer.

We are in the process of migrating to v11 SR from v8.5 so quite a big leap.

Till now all user access was via the plugin we are now testing a mix of Ajax and plugin.

In 8.5 users would open several sessions on different documents simultaneously.

thsi just no longer seems possible as each session is killed off with the "Killed because Named User Cal was needed from another client" as soon as a new document opens.

This isn't just a pain this is a potential show breaker as it is a big step backwards.

Are there any settings we can tweak to stop qvs killing these sessions. They are the same person same machine. I can see from the  log qvs gets different info from different "clients", so within Internet Explorer a plugin session is seen as a different "client" from an ajax session. But I am also seeing this happen between two plugin sessions - same user same machine. 

EDIT: after rechecking the last sentence needs correcting. If the user stays with the same client (ie plugin or ajax) then the already open sessions are not killed. So the message seems logical if ajax and plugin are to be considered as different "clients", but not great from a "customer" perspective - we pay for the named user licence, why then make it awkward when we use the licenses?

Looks like we will to have review the approach using a mix of Ajax and plugin.

QMC settings are Identify user by User name, allow dynamic license lease, allow dynamic CAL assignement.

Plenty of Names User CALs available so thsi is not an issue.

Message was edited by: Patrick.Laredo

[Chip_Matejowsky · Accepted solution]

Killed because Named User Cal was needed from another client

Another user session is being opened against an already active Named User CAL, but from a different client or machine, or the same QVW application from a different browser tab.