How many times are users are getting "user count exceeded"?

rsaritzky

Hi:

We have a single NAV system, but have users in 3 geographical locations using Terminal Server to access NAV. We have more users than NAV licenses, so users get the "Your program license does not permit more users to work simultaneously" message.

I'm trying to figure out how often this occurs, but because of the 3 separate locations, it's been difficult to get people to tell me every time they get this message.

So, I'm trying to figure out if any trigger in Codeunit 1 is fired before this message is displayed, so I can log these failed attempts.

Does anyone have any ideas on this?

We're on 5.0SP1 client, 3.60 database, SQL2005.

PeterD

LoginStart?

ara3n

The following solution records Nav errors.

http://mibuso.com/blogs/ara3n/2008/05/2 ... -navision/


but users would have to be logged in.

rsaritzky

I know for sure that the CompanyOpen trigger does not run prior to logging in. I'm not sure about LoginStart. I may just have to put some code into LoginStart to test if it fires when we get the "user count exceeded" message.

ara3n

Also are you up to date with your maintenance plan?
If not, I think they will no longer allow you add new users.

kriki

Well, you can try another route:
Implement a session killer http://www.mibuso.com/howtoinfo.asp?FileID=18 with the NAS or in SQL when the total user count= license limit and when it disconnects a user, log it in some table.
This way, you have an idea how much it 'would' happen and you free sessions that haven't been used for some time.

rsaritzky

kriki wrote:

Well, you can try another route:
Implement a session killer with the NAS or in SQL when the total user count= license limit and when it disconnects a user, log it in some table.
This way, you have an idea how much it 'would' happen and you free sessions that haven't been used for some time.

I do in fact already use a session-killer app. The problem here is the number of users. Our users seldom are idle more than 10-15 minutes, so I don't want to kill them. Killing them when the license limit is MET doesn't really do me any good - that will kick of user number "n-1" - I don't want to do that. I want to know when user "n+1" tries to log in.

I am going to try the LoginStart trigger to see if I can capture a failed login due to user count exceeded.

Alex_Chow

ara3n wrote:

Also are you up to date with your maintenance plan?
If not, I think they will no longer allow you add new users.

Since the user is running 5.0 executable, the deadline for him is June 1st.