hi, i'm licencing my baan production env. but, when i executed ttiex3400m000 "Print Requested System Configuration" I got an error, "Error while calling brand6.1, can not print security code". i think that this file is corrupted, but i don't have a backout for this file... what should i do?? i need to renew my licence because it will expire on next 02/17

Is there any additional information in the log files under $BSE/log?

Check your $BSE/bin/brand6.1. Check permissions and ownership.
# ls -la brand6.1
-rwxr-xr-x 1 bsp bsp 583513 15 okt 2004 brand6.1

jclju1 is right. The permissions need to be right.

If you really feel that the .brand file is corrupt, the last option might be to revalidate the tools set and regenerate the .brand file. Then you can try printing RSC again. Of course, please take a backup before "trying" anything at all.

Good luck.

I'm not sure, but I think I know what the problem is, months ago, I had problems to start baan,
but I can't remember exactly what the error was... the thing is that I had to change /usr/baan/bse/lib/licence6.1.
this file had the hostname, "Baanpro", I changed it and put the IP number. and I finally could start baan...
Everything was ok until now, that the "security key" can't be printed. I checked out the log files, for example the "log.brand6.1" and it said = ' Baanpro`not listed in /usr/baan/bse/lib/licence6.1

What can I do??

Open the licence6.1 file and add Baanpro along with the IP.

So the file should look something like this:

Baanpro, 10.10.10.10

(Substiture the IP with the correct one)

Let us know if it worked.

but can I do this while baan is up?? or should i get down baan first?? how is the licence6.1 file generated??

thanks for helping..

This file is set when Baan is first installed and licensed.

You don't have to shutdown Baan but it might be better to do this when there are no active transactions. Also, block the jobs from firing before changing. The reason is that it might generate a license error and throw the users out. Ideally it shouldn't because you have the IP address in there as well, but don't take any chances with production system.

So make sure there are no active users, login into Baan first as 'bsp' or a super user and then change the file.

Retry the Print RSC.

Remember to take a backup of any file/directory that you are changing.

A couple of things.

First: your error is around the brand6.1 binary.

Can you run it from the command line? brand6.1 -U should give you usage. (we're just verifying if the brand6.1 actually works, so if that prints out the usage then you're set.)

Second: Don't touch your .brand file at all, Baan uses the inode of the file to ensure security. copying it, backing it up, restoring it will switch the inode and make the file invalid.

Third: Are you running this as bsp or root? The licensing process is kind of a dance, there is a quickguide to take you through it on the Baan support site, I'd recommend following that to the T.


I'd be careful messing with your license6.1 file. it's easy to change but I wouldn't recommend adding a hostname and the ip for that hostname there.
Just use one or the other.

If your baan server is called Baanpro and you can "ping" that name and have it return your server from that box, then that is fine. Otherwise use the IP address.

Also what does the output of licmon6.1 -B or licmon6.1 -b (I don't have it in front of me) should print out your brand info.

Dave

licmon6.1 -B is command

licmon6.1 -B is command

Hello,

jclju1 is right. The -B option shows the shared memory anf file information !


Usage: licmon6.1 [-vVdbBwkusc][-h host][-p num]
-v : show version
-b : show brandinfo
-B : show brandinfo from brandfile and shared memory
-C : clear brandinfo from shared memory
-w : show users
-W : show other connections
-a : show all connections
-p [num] : check connections (ping)
-k : kill server
-u : show usercount
-s : show statistics
-c : cleanup orphaned local licences


Regards

i executed licmon6.1 -b and licmon6.1 -B, and I noticed that in "Machine ID" the numer of the machines, start with (-) for example, -4556839, and in "servers" is empty...

what if brand6.1 doesn't work?? what do i have to do then? the comand if brand6.1 -U???

sorry... when i executed licmon6.1 -B,

this file prints the next information=

# licmon6.1 -B
Brand information from brand file:
Organization : XXXXXXXXX, Inc.
Cust. code : 999999
Licencenr. : 999
Options : 0202041
Ba users : 1
Bx/bw users : 38
Start date : 17-02-2009
End date : 17-02-2010
Machine id : -971138765
Servers : baanpro
Brand information from shared memory:
Organization : XXXXXXXXX, Inc.
Cust. code : 999999
Licencenr. : 999
Options : 0202041
Ba users : 1
Bx/bw users : 38
Start date : 17-02-2009
End date : 17-02-2010
Machine id : -971138765
Servers :

______________________________________________________________

as you can see, in the shared memory information, doesn`t have de server name... why is this??

thankyou all so much for helping...

i think the machine id is ok.

i'm guessing that there was no license6.1 file when you started licd6.1.

i'd recommend putting baanpro back into your licence6.1 file (as the only entry)

if you can't ping baanpro from the commandline, of it takes you to a place that isn't your machine, then you should update your /etc/hosts to reflect that.

(assuming that your hostname really should be baanpro)

then try your licensing again.

Dave

ok dave, but, can I change the licence6.1 file, while baan is up?? or should I shut it down first? because, if after i change licence6.1 baan can't start, i wont be able to licencing and repair the damage... because that's what happened before, i could not start baan, i could not login baan in anyway.... this is a little confusing.. because i've never had this error before.. and I'm messing with baan production.

Thankyou dave

When you make the change, then any new logins will be affected by the change (existing ones shouldn't be affected)

so in your case - you should probably make the change after hours.

if you can ping baanpro from the command line and the IP is your baan server then you should be able to log in just fine.

Dave