I am getting above error while prining RSC. I have checked the host name in licence6.1 file, it is matching with the host name of server. I have also tried with IP address in licence6.1 file but no luck. The server is available on network. I can log in Baan.
details are as
H/w is IBM net server 250 with windows 2000, baan4c4 with DB2 v5 as database.
Regards,
Atul

By "printing RSC" you mean licensing the server?
Looks like a permission problem.
Check the ownership of the brand file and see if your current user is able to write into it.

no permission problems to brand.exe file in $BSE/bin directory and baan6.1.lic file is not yet created as this is fresh installation.
What else can be problem ?
Regards
Atul

Atulk, is your path set to $BSE/bin? This error occurs, if your path is not correct. Don't call $BSE/bin/ba6.1 but change your path, so that you can call ba6.1 from whereever you are.

Gerhjard, this is an NT system... I'm more used to UNIX than NT now, anybody with more experience with NT to help this one out?

Atulk, you mentioned that you can login into Baan, do you get any message at all when you login?

We could not understand your problem. You said you have Windows 2000, and then you are talking about "brand6.1" which is only for UNIX !!! Then you are talking about "C:\winnt\baan6.1.lic" which is related to Windows instalation. (this is OK).

Please make yourself clear. Otherwise you will receive answers regarding Baan Ascii - ba6.1..... (Take care of / and \...)

You are right with baan6.1.lic, since you haven't reached the step "Validate Tools Set" which creates this file. The file licence6.1 seems to be OK.

Make sure you have set properly the system environment variables BSE and BSE_TMP. It is also good to have
f:\baan\bin (as an example) in your path, although this is not mandatory.

In $BSE\bin there are some executables (like hostid.exe, I remember) which are "responsible" of generating the security key. Maybe you do not have this file.... A good idea would be to reinstall the porting set, to be sure you have all files. Save $BSE\bin as $BSE\bin.old - do a "copy", not a "rename".

There should be no other "secrets".