Hello,

Baan IVc4 SP24 - Red Hat 4 ES

I have just enabled Linux -> Win AD authentciation on our Baan server. For some users I am seeing errors with regards to audit files. see below

2008-05-21[17:02:10]:E:987428: ******* S T A R T of Error message *******
2008-05-21[17:02:10]:E:987428: Log message called from /view/port.6.1c.07.16/vobs/tt/servers/AUDIT/audit_dict.c: #435 keyword: check_audit_setup
2008-05-21[17:02:10]:E:987428: Pid 24444 Uid 639 Euid 639 Gid 125 Egid 125
2008-05-21[17:02:10]:E:987428: user_type N language 2 user_name 987428 tty ote locale ISO88591/NULL
2008-05-21[17:02:10]:E:987428: Errno 22 (Invalid argument) bdb_errno 0
2008-05-21[17:02:10]:E:987428: Log_mesg: make_dir failed for table tipcs020200 path /baan/bse/../audit/200/atipcs
2008-05-21[17:02:10]:E:987428: ******* E N D of Error message *******
2008-05-21[17:02:41]:E:987428:
2008-05-21[17:02:41]:E:987428: ******* S T A R T of Error message *******
2008-05-21[17:02:41]:E:987428: Log message called from /view/port.6.1c.07.16/vobs/tt/servers/AUDIT/serv_glob.c: #242 keyword: ATTACH_CURSOR
2008-05-21[17:02:41]:E:987428: Pid 24444 Uid 639 Euid 639 Gid 125 Egid 125
2008-05-21[17:02:41]:E:987428: user_type N language 2 user_name 987428 tty ote locale ISO88591/NULL
2008-05-21[17:02:41]:E:987428: Errno 0 bdb_errno 0
2008-05-21[17:02:41]:E:987428: Log_mesg: Table tipcs020200 has 32 audited columns but no audit DD !! Probably handle_ddinfo had failed
2008-05-21[17:02:41]:E:987428: ******* E N D of Error message *******


Now this is only for a small set of users. They have nothing different about there Baan login set-up. I have a local account on the Linux server and a Windows AD account.

It looks as if it could be a permissions problem of some type but I have checked the audit directory and permissions are set user=bsp, group=bsp, rw-rw-rw

I did have this issue once before for one person on a test box and the resolution was to disable Linux samba and winbind, login with local credientals, open the session, close session, re-enable samba and winbind and the problem disappeared. It's not practical to do this now so does anybody have an idea where I should start looking to resolve this?

I attach a screen shot of the error message for reference


Thanks

PJ

It would appear that the issue is down to the fact that we are using numbers for usernames. If i create a test account with letters I do not encounter the same problem.

Any ideas?