Palisade Knowledge Base

HomeTroubleshootingNetwork Server IssuesPalisade exited with status 255" / "Winsock: invalid address

18.7. Palisade exited with status 255" / "Winsock: invalid address

Applies to:
Palisade network server software 6.x/7.x/8.x

Palisade Server Manager thinks the license service is running, but the Status button display shows that the vendor daemon is not running.

To display the log, I click the magnifying glass at lower left, then the View button. Examining the log, I see "palisade exited with status 255".

If I click the Status button in Server Manager immediately after stopping and restarting the service, I see error code -15,578: 10049, "Winsock: invalid address".

This is most likely a firewall or port problem with the vendor daemon.

First: If you specified a port number for the vendor daemon, make certain that nothing else on the server is using that port. (If the vendor daemon port number is dynamic, FLEXnet automatically selects a port that isn't in use.)

Second: lmgrd and the vendor daemon palisade.exe communicate with each other on the vendor daemon port. Check the log to find which port is being used, and verify that communications can take place on that port, both inbound and outbound. You can test whether a given port is open by using PowerShell (v4 or newer) or Telnet:

If this loopback fails, make certain that palisade.exe and lmgrd.exe are both listed as exceptions allowing inbound and outbound communications, and that no block rule is overriding those exceptions.

As a third option, you can try changing the service on the server. To do this open Services.msc. Then open Palisade License Service and go to the Log On tab. Please try switching from Local Service to Local System account.

Last edited: 2020-07-21

This page was: Helpful | Not Helpful