HomeTroubleshootingAll Products: StartupConcurrent Network Client Requests Activation ID (5.x only)

2.12. Concurrent Network Client Requests Activation ID (5.x only)

Applies to: All 5.x network client software (not 6.0 or newer)

I installed the 5.x network client successfully, but when I try to run it, I get a Palisade License Activation screen asking me for an Activation ID.

Releases 5.x unfortunately displayed an activation prompt whenever there was any kind of problem with the network license. This is fixed in releases 6.x and newer. If you have a current maintenance contract, you can upgrade your network at no charge; just contact your Palisade sales office.

But of course you want to solve the individual user's problem right away, even if you intend to upgrade later.  There are several possible causes, but the most likely is incorrect installation. Here are the things to check:

Was the software installed on this workstation as a network client, and not a standalone trial?

During installation, the Client.ini file must be present in the same folder as the installer executable. Typically this folder is on the server as C:\Program Files\FLEXnet\Palisade\your serial number\ClientInstaller or C:\Program Files (x86)\FLEXnet\Palisade\your serial number\ClientInstaller folder. The network information is in that Client.ini file.

To install the client software, use Network Neighborhood or similar to point to the ClientInstaller folder on the server, then right-click the installer there and select Run As Administrator. If you prefer, you can copy both files to a network share, USB stick, or the client's desktop and do the install that way. The key requirement is that the Client.ini file must be in the same folder as the installer during installation. Otherwise, the installer will appear to succeed but it will not know that you have a network copy and will install a trial standalone copy.

To fix this particular client's installation, please see Changing a 5.x Standalone Copy to a Concurrent Network Client.

To avoid this problem for future client installs, use the ClientInstaller folder as described above.

Are server and client set up to use the same name and port?

On the server, look at your license file. (It is in the same folder as Palisade.exe, and has a .lic extension.) The port number is an optional field on the SERVER line, following the Ethernet address or the word ANY. If no port number is specified, the server dynamically selects a port in the rage 27000 to 27009.

Run LMTools and click System Settings.  The first field, Computer/Hostname, is the name of the server as far as FLEXnet is concerned.

On the client, look in the System Registry, at the key
HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE or
HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE.
The port number precedes the @ sign and server name.  If no port number precedes the @ sign, the client dynamically negotiates a port number 27000 to 27009 with the server.

The server name in the client's System Registry should match the host name in LMTools.  (There are some unusual exceptions, where network administrators use fully qualified domain names or IP addresses.  These must be carefully tested.)

If the license file on the server specifies a port number, the System Registry key on the client must specify the same port number. If the license file on the server does not specify a port number, the System Registry key on the client must not specify a port number.  For more information, please see "Edit the Client.ini file" and "Redirect any installed clients" in Redirecting a 5.x/4.x/1.x Concurrent Client to a New Server.

Can the client communicate with the server?

Verify that the client can communicate with the server using the server name and port number specified in the System Registry key.  If no port number is specified, all ports in the range 27000 through 27009 must be open.

You can test whether a given port is open by using Telnet. (This requires a Telnet client on the client computer and a Telnet server on the server. These are part of Windows, but they might not be turned on. If they're not enabled, you can enable them in Windows Control Panel » Programs and Features » Turn Windows features on or off.) The command format is

telnet myservname 27000

You should get a blank screen if the port is open. If it's not, you should get an error message within about 60 seconds.

Also verify that the firewall on the client is allowing PalFlexServer5.exe to send and receive packets.

Is the license process running on the server?

Run LMTools and select Server Status » Perform Status Enquiry.  If you do not see "Palisade UP within the display", the process is not running.  Try starting it (on the Start/Stop/Reread tab) and re-check status.  If it still is not running, click Config Server » View Log and look at the end of the log for error messages.  Troubleshooting help is at Network Server Issues.

Is a license available?

If all licenses are currently in use, 5.x will pop up a Palisade License Activation screen without providing an explanation. Please see Monitoring License Use on 5.x Concurrent Network for instructions to check the licenses in use and verify that one is available.

Last edited: 2015-10-05

This page was: Helpful | Not Helpful