danielv
5th August 2004, 20:57
Installed second NIC on my test server and invalidated licensing service.
The first original NIC is still on the server
Do I need to ask for new license keys or can I use the old ones?
If I can use the old ones, what steps do I need to take to validate server again?
The OS is W2K, SP15, MS SQL Server 2000
Any help would be appreciated
thanks
Daniel
dave_23
5th August 2004, 21:34
If the original NIC is still there you can try changing the binding order of your
network cards, if the new one is bound first, then baan will try to license off
of that..
If you can switch those, then you won't need to do anything to revalidate.. if you cannot then you'll have to revalidate using the new nic card.
Dave
danielv
5th August 2004, 22:24
Thanks,
changed binding order, with no luck.
Probably I changed the security key..
I did run Patch Objects after system crash...
Any other ideas?
thanks
dave_23
6th August 2004, 00:07
If you ran patch objects after system crash, you need to run "Configure App"
with the license daemon up.
Dave
Darren Phillips
6th August 2004, 00:38
The binding makes no difference the security key is calculated by using the mac address of all cards in the machine. If you take the new card out and use the brand.exe from the command line (there are other posts on the board covering how to do this)
http://www.baanboard.com/baanboard/showthread.php?t=15861&highlight=brand.lic
this will regenerate the brand.lic file
danielv
6th August 2004, 00:56
Darren,
thank you !, I took out the second NIC, restarted server and licensing server started again.
Now, what do I need to do to add second NIC?
Is it possible?
thanks again
dave_23
6th August 2004, 01:10
Glad that did the trick for ya Daniel. But I have to disagree with Darren.
If you're running NT and you have 2 NIC cards and switch the binding order, the license daemon will fail. If the license file was created using all of the MAC addresses then this wouldn't happen.
My guess is that if you switched the binding order and made the old NIC primary and rebooted the system should have come back up.. Then you'd run Configure App since you had run Patch after system crash...
But, that's just how I understand it.. and I've been wrong before..
Dave
danielv
6th August 2004, 01:17
Darren,
so from what I understand, if I add the second NIC I will need to generate another security key and validate it?
Dave & Darren Thank you both for your help... I learn something new every day... :-)
danielv
6th August 2004, 01:24
Dave,
when the security key was generated about a year ago, I did not had the second NIC...
Just recently I decided to add the second NIC ...
dave_23
6th August 2004, 02:53
Dave,
when the security key was generated about a year ago, I did not had the second NIC...
Just recently I decided to add the second NIC ...
So according to my understanding .. you would just have to make sure the 2nd NIC wasn't the primary (and then reboot).. then you'd be all set...
Dave
danielv
6th August 2004, 05:19
Dave
Added second NIC and checked binding order.
It did not work.
It looks like the Security Key is calculated based on all NICs available. What I have been reading this is only for NT/W2K. Unix is a different beast
thanks
Daniel
dave_23
9th August 2004, 15:46
Spoke with a friend in Baan development..
It is not calculated based on all available NICs, just one.
But he pointed me to some solutions that may help:
131733, 113902, 111736
Good luck!
Dave
Darren Phillips
10th August 2004, 02:31
This is taken from a baan document it indicates otherwise.
1 - Basics on Licence Server
############################
1.00 - Documentation
====================
Quick Guides :
Sol. # 1696 - QG1807 - How to Handle a License That is About to Expire.doc
Sol. # 1797 - QG1801 - How to Validate a Single Host (4.0a).doc
Sol. # 1798 - QG1802 - How to Validate a Single Host (4c)-NT.doc
Sol. # 1798 - QG1802 - How to Validate a Single Host(4b-4c)-Unix.doc
Sol. # 1799 - QG1803 - How to Validate Hosts in a Network.doc
Sol. # 1800 - QG1814 - Re-Licensing a New Server After a Hardware Failure.doc
Sol. # 1801 - QG1815 - Re-Licensing After Failure of Root Drive.doc
Sol. # 1802 - QG1816 - Re-Licensing After Failure of CPU or NIC.doc
Sol. # 3572 - QG1818 - BaanERP Validation Guide.doc
Sol. # 3814 - QG1819 - Licensing and Validations (FAQs).doc
Standard docs :
U7045AUS BaanIV cx - Install on Microsoft Cluster Server.pdf
U7123AUS BaanERP - Install on Microsoft Cluster Server.pdf
Hewlett-Packard documentation :
http://docs.hp.com/hpux/ha/
http://www.hp.com/go/ha
http://docs.hp.com/servlets/iknow/iKtypeA
1.01 - Terms, Definitions
=========================
BSE - Baan Software Environment.
Designate two things :
* a runnable instance of the Baan software
* The environment variable that points to the root directory
where this instance is installed
VRF - Validation Request Form --> Fill in by customer
LCI - Licence Code Information <-- Provided by Baan CS&S
CUNO - Customer Code (six digits) <-- Provided by Baan CS&S
LICO - Licence Code (3 to 5 digits) <-- Provided by Baan CS&S
SEQN - Sequence Number (1 digit) <-- Provided by Baan CS&S
SK - Security Key --> Generated by customer
VKtools - Validation Key (Tools) <-- Provided by Baan CS&S
VKsoft - Validation Key Software (Standard) <-- Provided by Baan CS&S
NODE - Designate a machine running the Licence Server program (LICD)
Hostname - Name of the machine, defined at OS level.
Hostid - Unique number identifying the machine, defined at OS level.
On Unix machines, the hostid is retrieved from the motherboard
of the computer.
On NT machines, it is a computation (?) of the MAC addresses of
all installed network adapters.
dave_23
10th August 2004, 03:49
I like the (?) in that one.
Seems like its pretty unclear, even internal to Baan, different answers
coming from all over the place.
Dave
danielv
12th August 2004, 01:19
did not work.
Let me just say that I did not go through the exercise of re-validating the server.. Just tried solutions 131733, 113902. Did not tried sol 111736, since it asked to re-validate.
One test that came up with positive results was that I disabled the second NIC and restarted licensing service. After that I was able to enable second nic.
So, looks like re-validating is inevitable after adding a second NIC