Hi,

I have a problem with licenses, from time to time when users let processes runing at night at the next day the session they let running has crashed and the bshell they were using is closed but their license is still showed in
licmon -w

when i execute: licmon -w | find "jcasanov"
i got this:
server bx/bw jcasanov.1035 server 12-09-2006 07:57

i guess the 1035 is the pid of the bshell jcasanov was using so i tried
bshcmd -k 0 1035 (to kill the bshell subprocess itself) but because the bshell is not running it simply waits... but not do anything...

so, my question is: is there a way to free that licence without reboot the server?

thanks in advance,
Jaime Casanova

Hi there,

use -e instead of -k

regards

Norbert

Thanks for the answer...

i tried "bshcmd -e 1035" and it simply waits (i wait for a minute before stopping it).
is this a long running operation?

Maybe i just have to wait longer? any other idea?

have you tried using the clean option in licom

It would be good if you can put the cleanup command in a job(using Scheduled Tasks) which could be run every hour or every other hour and which would take care of runaway baan processes that takes up licenses even after user closes the bshell..

the command for clean up is licmon -c

sk

I think is more easy that stop and start the baan licencing service this liberate the licency

When you do this, you are going to throw off any user who is connected to Baan at that time. Dont think the users would appreciate that. licmon -c doesnt touch the logins that are valid....

sk

My suggestions:

Better to run the licmon utility with the kill orphanded licenses e.g. with the taskmanager of windows.

Up to now we had no problems with the live system, the command seems to be stable.

Regards,

Kozure

have you tried using the clean option in licom

thanks for all the responses...

my version of licmon doesn't seems to know about the clean option

Usage: licmon [-vVdbBwkus][-h host][-p num]
-v : show version
-b : show brandinfo
-B : show brandinfo from brandfile and shared memory
-C : clear brandinfo from shared memory
-w : show users
-W : show other connections
-a : show all connections
-p [num] : check connections (ping)
-k : kill server
-u : show usercount
-s : show statistics

C:\baan\bin>licmon -v
Copyright Baan, 1990-2001
Porting set 6.1c.06.01
Port number PA.1649

regards,
Jaime Casanova

brandinfo show the brand information of this host
BRANDINFO show the brand information from the file
help show this information
ping [number] ping the licence server (test connection)
quit quit licence monitor
stats show server statistics
users show usercount
who [all|ALL] list [other | all] users
clean cleanup orphaned local licences

D:\baan\bin>licmon -v
Copyright 2004 Baan International BV
Porting set 6.1c.07.06
Port number PA.2644

hi ,

try

1) licmon ->

2) clean ->

to kill

bshcmd -e <pid>

regards,
niraj

Hi ,

Using bshcmd -e <pid> , we can kill one user at a time
Is it possible to kill all user in one command
Is there anything like

bshcmd -e <pid1> , <pid2> ..........

or something like killall for win NT

Regards,
Niraj

Since users could be thrown off by stopping and restarting Baan Licensing Service, you could probably use the command
c:\Net Stop BaanLicensing

followed by

c:\Net Start BaanLicensing

sk

Hi

Hang users are major problem of BaaN licensing mechanism specifically in high-available 24/7 centralised operations. At that time, you can not restart licence service, because it abnormally disconnects active users and there are chances of data inconsistency/corruction in database.

Thats why in newer porting sets BaaN has provided -c in licmon program. In my experience -c can fails some times.

You can use pskill available here http://www.sysinternals.com/Utilities/PsKill.html
or kill command provided in windows resouce kit. But that can also fails.;)

regards,

-Suhas

I think it would be better to put a scheduled task in the server that runs a batch file every 5 hour that stops and starts the licderp (licderp -stop and licderp -start). This will not trouble existing users as far as I have seen in B50c. You may try for BIVc4.

Does not effect users logged in in IVc3 or IVc4. It does not log them out. They will remain logged in but the license manager will not recognize them. The only problem you may have is if you run into maximum number of users while users not logged through the license manager still exist. These users will get the message maximum number of users reached although they are already logged in because the license manager does not recognize them.

The clean fuction does not exist in older porting sets but I'm not sure when it was introduced.