We are migrating our BaaN IV c4 installation to a new machine with W2003 and BaaN IV c4 and SQL Server 2005.

We are having trouble generating the BaaN users.
They only work if the user is generated as a local user in the server, with domain users we get the message "Error 514. Probably no permission ......."

The strange thing is that if we go to file msql_users in /baan/lib/msql and I look for the line of a specific user i.e user karvil, it says something like "karvil:karvil:*Ewapkx#A'IiH/H5IYK+\~QJia#e+vV&:baandb" .
If I ichange it to "KARVIL:karvil:*Ewapkx#A'IiH/H5IYK+\~QJia#e+vV&:baandb", that is, change the first code to capital letters, it works OK and I can get into BaaN normally.

Has anyone got any idea why this is happening?

Did you upgrade portingset? I noticed that new portingsets make differences between small and capital letters.
There were some cases that after portingset upgrade customer had to change OS user on Windows form "Baan" to "baan" to resolve such error. Anotehr way is probably what you did - to change line in xxx_users file from "baan:baan:..." to "Baan:baan:..."

There was problem with capital letters in login names created around portset 6.1c.0714 or 15, I think. Certainly by portset 0717 the issue was clear. (Do not run portsets 0718 or 0719 on a Windows platform, there is a fault.)

The user is probably created in the domain with capitals. Change it to lowercase and it will work. Had the same problem.

Regards,
Han

Han

Indeed, it probably will. But all our AD user names include capital letters, and in the Baan User Maintenance the System Login is shown in lower case. This arrangement works fine (except when you get a porting set error, as we had recently). Of course, we are a Windows shop - different rules may apply for Unix servers.

Hi all, thankyou for all the answers. The problem solved when upgrading porting set from 6.1c.0713 to 6.1c.0717.

cheers