XLSTAT: How to Troubleshoot Network License Setup Issues

Depending on the network environment, some customers might experience issues when initially setting up the XLSTAT Network license server.  The intent of this article is to guide in troubleshooting the installation. 

Please refer to the Network Server Installation Guide for general installation directions.

 

When Clients Cannot Communicate with the Server

The XLSTAT client software uses TCP, port 7070 by default to communicate with the server. If this connection cannot be established, this error message will be triggered:

To address this, please make sure of the following:

• The TCP port on the XLSTAT client and server match

• The TCP port is open in the client's antivirus program

• The TCP port is open on any firewalls that restrict communications in between those subnetworks.

When the Server Cannot Process Requests from Clients

Make sure:

• The proper network license was activated on the license server.

  • This can be checked by opening the "XLSTAT Network License Server Admin Tool" and viewing the  Licenses tab.

• The server is not suspended.

  • This can be checked using the "XLSTAT Network License Server Admin Tool" from the Start menu, on the machine where the server is installed.

 

If you have issues setting up, please ask the Lumi AI Assistant  by going to the Support Resources Page and clicking on the appropriate product name. If the assistant can't help, a case will be created for you.

Once you receive a case number by email, please email back and include the following information in your request in order to ease its resolution:

• Details regarding the installation of the XLSTAT server and client devices

• A copy of the support file from an XLSTAT client that experiences the problem.

  • This can be generated from the About XLSTAT menu on the XLSTAT toolbar.

  • Click  Technical details then Support file .

• An archive of the files in the C:\ProgramData\addinsoft\xlstatnls\logs  directory from the XLSTAT server.

  • If this archive is too large to be included in an email, only include the server.log files from the last 5 days or so.