Hey there,

we installed Baan ERP on a Windows 2003 Server in combination with an Oracle database und transfered the data from an older computer on this new machine.
After that no user execept our admin user is able to access the baan environment. What's wrong?
Thanks for your help
Sören

Hi,

You have transferred the data from an older machine to new one and admin can access BaaN means there is no issue related to connectivity.

The symptoms shows, it could be problem of permission. Please check user permission. Also check/post event viewers message. So that it helps to understand/diagnose your problem better.

Regards,

-Suhas

Please also check if , in Windows 2003, u have defined user in administrative group ???

making user the member of adminitrator, will solve the problem

Deepak

W2003 has some more restrictions than W2k, which makes Baaninstallations a little bit more difficult. In my point of view it is not advisable to make all users member of the admin group. Create a new group like 'baanuser', make all baan users member of it and give them permission on the baan and oracle directories.

Thanks for your replies. !
Putting the users into a local admin group on the server works. But putting the users into a non admin group with permissions on the oracle and baan doesn't work.. But I don't think that it is a good idea to put all baan users into an admin group. Is there another solution?

At least the BaanIV gui uses rexec to connect to the baan server and therefore all Baan users need the "local log on" policy right. This is most likely the same for BaanERp and Win2003.

Hi Soeren

You can create a new group and put the users in that group but the same group should have a rights of administrator.

It is a weird idea to make all Baan users to local administrators on a server. I guess most Windows administrators would object to this. There must be a better way of doing this!

1. you must add the Baan users group to the "Allow Local Logon" Policy in Win 2003 Server
2. Set read/write permissions for the Baan users to the BSE directory (D:\Baan or whatever) . I don't know why this is needed, but it seems that the Baan application access the application files under the users permissions.

This worked for us on BaanIVc2. I think for BaanIVc4 only the local logon policy is needed.

1. you must add the Baan users group to the "Allow Local Logon" Policy in Win 2003 Server
2. Set read/write permissions for the Baan users to the BSE directory (D:\Baan or whatever) . I don't know why this is needed, but it seems that the Baan application access the application files under the users permissions.

This worked for us on BaanIVc2. I think for BaanIVc4 only the local logon policy is needed.

I'm sure there are some guidelines available from Infor, but from the top of my head I would say we can narrow it down a bit as follows (coorections welcome):

- collect baan users in a baan group
- baan group needs read rights in $BSE
- baan group needs execute rights in $BSE/etc in order to log on
- baan group (probably) needs execute rights in $BSE/bin
- baan group needs read/write permissions in $BSE/tmp in order to print, sort and logon
- baan group needs read/write permissions in $BSE/log (for logging obviously)
- baan group needs read/write permissions in $BSE/audit (for auditing)

For security's sake: NO execute rights in tmp, log and audit. NO write permissions in lib/users.