Sector7 Licensing
I'm having problems recognizing the Ethernet device on my system
What is the format of the license file?
Where should the license file be created?
Troubleshooting Error Messages
I'm having problems recognizing the Ethernet device on my system
The license manager contains it's own table of Ethernet devices for different systems. It may be that the device used by your system is not in this list (we do update them regularly). If this is so, then it will be necessary to set the environment variable S7_NETDEV to the path/filename of the device; e.g.
- setenv S7_NETDEV "/dev/ln0" C-shell
- S7_NETDEV="/dev/ln0"; export S7_NETDEV Bourne-shell
If you do not know the path/filename of the device, netstat –I will display it for you. It may also be necessary to set the permissions of the device to 666 using chmod(C).
System Ethernet Device Digital qe0 qe1 se0 se1 de0 de1 ni0 ni1 ne0 ne1 ln0 ln1 te0 te1 tu0 tu1 HP /dev/lan0 /dev/lan1 IBM /dev/sock /dev/net0 /dev/net1 /dev/tok0 /dev/tok1 /dev/ent0 /dev/ent1 Sequent /dev/enet/eg0 /dev/enet/eg1 /dev/enet/eg2 /dev/enet/eg3 /dev/enet/se0 /dev/enet/se1 /dev/enet/se2 /dev/enet/se3 SCO Unix /dev/e3A0 /dev/e3B0 /dev/e3C0 /dev/e3D0 /dev/e3E0 /dev/net0 /dev/net1 /dev/sme0 /dev/wdn0 /dev/wdn1 /dev/zxe0
What is the format of the license file?
There are two different formats, depending upon the platform on which you are working. The license manager relies on the file S7.license , or in the case of SCO Unix without an Ethernet adapter, s7.license. The components of each line in the license file is separated by a single space character, and there is a line entry for each software component that is to be licensed:
Product The code used to identify components of the software to the license manager.
System ID The code used to uniquely identify the system for which the software will be licensed.
expiration Date The license will cease to operate after midnight on the date shown. If set to 00 00 0000, there is no expiration date. Note this is in the form DD MM YYYY.
Users The number of consecutive users for which the software is licensed. If set to 0 (zero), there is no limitation set by the license manager.
SCO-Info serial#NumCPU#Users from SCO Unix system. This information can be ascertained by running ' uname -X'.
License Key The key used to enable use of the appropriate license. Note that the $ symbol is part of the key, and must be specified in the file.
S7.license
<Product> <System ID> <DD MM YYYY> <Users> <License Key>
BP/BASIC 00 00 00 00 00 00 10 05 1999 32 $8011218CDC2As7.license
<Product> <System ID> <DD MM YYYY> <Users> <SCO-Info> <License Key>
BP/BASIC 00 00 00 00 00 00 10 05 1999 32 xyz005081#1#unlim $8011218CDC2AWhere should the license file be created?
Under normal circumstances it would reside in /etc (or in the main Windows directory for Windows®), and have permissions of rw-rw-rw, to allow access by all users on the system. It can be created manually with a regular text editor such as vi/notepad using the information supplied on the Run-Time License Schedule supplied by Sector7.Troubleshooting Error Messages
The messages shown below may be displayed if an error occurs while verifying the license for a Sector7 licensed product.
Symptom The product exits with "<product>: License Failure: (1) Unable to Open Sector 7 License File" Cause The licensing mechanism has been unable to open the license file. This could be because the file does not exist, the filename is incorrect, or the permissions of the file are incorrect. Solution Check that the license file is in the correct directory location and that it has the correct name. Note the case dependencies of the two different Unix versions. Also check that the permissions are correct.
Symptom The program exits with "<product>: License Failure: (2) Error Reading Sector 7 License File" Cause An error occurred whilst reading the license file. This could be due to corruption, or an incomplete entry. Solution Check the contents of the license file for any form of corruption.
Symptom The program exits with "<product>: License Failure: (3) No License for This Product" Cause An attempt has been made to run a Sector 7 licensed product for which there is no entry in the license file. Solution Contact Sector7 to obtain and install license keys for product.
Symptom The program exits with "<product>: License Failure: (4) No License for This Product" Cause An attempt has been made to run a Sector 7 licensed product for which there is no entry in the license file. Solution Contact Sector7 to obtain and install license keys for product.
Symptom The program exits with "<product>: License Failure: (5) License Checksum Failure" Cause The System ID in the license file is set to all zeroes, and with no expiration date specified, the license is deemed invalid. Solution Contact Sector7 to obtain and install correct license keys for product.
Symptom The program exits with "<product>: License Failure: (6) Ethernet Addresses do not Match" Cause The System ID in the license file does not match the one obtained from your system. Solution Obtain the correct System ID and contact Sector7 to obtain and install correct license keys for product.
Symptom The program exits with "<product>: License Failure: (7) License Checksum Failure" Cause There is no ‘$’ preceding the license key for the specified product entry in the license file. Solution Edit the license file and insert the $ character before the license key for product.
Symptom The program exits with "<product>: License Failure: (8) License Checksum Failure" Cause The length of the license key for the specified product entry in the license file is incorrect. Solution Edit the license file and check that the license key for product is entered as supplied by Sector7.
Symptom The program exits with "<product>: License Failure: (9) SCO License System Failure" Cause On a SCO Unix system without an Ethernet card, the System ID in the license file does not match the one obtained from your system. Solution Obtain the correct System ID and contact Sector7 to obtain and install correct license keys for product.
Symptom The product exits with "<product>: License Failure: (A) License Checksum Failure" Cause The licensing mechanism has been unable to read the System ID from your system, and with no expiration date specified, the license is deemed invalid. Solution Check to see if the gid program is working correctly. If it does not return a valid System ID, it could be that the license manager is not detecting your Ethernet adapter. Check the table and above and use S7_NETDEV appropriately.
Symptom The program exits with "<product>: License Failure: (B) License Date Expired" Cause The license key for the specified product entry in the license file has an expiration date that has now expired. Solution Please contact Sector7 for a new license key.
Symptom The program displays "WARNING - < product > License Expires in n Day(s)" and continues operation. Cause The license key for product in the license file has an expiration date that will expire in the specified number of days. This message will be displayed 5 days prior to expiration of the key and every day thereafter. Solution Please contact Sector7 for a new license key.
Symptom The program displays "WARNING - < product > License Expires at Midnight" and continues operation. Cause The license key for product in the license file has an expiration date that will expire at midnight today. Solution Please contact Sector7 for a new license key immediately.