Error # 2070. The license server is down. Specific symptom number: 5

Technote (FAQ)


We have network/concurrent licence installations of SPSS Statistics. When SPSS Statistics is launched, the following errors are reported:

The current license does not permit this job to continue.

followed by...

Error # 2070
The license server is down. Please check to see that the license server is running or ask your local SPSS coordinator to check the license server.
This command is not executed.

Specific symptom number: 5.

The SPSS Sentinel License Manager has been licensed and is running. What is the problem?


The above error can be caused by the following:

The License Manager IP address entered during the SPSS for Windows installation is invalid. Please do the following to verify:

1. Navigate to the SPSS Statistics directory and open "spssprod.inf", using any text editor.

2. Verify the "DaemonHost" value matches the IP address of the machine where the SPSS Sentinel License Manager is installed.

If the "DaemonHost" value is accurate, you have a name resolution problem. Error # 2070, Symptom number 5 typically means the name resolution database contains a record where a single or duplicate hostname to IP address mapping is incorrect (and that IP address is not active or does not exist on the network). For example, the name resolution database maps Machine_A to IP address:, but Machine_A's IP is actually some other address. To verify, please do the following:

3. Run lswhere.exe (which is located in the SPSS directory) from a problematic SPSS for Windows client and take note of the displayed output. The following is an example of the output:

Sentinel LM 8.2.2 Search Tool For License Servers
Copyright (C) 2004 Rainbow Technologies, Inc.

Server Address :
Server Name : Machine_A

If the SPSS Sentinel License Manager machine is not listed or you encounter the error, "Error[17]: Probably no servers are running on this subnet.", please add the following system environment variable to the SPSS for Windows client and run lswhere.exe again:

Variable: LSHOST
Value: Name or IP address of the License Manager machine

For information about defining environment variables, see p. 13 of the Network License Administrator's Guide. Additional information can be found under Resolution 51499. If using the LSHOST environment variable does not render the SPSS Sentinel License Manager machine, try using LSFORCEHOST instead.

4. When you see the SPSS Sentinel License Manager machine name and corresponding IP address listed in the lswhere output, ping the displayed Server Name from a command line, e.g.

ping Machine_A

An example of the resulting output is as follows:

Pinging Machine_A [] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

If the request times out, you have a name resolution problem and must address it before SPSS can acquire a license from the SPSS Sentinel License Manager.

If the machine is trying to connect to the SPSS Sentinel License Manager through a VPN and you have meticulously gone through each of these steps without success, then we have had reports from other customers that upgrading to a more recent version of the VPN client, e.g. 4.8, has also resolved this issue.

Another cause of this problem is that the Sentinel License Manager fails to start due to a conflict with another application. Some customers have stated that the Domain Name Service (dns.exe) has started to use port 5093 after a server is rebooted. This is due to MS Security Update 953230 (MS-08-037). Please go to: for more information about this update.
MS08-037: Vulnerabilities in DNS could allow spoofing

MS kb953230

Port conflict and connection issues
After you install this security update, and then you restart the computer, you may experience issues with User Datagram Protocol (UDP) dependent network services. After you install this security update, a service that depends on a UDP port may not start on a computer that is running Windows 2000, Windows Server 2003, or Windows Server 2008. This issue occurs if the service is allocated to the DNS service after security update 953230 is installed.

For more information about this issue, click the following article numbers to view the articles in the Microsoft Knowledge Base:
956188 You experience issues with UDP-dependent network services after you install DNS Server service security update 953230 (MS08-037)
977512 The DNS Server service binds to all ports in the Windows Deployment Services port range on a server that is running Windows Server 2008 R2 or Windows Server 2008

To confirm this run the following command: netstat -abp udp > sentinel.txt
from the command line of the server housing the Sentinel LM. This will produce a text file (named sentinel.txt) that lists all applications using ports on the server. Run a search for UDP port "5093" and determine if the Sentinel LM application (named lservnt.exe) is using this UDP port.

If a conflict has been found, reserve this port through the Registry and reboot the server

Related information

A simplified Chinese translation is available

Historical Number


Document information

More support for:

SPSS Statistics

Software version:

Not Applicable

Operating system(s):

Linux, Windows, iOS

Reference #:


Modified date:


Translate my page

Content navigation