License troubleshooting for LANSA V13

Date:13 December 2012
Product/Release:LANSA V13
Abstract:Troubleshooting Licensing problems in LANSA V13
Submitted By:LANSA Technical Support

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(s) notice will look like the following:

  • Attached please find ...
    - Server license - x_lic_170A_1DD2557A_0_0000077395.xml

A Software Key License File notice will look like the following:

  • Attached please find ...
    - Key license - lservrc_170A_1DD2557A_0000002021.txt


Server License Code

Server licensing involves adding the license code you have received from LANSA Licensing to your LANSA system

  • via the Licensing - Server Licenses shortcut in the LANSA folder on windows.
  • via the <pgmlib>/LANSA LICENSE command in QCMD on IBM i.

This type of LANSA licensing generally applies to server licensing, for example, LXX (SuperServer), DEV (IBM i Development), CLT (LANSA Client), WEB (Web execution).
Note:
The license you receive 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. In V13, LANSA Integrator licensing is no longer via Software Key Licensing.
Note:
The license you receive is only valid for the CPU that you have requested it for.


Select License Type

Click on the License Type/Operating system combination where the license issue is being encountered:


Server License Code on Windows

The two possible points when you may encounter a LANSA license issue are when applying the license or at runtime, when excuting the LANSA product/feature that is using the license. The following checklist works through both possibilities.

  1. Does the problem license code appear as valid in the LANSA License facility? Open the Licensing - Server Licenses facility from Settings and Administration in the Visual LANSA folder. Review the license codes in the Existing tabsheet and ensure the license is listed and is valid. All licenses that have been applied will be listed whether they are valid or invalid or expired. You can use the Description column to see what LANSA Product or feature the license codes refer to.
  2. If the problem license code is not listed, you may have never applied it. Did you click the Apply All or Apply Selected button on the New licenses screen? You should review the steps in Applying a license to LANSA V13 to apply the license.
  3. If the license code is listed but invalid or expired, you should request a new license from your local LANSA Representative.
  4. If no licenses are listed at all on the Existing screen, its possible that your encrypted license file is missing or has been corrupted. The encrypted license file in V13 is of the form x_lic_<model>_<cpu> (with no file extension). You should reapply all your licenses from the XML files sent to you from LANSA Licensing, using the steps in Applying a license to LANSA V13. Note: You cannot reapply expired licenses as the Apply buttons will be disabled.
  5. If you no longer have your XML files for valid licenses, you should contact your local LANSA representative to get them re-issued.
  6. If you have expired licenses, you should contact your local LANSA representative to obtain valid licenses.
  7. If you have multiple Visual LANSA V13 configurations on your PC, all licenses applied will display in the License facility of all your configurations. Once you have applied licenses to the first configuration, a central licensing location will be created and will be available across all your your configurations. If you encounter a situation whereby licenses are listed in the License facility of one V13 configuration but not another one on the same PC, you should contact LANSA Support for further instructions.
  8. Some server licenses (for example, LANSA Client CLT code) require the LANSA Listener to be stopped and restarted to be initialized. 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?
  9. Do you have the correct license for the product or feature you are executing? For example, you need an LXX (or seat based equivalent) on the server to execute a LANSA superserver application to a Windows server or an IBM i server.
  10. If you have a seat based license, have you exceeded the number of seats available for use?
  11. 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. In these situations, existing licenses will appear as invalid in the Licensing - Server Licenses facility.
  12. Other possibilities would be detailed in the Support section of the LANSA Web site.
  13. If you are applying this license to a PC with multiple network cards, refer to 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 LANSA Licensing facility.
  2. If you don't have the F6 Add/Create option or the F22 Delete option, you should check the possible reasons listed in LANSA License - F6 Add/Create and F22 Delete options not available
  3. 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
  4. The LANSA License screen in V13 lists the licenses code, the license description and whether they are valid or not and if they are seat based, how many seats you are licensed for. Ensure the licenses are valid for the period and seats (if applicable) expected. 
  5. Do you have the correct license for the product or feature you are executing? For example, you need an LXX (or seat based equivalent) on the server to execute a LANSA superserver application to a Windows server or an IBM i server.
  6. If you have a seat based license, have you exceeded the number of seats available for use?
  7. Other possibilities would be detailed in the Support section of the LANSA Web site.

Server License Code on UNIX/Linux

  1. Troubleshooting steps to come.
  2. 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 a Visual LANSA development environment.

  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. 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.
  3. 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.
    Note: Software key licensing in V13 does not support the concept of a central license location. The software key license file needs to be available for each Visual LANSA installation.
  4. 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.
  5. 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.
  6. Other possibilities would be detailed in the Support section of the LANSA Web site. 
  7. 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.
    Hint: You can easily test this by closing one IDE/development environment. If you can then open the IDE/development environment that was generating the license error, you do not have enough available license 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 UNIX/Linux

  1. Troubleshooting steps to come.
  2. 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.