When opening Aspel SAE, COI, or NOI on a network workstation, the message “No se encuentra ningún servidor de licencias” (License server not found) or its variant “No se logró conectar al servidor de licencias” (Could not connect to the license server) appears. This error prevents the program from starting in multi-user mode because the client cannot communicate with the service that manages licenses. In this guide you will learn how to diagnose and resolve each possible cause of this problem.

The Error

When you try to launch any product in the Aspel family (SAE, COI, or NOI) on a workstation configured for multi-user mode, the program displays a dialog box with one of these messages:

  • “No se encuentra ningún servidor de licencias” (No license server found)
  • “No se logró conectar al servidor de licencias” (Could not connect to the license server)
  • “Error al conectar con el servidor de licencias en [IP]:[Port]” (Error connecting to the license server at [IP]:[Port])

The program does not allow you to continue and either closes or remains in read-only mode with a single license. This error can appear suddenly on machines that previously worked correctly, or from the very first connection attempt on a new installation.

Root Cause

There are five main reasons why Aspel cannot find the license server:

  1. The ServLicAsp service is stopped. The Windows service “Licencias de usuarios Aspel” is not running on the server machine. This can happen after a server reboot, a Windows update, or an unexpected shutdown.

  2. The firewall is blocking ports 10000/10001. The Aspel license server communicates over TCP ports 10000 and 10001. If Windows Firewall or a third-party firewall blocks these ports, clients cannot connect.

  3. The ServLic.ini file has the wrong IP. Each Aspel installation on client machines contains a ServLic.ini file that specifies the IP address and port of the license server. If the server IP changed or the file has incorrect data, the connection fails.

  4. The license server was uninstalled. Sometimes, when reinstalling Aspel or migrating the server, the licensing component is removed but client machines still point to the old address.

  5. Network connectivity issues. Disconnected cables, powered-off switches, misconfigured VLANs, or changes in network infrastructure can prevent the client from reaching the server.

Step-by-Step Solution

Step 1: Verify the service on the server

On the machine where the license server is installed:

  1. Press Win + R, type services.msc and press Enter.
  2. Look for the service named “Licencias de usuarios Aspel” in the list.
  3. Verify that the Status is “Running”.
  4. If it is stopped, right-click and select “Start”.
  5. Double-click the service and change the Startup type to “Automatic” so it starts with Windows.

If the service does not appear in the list, the license server is probably not installed. See the article on how to install and activate the license server.

Step 2: Review the ServLic.ini file on the client

On each client machine where the error appears:

  1. Navigate to the Aspel product installation folder, for example:
    • C:\Program Files (x86)\Aspel\SAE 9.0\
    • C:\Program Files (x86)\Aspel\COI 10.0\
    • C:\Program Files (x86)\Aspel\NOI 12.0\
  2. Open the ServLic.ini file with Notepad.
  3. Verify it contains the correct IP of the license server and the proper port:
[Servidor]
IP=192.168.1.100
Puerto=10000
  1. If the IP does not match the current server, correct it and save the file.
  2. Repeat on all affected client machines.

Step 3: Test network connectivity

From the client machine, open a Command Prompt (CMD) window and run:

ping 192.168.1.100

If the ping responds successfully, test the connection to the service port:

telnet 192.168.1.100 10000
telnet 192.168.1.100 10001

If ping fails, there is a network issue between client and server. If ping works but telnet does not connect, the problem is a firewall or the service is stopped.

Note: If the telnet command is not available, enable it from Control Panel > Programs > Turn Windows features on or off > Telnet Client.

Step 4: Configure the firewall on the server

On the server machine:

  1. Open Windows Firewall with Advanced Security (search for “firewall” in the Start menu).
  2. Click Inbound Rules > New Rule.
  3. Select Port > TCP > Enter 10000, 10001.
  4. Select Allow the connection.
  5. Apply the rule to the Domain, Private, and Public profiles as appropriate for your network.
  6. Name the rule “Aspel License Server”.

You can also create the rules from CMD with administrator privileges:

netsh advfirewall firewall add rule name="Aspel License TCP 10000" dir=in action=allow protocol=TCP localport=10000
netsh advfirewall firewall add rule name="Aspel License TCP 10001" dir=in action=allow protocol=TCP localport=10001

Step 5: Restart and verify

  1. Restart the “Licencias de usuarios Aspel” service on the server.
  2. On the client machine, completely close Aspel if it was open.
  3. Reopen Aspel SAE, COI, or NOI.
  4. Verify that the program starts without the error message and works in multi-user mode.

Alternative Solution

If after following all the steps above the error persists, try the following:

  • Reinstall the license server: Download the license server installer from the Aspel website, uninstall the current version, and reinstall it. This regenerates the configuration and service.
  • Change the port: If port 10000 is occupied by another service, modify the port in both the license server and the ServLic.ini file on all clients.
  • Verify with netstat: On the server, run netstat -an | findstr 10000 to confirm the service is listening on the expected port.
  • Check your antivirus: Some enterprise antivirus solutions block local connections. Add ServLicAsp.exe to the exclusion list.

Prevention

To prevent this error from recurring:

  • Set the service to Automatic so it starts with Windows.
  • Document the license server IP and share it with your support team.
  • Use a static IP for the license server machine; avoid DHCP on that computer.
  • Create firewall rules as part of your standard installation procedure.
  • Monitor the service with supervision tools to receive alerts if it stops.
IssueLikely causeQuick fix
”No se logró registrar la serie”Service network permissionsConfigure domain account for the service
Only one user can log inService stoppedStart ServLicAsp in services.msc
”La serie no es válida”Series not registered on serverRegister the series from Utilities
EEFFACE error on launchCorrupt data filesRepair database from utilities
License server won’t installWindows 64-bitInstall manually from SysWOW64

Summary

  • The “No se encuentra ningún servidor de licencias” error in Aspel has five main causes: stopped service, firewall, incorrect IP in ServLic.ini, uninstalled server, or network issues.
  • First verify that the “Licencias de usuarios Aspel” service is running on the server.
  • Check that the ServLic.ini file on each client has the correct IP and port.
  • Open TCP ports 10000 and 10001 in the server firewall.
  • Use ping and telnet to diagnose connectivity problems.
  • Set the service to Automatic startup and use a static IP to prevent the issue.