Baan Version : Baan4a on HPUX 11.00 (resides on application server)
Database : Oracle8 (resides on database server)

Hi,

I have this problem with some users could not login although the license is available for them to use. The problem is that whenever they login using their ID, it opens up the option dialog and the exits without launching Baan at all.
We had :
1) Bring down and up again Baan daemon on both servers
2) Recreate their ID alternately with other ID temporarily.

Solution 2) works temporarily. So we need to know why this instance happen and this is the first time we encountered this scenario.
Kindly help as we have already logged a call to Baan Malaysia and they have actually escalate this matter to Baan Holland but they still could not rectify what has cause this problem to happen.
Currently our users are using alternate IDs but there are many of them affected. So is there any way to check why this happen.

Thanks
Regards

First thing you should do is check all relevant log files in $BSE/log and post some snippets of it here. It will help the folks on Baanboard in troubleshooting your problem.

You may also want to chekc to see if you have not reached the maximun amount of processes that is configured for the Box.
Also make sure the use has the appropiate files in the /baan/bse/lib/user directory.

These are the messages in log.bshell under the current environment(/software/baan/bse/log)

2003-01-10[09:00:32]:E:kkumut01: Log message called from /port.6.1c.06.02/vobs/t
t/lib/al_1/al_log.c: #1128 keyword: stack trace
2003-01-10[09:00:32]:E:kkumut01: Pid 12112 Uid 188 Euid 188 Gid 125 Egid 125
2003-01-10[09:00:32]:E:kkumut01: user_type N language 2 user_name kkumut01 tty 5
locale ISO88591/NULL
2003-01-10[09:00:32]:E:kkumut01: Errno 2 (No such file or directory) bdb_errno 0
2003-01-10[09:00:32]:E:kkumut01: ( 0) 0x000c6df0 create_stack_trace + 0x90 [
log.bshell (1%)
t/lib/nw_1/ipc_sock.c: #914 keyword: ipc
2003-01-10[09:23:07]:E:kkumut01: Pid 13423 Uid 188 Euid 188 Gid 125 Egid 125
2003-01-10[09:23:07]:E:kkumut01: user_type N language 2 user_name kkumut01 tty
locale ISO88591/NULL
2003-01-10[09:23:07]:E:kkumut01: Errno 0 bdb_errno 0
2003-01-10[09:23:07]:E:kkumut01: Log_mesg: boot failed of user 'kkumut01' remote
user 'kkumut01' server 'umwsa28!bisam' bse '/software/baan/bse' boot '/software
/baan/bse/bin/ipc_boot6.1'

However when we try to login using the similar id as above in our production database server, it can go through.
For your information, prior to this, our engineer has rebooted the production application server which is due to some technical problems. Previously we did not encounter this problem at all and our users are able to login without any difficulties.

1) Is there any other ways i could check apart from the log files because the information gathered from the log files is quite meaningless and does not really help in rectifying the problem.

2) Can we check certain files(user files for eg.) or others which may be corrupted when we rebooted the server earlier. If there is where could we check and how do we perform the checking.

Thanks. Regards

Regards

Are you using remote users? I see the error error 2: no such file or directory. Could it be that you are missing the r<user> files?

Yes. We are using those remote users. But all the files for the remote users are there under the /lib/user directory and no one has removed those files or any of such.

When you say 'recreate users with other ID', do you mean recreate the remote user in Maintain Remote Users and have them use the same System User to login to the database server? Is there any pattern who can and cannot log in? (e.g. root, bsp, super users, normal users) etc. Have you changed any (system) passwords that may prevent users from logging in? Have you file/directory permissions?

My two cents:
What files are opened and what is the difference with succesfully logged on clients when running with the command box option:
-- -keeplog -logfile openfile.txt -dbgfdev

If you have only the option dialog box started, can you open a shell there? If so can you release your license with typing:
killall
exit

Will you be able to logon with the same user (is it sometimes failing or everytime) afterwards? Is it always and alone the same one user or not? What is the result of a diff between a succesfull loggin in persons rfile and ufile compares with someone who cannot login.

1) We created users (for eg. user that have problem loggin in - leett01), we create another ID for him - leett05 (both unix and baan).

We don't really have any pattern who can go in and who cannot. The thing happen intermittenly where by at one time the user can go in but the other users could not. So we would not know what seems to be the pattern.
Similar to bsp, sometimes we can go in and sometimes we could not even though there are enough licenses to go in. No, we have not changed any system password for users or the superusers.

2) The option dialog is opened when the user try to login, but it was opened for a while before it exits altogether. And we can also check that the user is able to occupy the licence for about ~10 sec then it exits without starting up the menu.

Its not always the same user can go in. Sometimes the user can go in at x time but could not at y time. Im not sure about the difference of the r file and u file between those who can and cannot login. Is there any way we could tell because i check the files are the same for those who can and cannot login.

Attached is the file (openfile.txt) for both users 'bsp' and 'pleong01'. At this time, 'bsp' is able to login but 'pleong01' could not. So maybe comparison can be made and check at which point the connection been terminated.

Attach is the file for bsp which can login at one time.