License troubleshooting for LANSA V14

Date:May 2019
Product/Release:LANSA V14
Abstract:Troubleshooting Licensing problems in LANSA V14
Submitted By:LANSA Technical Support

The LANSA license you have received is either a LANSA Server/Runtime License Code(s) or a LANSA Development License File.

Note: The LANSA Development Licenses introduced in EPC142050 for V14 SP2 replace the 3rd party software key licenses in use prior to this EPC.

Select License Type

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


Server License Code

This type of LANSA licensing generally applies to server licensing, for example, LXX (SuperServer), DEV (IBM i Development), CLT (LANSA Client), WEB (Web execution). Server licensing involves adding the license code you have received from LANSA Licensing to your LANSA system

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

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

Your LANSA License email notification states what type you have received. A Server License Code(s) notice will look like the following:

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

 

LANSA Development License File (including Remote License Servers)

A LANSA Development license is required to launch the Visual LANSA IDE. Without a valid LANSA development license, a license error will be generated on login. Applying this license involves launching the LANSA Development License manager to navigate to the location where you saved the license file to and applying it within the License manager.
Note:
The license you receive is only valid for the CPU that you have requested it for.

Your LANSA License email notification states what type you have received. A LANSA Development License File notice will look like the following:

  • Attached please find ...
    - Key license - LICENSES_170A_1DD2557A_0000239495.DAT
    For Model: 170A Serial: 1DD2557A

 

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 V14 or above 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.
    Note: LANSA License screen in V14 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. Note: LANSA reads through the licenses sequentially until the requested license code is found. Make sure that there is not an invalid or expired version of a particular license code listed above a valid version of the same license code. If an invalid or expired license code is found first, a license error will be generated. For ongoing license maintenance and to prevent any license errors due to their existence, invalid or expired licenses should be regularly removed by selecting the license to be deleted and clocking the Delete Selected button.
  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 V14 is of the form x_lic_<model>_<cpu>.lic. 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 V14 or above. 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 V14 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 V14 configuration but not another one on the same PC, you should contact LANSA Support.
  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 messages on screen for possible reasons. Other possible reasons are 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 V14 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. Note: LANSA reads through the licenses sequentially until the requested license code is found. Make sure that there is not an invalid or expired version of a particular license code listed above a valid version of the same license code. If an invalid or expired license code is found first, a license error will be generated. For ongoing license maintenance and to prevent any license errors due to their existence, invalid or expired licenses should be regularly removed using the delete option (F22).
  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.

LANSA Development License File on Windows

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

Things to check:

  1. Does the license file have the correct naming format. The correct name is license.dat
  2. Is your licensing set to Local mode? Check in the LANSA Development licensing studio that the License Server is set to Local. The LANSA Development licensing studio should also display the applied license. Ensure you have a VLW. Review the start date and end date and ensure the status is valid.
  3. The CPU details may have changed since you generated the x_cpu details for the license you are trying to apply. The license is generated for the exact CPU details provided. Applying an O/S service pack or installing a new network card can affect the CPU details. If in doubt, re-generate your x_cpu details from the LANSA Development License Manager and send to your local LANSA license representative for a replacement license.
  4. Do you have the latest EPC142050 applied to your LANSA system? You can check using the Product Information option from the Help Menu in the IDE. The new LANSA development licensing requires EPC142050 to be applied to your V14 SP2 Visual LANSA system. Refer to www.lansa.com/support/notes/epc.htm for the latest LANSA EPCs.
  5. If no obvious reason can be found, you should generate a log file and send it to LANSA support. A log file can be generated by
    • Creating a windows environment variable called LSIDELOG and setting it to a location (the location must exist). For example, LSIDELOG=c:\temp\ide.log
    • Launch Visual LANSA. If you get a license error, navigate to the location set in LSIDELOG= and send the generated ide.log file to LANSA support.
  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

LANSA Development License Server on Windows

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

Things to check:

  1. The x_cpu details must be obtained from the CPU that is nominated as the dedicated LANSA Development license server. This is also the CPU that the license is applied to.
  2. Does the license file have the correct naming format. The correct name is license.dat
  3. Is your licensing server set to a dedicated Host name value (PC name or IP address)? Check in the LANSA Development licensing studio that the License Server is set to Host name and the Host name is correct. The Host name is the Computer Name. An IP address can be used instead. Check with your Network Administrator to ensure this value is correct.
  4. The LANSA Development licensing studio should also display the applied license. Ensure you have a VLN. Review the start date and end date, the number of seat and ensure the status is valid.
  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. If in doubt, re-generate your x_cpu details from the LANSA Development License Manager and send to your local LANSA license representative for a replacement license.
  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 EPC142050 applied to your LANSA system? You can check using the Product Information option from the Help Menu in the IDE. The new LANSA development licensing requires EPC142050 to be applied to your V14 SP2 Visual LANSA system. Refer to www.lansa.com/support/notes/epc.htm for the latest LANSA EPCs.
  8. If no obvious reason can be found, you should generate a log file and send it to LANSA support. A log file can be generated by
    • Creating a windows environment variable called LSIDELOG and setting it to a location (the location must exist). For example, LSIDELOG=c:\temp\ide.log
    • Launch Visual LANSA. If you get a license error, navigate to the location set in LSIDELOG= and send the generated ide.log file to LANSA support.
  9. Other possibilities would be detailed in the Support section of the LANSA Web site.
  10. 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 LANSA Development licensing and and Server Rutime codes) to work. The non availability of this primary network card will disable the LANSA licensing on this PC.