- Show Remaining Articles ( 36 ) Collapse Articles
BBj ODBC Driver
BASIS ODBC Driver (pre-BBj)
- Show Remaining Articles ( 31 ) Collapse Articles
- Show Remaining Articles ( 68 ) Collapse Articles
BBj Enterprise Manager
BASIC Web Utility
- Show Remaining Articles ( 40 ) Collapse Articles
- Show Remaining Articles ( 226 ) Collapse Articles
PRO/5 Data Server
- Show Remaining Articles ( 25 ) Collapse Articles
TAOS: The Developers Workbench
- Show Remaining Articles ( 101 ) Collapse Articles
00768: Troubleshooting Novell BLM Configuration issues
Troubleshooting Novell BLM Configuration issues
The following errors typically occur if a step is missed in the Installation / Configuration of the Novell BLM and PRO/5:
* FLEXlm errors -14, -15, -17 when trying to invoke Visual PRO/5.
* Message “can’t find the license.dat file” when LOADing the Basis.NLM on the Server
Here are some tips on troubleshooting the FlexLM errors under Novell:
1) When installing the BLM, you are prompted to go to the Novell Console and type:
Write down the FIRST network card node address. This is the HOST ID, be sure to verify for accuracy. This will become part of the permanent license file. If this is incorrect, you will need to know what the correct HOST ID is (FIRST network card node address) and request a new license file via the registration process.
2) Verify that the license file is named using the 8.3 naming convention since it will be used in the NLM load line. Here is an example of a typical load line from a Novell console prompt:
load basis -l sys:\basis\blm\blmgr.txt -c sys:\basis\RO555555.lic; RO555556.lic <CR>
To start the BLM automatically when rebooting the Novell Server, modify the AUTOEXEC.NCF file to include the above load line. Make sure the license file is named in 8.3 format (RO555555.lic) The *.lic file can reside anywhere on the Novell Server as long as you point to the correct path the .lic file resides in.
Optionally, the BLM may be started manually by typing this line at the Novell console prompt.
No reboot of the Novell server is required with a manual load of the BASIS.NLM.
Note: The NLM may be unloaded by typing the following at the Novell console prompt:
Here is an example of a permanent license file under Novell:
SERVER this_host 00508B440ADF SPX:9961 TCP:27000
FEATURE PRO5_DEV basis 2.10 permanent 25 31276ED44AD7 HOSTID=ANY ck=154 SN=PRO555555
3) Installing the VPRO/5 client will create a basis.lic file (Basis pointer file). The basis.lic file resides in the VPRO/5 directory and is a different file from the license file that is created for the Basis License Manager (BLM) outlined above. Select IPX/SPX during the client (VPRO5) install when prompted. The install will prompt the user to go to the NOVELL server console and type:
Write down the IPX internal network number. Verify this number for accuracy. It is a different number than the first network card node address mentioned above but equally important. At the VPRO/5 install screen, type this number into the field provided.
This file may also be created after the initial install by the following steps:
START>PROGRAMS>VPRO5 REV 2.11 >Install a BASIS License.
If the VPRO/5 was a Network Install:
Map a drive to the Novell server from the workstation. This can be done from Windows Explorer. In the Novell directory where VPRO/5 is installed, double click on REGLIC.EXE.
‘Configure this application to use the BASIS License Manager’;
Click on NEXT;
Follow the steps above to get the correct IPX internal network number.
Verify that IPX/SPX was selected during the VPRO/5 install by looking at the basis.lic. Here is an example of a IPX/SPX basis.lic file (pointer file):
SERVER hotel42 ANY SPX:9961@000000000001#376acc3d
Note: the IPX/SPX internal network number is at the end of line one, i.e. #376acc3d.
If they are setting an Internal Network Number in the autoexec.ncf file ensure that the internal network number being used in the basis.lic file is the number returned from typing config at the Server’s Console and NOT the number defined in the autoexec.ncf file.
(Also, ensure that there are 11 zeros the # sign and then the internal network number.)
If TCP/IP was inadvertently selected the ‘instllic’ program will have to be run, this is the program that allows the selection of IPX/SPX or TCP/IP.
4) Next, in the Control Panel Network Applet, under Configuration / IPX/SPX Protocol Properties, verify the ‘Frame Type’ selected is the same as the ‘Frame Type’ selected on the Novell Server, i.e 802.3. This information is located under the Properties of IPX/SPX in the workstation’s Network Applet from the Control Panel
Ensure that ‘Auto Frame Type’ is not selected on the workstation. To find out the ‘Frame Type’ needed on the workstation, go to the Novell Console and type
: load INETCFG
select protocols / select IPX/SPX / select Bindings Options
then go down until you find ‘Frame Type’
Ensure that this type matches the Workstation Frame Type selected under the IPX/SPX Properties and that ‘Auto Frame Type’ is not selected.
If you are still having problems connecting tothe Novell server, you may need to re- install or update the NIC card drivers
5) When you are running IPX/SPX, you will see a SPX:9961 port # being specified in all license files. This is a port selected by our engineering staff, there is a remote possiblity that other vendors may be using that port number and therefore not allowing the VPRO5 clients to connect to the BLM to checkout a license. To rule this possibility out, you can change the 9961 number to any other 9000 port number such as 9861, for example, and see if that SPX port # allows a connection to the BLM. You will need to change this in all .lic files including the basis.lic file.
Please note that the @000000000001 portion of the BASIS.lic file is created by VP5 when you run the Install a License from Visual PRO/5.
Last Modified: 07/24/2002 Product: Visual PRO/5 Operating System: Novell
BASIS structures five components of their technology into the BBx Generations.