License troubleshooting for LANSA V11 and V12

Date:11 January 2010
Product/Release:LANSA V11 and V12
Abstract:Troubleshooting Licensing problems in LANSA V11 and V12
Submitted By:LANSA Technical Support
Last Review:October 2012

The LANSA license you have received is either a Server License Code(s) or a Software Key License File. Your LANSA License email notification states what type you have received.

Server License Code

This involves adding the license code you have received from LANSA Licensing to an existing license file in your LANSA environment. This type of LANSA licensing generally applies to server licensing, for example, LXX (SuperServer), DEV (IBM i Development), CXX (LANSA Client), WEB (Web execution).
Note:
The license you have received is only valid for the CPU that you have requested it for.

Software Key License File (including License Servers)

This is also known as softkey licensing and includes the License Server facility. Applying this license involves placing the Software Key License file in a designated location so that LANSA can read it. The file must follow the correct naming convention.

Note: The license you have received is only valid for the CPU that you have requested it for.

Select the License Type/Operating system combination where the invalid license error is being generated:


Server License Code on Windows

  1. Did you stop the LANSA listener (LCONNECT service) before you entered the license code? Have you restarted the LANSA listener (LCONNECT service) after you entered the license codes?
  2. Do you have multiple Visual LANSA systems on this PC? If yes, your V11 installation of Visual LANSA will search for and be directed to the x_lickey.dat file of an existing Visual LANSA configuration. This means that multiple installations of Visual LANSA on the one PC can share the same x_lickey.dat license file. The Server License shortcut in the V11 Visual LANSA installation will show which x_lickey.dat is being used.
    Note: If you wish your separate Visual LANSA installations to have separate x_lickey.dat license files (in the situation where the Visual LANSA installations require different licenses), then after requesting the license code(s) from LANSA Licensing, you will need to insert the new license code(s) in the x_lickey.dat file that is appropriate for the Visual LANSA installation you want to license and you will need to point the Visual LANSA installation to this version of x_lickey.dat. You should contact your local LANSA support group for instructions on how to do this.
  3. Double check that you have entered the license code correctly i.e. YYY0123456789ABCDEFGHIJKLMNOPQR (3 letter license type and 28 character license code; no spaces)
  4. The 3 letter license type must be specified in uppercase i.e. LXX, C05 etc.
  5. If you have a seat based license, have you exceeded the number of seats available for use?
  6. Have the CPU details changed since you generated the x_cpu details for the license you are trying to apply. For example, applying an O/S service pack, installing a new network card can affect the CPU details.
  7. Other possibilities would be detailed in the Support section of the LANSA Web site.
  8. If you are applying this license to a PC with multiple network cards, refer to the special considerations.

