Palisade Knowledge Base

Knowledge Books

• Knowledge Books
• Standalone Licenses
• Network Guide
• More on Networks
• End User Setup
• Techniques and Tips
• Troubleshooting
• Licencias individuales
• Guía para Administradores de Red
• Licencias de red
• Configuración de usuario final
• Técnicas y Consejos
• Soluciones
• Licenças Standalone
• Licenças de Rede
• Configuração do usuário final
• Técnicas e Dicas
• Soluções
• Obsolete Articles

• Main Support Page

Home → Troubleshooting → All Products: Startup → "FLEXnet returned error code –97" (network client)

2.62. "FLEXnet returned error code –97" (network client)

Disponible en español: "FLEXnet generó un código de error -97" cliente de red simultanea

Applies to: All Concurrent Network products, releases 5.x and later

When I launch @RISK or another one of the Palisade applications, I get this error message:

Authorization failure
Details:
FLEXnet returned error code –97: The desired vendor daemon is down.

What is wrong?

This message means that the client could communicate with an LMGRD program on the server, but could not communicate with the Palisade.exe program (the "vendor daemon") on the server. This could be caused by configuration problems on your server or your clients. Your first question is, does this happen on all clients, or are some clients able to run? A server problem will affect all clients. A client problem could affect all clients or only some clients, depending on whether some clients are configured correctly and some incorrectly.

• (Affects all clients) Port-number conflict among multiple FLEXnet-licensed products. See "Finding and fixing port-number conflicts" in FLEXnet Error: "Exiting due to signal 27".

• (Affects all clients) Misplaced license file. In Palisade Server Manager, click Open LIC Folder. You should have PalisadeNetwork.lic and Server.lic only. If you have other .lic files there, remove them. (Sysadmins sometimes put a Palisade_Course.lic file in this folder on the server. That's a standalone license and will cause your network license to malfunction.) Click Refresh in Server Manager after removing any wrong file.

• (Affects all clients) License process not running on the server. Network Server Issues lists the most common problems and their solutions.

  • In 6.x and newer, launch Palisade Server Manager. If the service is not running, start it, click Refresh, and verify that it is still running. If it stops itself, click Open .LIC folder and examine the contents of the PalisadeService.log file.
  • In 5.x, launch LMTools. On the Server Status tab click Perform Status Enquiry. If the service is not running, on the Start/Stop/Reread tab click Start Service; perform a new Status Enquiry to verify that the service is not running. If it is not, go to the Config Services tab and click View Log. Trouble messages will be near the end of the log.

• (Could affect all clients, or only some clients) Firewall forbidding communications between this client and the server. On the client, either open the appropriate ports or make PalFlexServer8.exe, PalFlexServer7.exe, PalFlexServer6.exe, or PalFlexServer5.exe an exception in the firewall. On the server, list both Palisade.exe and lmgrd.exe as exceptions for send and receive. For more details, see Network Ports and Firewalls.

• (Could affect all clients, or only some clients) Any of the causes listed, with solutions, in "FAILURE: Unable to reach a network server."

Last edited: 2018-06-11