hankfu
18th April 2002, 07:14
Hi, all

We always get the message "max users is reached".
To avoid see it, we added 5 licenses. It's enough absolutely. But recently we got the message fruquently once more. And we found some users always open the baan, but actually he only use it for a while. Now we have no any idea to solve it.

Are there some solutions can kick off the users automatically when the user didn't do anything in baan within a specific time?

Has anybody met the same problem?

Any suggest will be highly appreciated.

nizamudeen
18th April 2002, 09:36
Hi,

This is an issue everywhere. there is alreday a thread posted regarding this under

http://www.baanboard.com/baanboard/showthread.php?s=&threadid=1579

Also have a try with Closeidle program. you have a 30 days trial.
Download it from http://www.dsigb.com

Regards

victor_cleto
18th April 2002, 09:38
Yes, see in the support website the solution 19868 for more details. In resume, you use two variables to control the idle detection from the server by defining (in the server side):

DS_MAX_WAIT [default=30 seconds], you specify the timout duration BW has to respond to the sync message
DS_TIMEOUT_DETECT [default=30 minutes], you specify the timeout duration before the bshell starts sending a sync message to the BW.

So, what happens is the following (assuming the defaults): after 30 minutes the bshell sends a sync message to the BW, if this one does not respond within 30 seconds, the connection is terminated. A message is then logged in the log.bshell (or NT event viewer) with a "Connection to Display Server timed out after <DS_TIMEOUT_DETECT> minutes"

But this not always works as expected, and hung bshells is a common thing...

Ravenscross
18th April 2002, 10:49
Have to say that having used CloseIdle it is a great product to use on those users that open Baan at the beginning of the day and close at the end without using it to often.

msanlon
20th April 2002, 00:35
Here's a free one that does the same as CLOSE IDLE

DS_TIMEOUT_DETECT only works when there is no client at the other end of the connection. It's handy for freeing up some licenses when a client has been killed

From porting set 6.1c.06.01 and above, Baan implemented the SESSION_TIMEOUT variable which will disconnect idle Baan Clients. This is much more useful!

See Baan Solution 110907 for more details

ericthomas
22nd April 2002, 11:53
Dear All,

We have found session time_out very useful but it leave applications locks fir users who are idle in maintain sessions of sales orders.

We have informed baan about it and they are looking into it.
Again users should not lock sales orders if not using!!

We have developed a new session to remove those locks and it is under testing now.

Frank Rogers
25th April 2002, 17:33
We have been using closeidle for sometime ( 6/9 months)

It is effective for almost eliminating ghosts and reducing the number of licences used which can be dramatic

Tip - the policy was agreed by MDs in order to "reduce" cost
Users not overly happy but it is their management's decision

There are percieved problems by users but none substantiated to date

Can be tuned for "groups" of users which is also useful