Can somebody please tell me how the NLM (ie NLM_STATS) calculates the number of users that are logged on?

We have a client who has 40 licences. NLM_STATS shows that there are about 20 users logged on, but when they try opening the app on other PCs it says Too many users.

They have looked at the server and disconnected anyone logged on who does not have any files open but that still only allows about another 7 to log in. So, where are the other licenced being chewed up?

Can anyone suggest anything they can try?

Thanks

Is the session being unloaded / closed cleanly? (does the Windows shortcut close neatly on session completion)

If the session crashes out or is closed violently, perhaps the user count isn't being decremented properly. Perhaps a log file would suffice in this regard.

Perhaps some users are loading multiple local sessions?

I'd be fossicking around the Netware client settings and the Windows shortcuts to check the settings don't cause the users to crash out.

I recall years ago that CD towers or some backup devices could cause this glitch under Netware.

Could you inspect the server monitor.nlm (or equivalent) to view the users' files open and check/count those who have *.lk and *.ov files open.

What version of Netware?

What version of the Revelation product?

Steve

Steve,

Netware 4.1, AREV 3.1 - i think

They said they have checked how many clients have .lk and .ov files open on the server and its nowhere near the max number of user licences they have.

I think a reboot of the server allows the max number of users to log in but then the problem starts all over again.

One possibility is that the workstation session isn't shutting down properly and that the connection to the NLM prevails somehow.

Try (with no-one else active on the system) logging into and out of the application 40+ times in succession from the one workstation, and see if you can trip the "Too many users" error condition by using one workstation only.

I'd be interested to watch users closing down their sessions - do they simply hit the X at top right of the DOS Window, effectively stopping the LHIPXTSR from unloading gracefully. Or do they exit gracefully?

I have also seen an issue with this when the client is connecting to multiple Novell servers. Let's say the user is connecting to ServerA, which is the ARev server, and it has a 50 user license. This is more than enough to support the 40 user license for the application. Let's say the user is also connecting to ServerB, and this server only has a 30 user license.

If the connection table is full on ServerB, even though connections and licenses are still available on ServerA, ARev will return the "attempt to log in too many users."

We had this problem a lot at my last company where we had a small fileserver that was just for the development group in addition to our development server. ARev wasn't on the fileserver, but if its connection table was full, we couldn't get into ARev.

HTH,

[email protected]

Greyhound Lines, Inc.

Yes, this is a problem if there is just one Novell server too. We had this similar issue:

50 user Arev

100 user Novell

35 arev users logged in

110 total Novell users for email, etc. (Don't know how they got a 100 user Novell license to support 110 logins.)

When the Novell user license count was exhausted, you could still log into Novell, but not Arev, even though Arev had plently of licenses left.

Got the same 'Attempt to log in too many users' message from arev.

Is the /P switch being used when loading LHIPXTSR? Check the batch file or PIFs.

Other thoughts - re Novell client.

Check that "true commit" is set on, if your Netware client supports these settings.

View this thread on the forum...