Server License Code on IBM i

  1. You must log in to the IBM i as either QSECOFR or the LANSA system owner to access the Licensing system
  2. If you have more than 1 version of LANSA on your IBM i, make sure that you are entering the license code into the correct LANSA system. (Tip: Qualify the LANSA license command with the program library of the system you wish to apply the license to eg. MYPGMLIB/LANSA LICENSE
  3. Double check that you have entered the license code correctly i.e. that you haven't mixed the characters, for example zero (0) for O or one (1) for I
  4. If you have a seat based license, have you exceeded the number of seats available for use?
  5. Other possibilities would be detailed in the Support section of the LANSA Web site.

Server License Code on UNIX/Linux

  1. Did you stop the LANSA listener (LCONNECT service) before you entered the license code? Have you restarted the LANSA listener (LCONNECT service) after you entered the license codes?
  2. Do you have multiple Visual LANSA systems on this PC? If yes, each Visual LANSA system with have an x_lickey.dat file to store license codes for that Visual LANSA system. Check that you have inserted the new license in the x_lickey.dat file that is appropriate for the Visual LANSA you want to license. (Tip: Using Windows Explorer, perform a search for x_lickey.dat and find the file that exists in the x_lansa directory in your chosen Visual LANSA installation. You can open the file directly from Windows Explorer to insert the license code)
  3. Double check that you have entered the license code correctly i.e. YYY0123456789ABCDEFGHIJKLMNOPQR (3 letter license type and 28 character license code; no spaces)
  4. The 3 letter license type must be specified in uppercase i.e. LXX, C05 etc.
  5. If you have a seat based license, have you exceeded the number of seats available for use?
  6. Other possibilities would be detailed in the Support section of the LANSA Web site. 

Software Key License File on Windows

Note: A software key license file on Windows can be used to license either a Visual LANSA development environment or a LANSA Integrator system.

  1. Does the software key license file have the correct naming format. The correct name is lansakey.txt
  2. Re-check that you have copied the lansakey.txt file to the correct location on your PC. The correct location depends on whether the software key license file is storing a Visual LANSA development license or a LANSA integrator license.
    - A Visual LANSA Development (VLW & VLD) software key license file should be located in the same directory as the LANSA.EXE file. Example file location: c:\program files\LANSA\LANSA\lansakey.txt.
    - A LANSA Integrator softkey license files should be located in the jsm instance system subdirectory. Example file location: \jsm\instance\system\lansakey.txt 
  3. In LANSA Integrator Studio, take the License check menu option. The License check option connects to the server and opens a dialog showing your current Integrator license, and which features are licensed.
  4. Do you have multiple installations of LANSA? If yes, the software key license file may have been copied to the incorrect Visual LANSA development environment or LANSA Integrator system.
  5. Have the CPU details changed since you generated the x_cpu details for the license you are trying to apply. For example, applying an O/S service pack, installing a new network card can affect the CPU details.
  6. Do you have the latest EPCs applied to your LANSA system? Refer to www.lansa.com/support/notes/epc.htm for the latest LANSA EPCs.
  7. Other possibilities would be detailed in the Support section of the LANSA Web site. 
  8. Are you applying this license on PC with multiple network cards? If yes, refer to the special considerations

License Server on Windows

Note: A License server can only be used on Windows to license a Visual LANSA development environment.

  1. The x_cpu must be obtained from the CPU that is nominated as the dedicated license server. This is also the CPU that the license is applied to.
  2. Does the software key license file have the correct naming format. The correct name is lservrc (no extension)
  3. Re-check that you have copied the lservrc file to the correct location on your license server. The correct location is where the license server service is installed. The default is c:\Program Files\lansa\SentinelLM
  4. Have you stopped and restarted the license server service (Sentinel RMS License Manager) in Windows -> Services after copying the new lservrc license file to the correct location?
  5. Have the CPU details changed since you generated the x_cpu details for the license server? For example, applying an O/S service pack or installing a new network card can affect the CPU details.
  6. The VLN license is seat based. If you are generating a message that all the licenses are already in use by other developers, you might need to consider obtaining extra seats.
  7. Do you have the latest EPCs applied to your LANSA system? Refer to www.lansa.com/support/notes/epc.htm for the latest LANSA EPCs.
  8. Other possibilities would be detailed in the Support section of the LANSA Web site.
  9. Are you applying this license on PC with multiple network cards? If yes, refer to the special considerations

Software Key License File on IBM i

  1. Does the LANSA Integrator license have the correct naming format. The correct name for the LANSA Integrator license file is lansakey.txt
  2. Re-check that you have copied it to the jsm instance system subdirectory on the IBM i IFS. Example file location: /jsm/instance/system/lansakey.txt
  3. Do you have multiple installations of LANSA? If yes, the license file may have been copied to the jsm/instance/... for the incorrect LANSA Integrator system
  4. Do you have the latest Integrator EPC applied to this LANSA Integrator system? Refer to www.lansa.com/support/notes/epc.htm for the latest LANSA Integrator EPC level.
  5. Other possibilities would be detailed in the Support section of the LANSA Web site. For example, refer to Invalid license error caused by jsmrfi.jar in WebSphere for a possible LANSA Integrator license issue.

Software Key License File on UNIX/Linux

  1. Does the software key license file have the correct naming format. The correct name is lansakey.txt
  2. Re-check that you have copied the lansakey.txt file to the jsm instance system subdirectory. Example file location: /jsm/instance/system/lansakey.txt
  3. In LANSA Integrator Studio, take the License check menu option. The License check option connects to the server and opens a dialog showing your current Integrator license, and which features are licensed.
  4. Do you have multiple installations of LANSA? If yes, the license file may have been copied to the jsm/instance/... for the incorrect LANSA Integrator system
  5. Do you have the latest Integrator EPC applied to this LANSA Integrator system? Refer to www.lansa.com/support/notes/epc.htm for the latest LANSA Integrator EPCs.
  6. Other possibilities would be detailed in the Support section of the LANSA Web site.

Special Considerations

When running x_cpu.exe on a PC with multiple network cards, the x_cpu utility will recognize that multiple cards are present and will request the user to select a card as the 'primary network card'. This network card must always be present for LANSA licensing (both Software Key and Server Codes) to work. The non availability of this primary network card will disable the LANSA licensing on this PC.