Palisade Knowledge Base

HomeTroubleshootingNetwork Server IssuesFLEXnet Error: "Exiting due to signal 27"

18.16. FLEXnet Error: "Exiting due to signal 27"

Applies to: All Palisade network products licensed with FLEXlm or FLEXnet

Server Status says that the vendor daemon is not running. When I look at the debug log file, I see this error:


This means that the vendor daemon (Palisade.exe) can't find any valid licenses, or there is a conflict between two or more vendor daemons.

Finding and fixing port-number conflicts on the server:

If you also have FLEXnet licenses from other vendors, check that they are not using the same port number. The port number is found on the SERVER line of the license file, as an optional argument after the Ethernet address. (If "ANY" appears on that line, it refers to any Ethernet address, not any port number.) If some specify a port and some do not, there could be a conflict if an lmgrd with a specified port happens to load after an lmgrd with an unspecified (dynamic) port. If any vendor's license file, including Palisade's, specifies an lmgrd port number on the SERVER line, then every license file must specify a unique port number on the SERVER line. (The more robust solution is not to specify an lmgrd port in any license file.)

If there is a conflict, change the port number in one of the license files, and make a matching change on the clients.

If you specify both lmgrd port number on the SERVER line and vendor-daemon port number on the VENDOR line, they must be different.

Finding and fixing multiple-daemon conflicts:

The Palisade vendor daemon, palisade.exe, can run only one copy at a time. Open Task Manager to see whether you have multiple copies running. If you do:

  1. Shut down all the palisade.exe processes. Also shut down their associated lmgrd.exe processes.
  2. If you have multiple Palisade services defined in LMTools, remove all but one of them.
  3. Restart the Palisade license service in Server Manager (if available) or LMTools.

Finding and fixing license issues:

Perhaps you installed a license but it has expired, or you never installed your license, or maybe you simply need to have the license process reread your licenses.

If you have Palisade Server Manager, which comes with 6.0 and later network software, run it and look at the list of licenses. If no licenses are shown, click the "Unavailable Licenses" button, if it appears, to see unavailable licenses including expired licenses. This should tell you what's wrong, but feel free to contact Palisade Technical Support for assistance.

If you don't have Palisade Server Manager, and your license is a certificate type:

  1. Look in the license file (certificate), on the INCREMENT line, for the expiration date. If the certificate has expired, contact Palisade Technical Support to obtain an updated license file. Please attach your expired license file to your request.
  2. If your certificate has not expired, open LMTools and on the Config Services tab verify that the second box points to the correct license file. Change it if necessary, and click Save Service, then go to Start/Stop/Reread and click Start Server. Close and reopen LMTools, and check Server Status.

If you don't have Palisade Server Manager, and your license is a trusted storage type ("activatable", downloaded with TransferLicenses.bat or Request.bat):

  1. Open a command prompt, navigate to the folder whose name is your serial number, and type this command:
    palserveractutil -view
  2. If the command fails with "ERROR: Activation library initialization failed", you have a port-number conflict; see above.
  3. If you see "No fulfillment records in Trusted Storage", you have not yet downloaded your license. Please follow the procedure in Server Steps 2 through 4 in the network Readme file.
  4. If you see some fulfillment records, look on each INCREMENT line for an expiration date. If every license has expired, please contact Palisade Technical Support for assistance and attach a copy of the output. If you have a permanent license or it has not yet expired, open LMTools and on the Start/Stop/Reread tab click Stop Server, then Start Server. Close and reopen LMTools, and check Server Status.

Last edited: 2016-06-09

This page was: Helpful | Not Helpful