Aspel SAE is the most widely used business management system in Mexico for inventory management, invoicing, and accounts receivable. When a company needs multiple users to work simultaneously in SAE, the system is configured in network or multiuser mode. However, connection errors that prevent workstations from accessing the data server are very common. This guide walks you through fixing the most frequent errors when connecting Aspel SAE over a network.

The Error

When trying to open Aspel SAE from a workstation configured to connect to the network server, error messages like these appear:

  • “No se puede conectar con el servidor de datos” (Cannot connect to data server) — this is the most frequent message and appears immediately when starting SAE on the workstation.
  • “Error al acceder a la base de datos en red” (Error accessing database over network) — occurs when SAE can locate the server but cannot open the Firebird database.
  • “Unable to complete network request to host” — a Firebird message indicating it cannot establish a network connection with the server.
  • “No se encontró la ruta de red especificada” (Network path not found) — appears when the path configured on the workstation is incorrect or the shared folder is inaccessible.
  • “El servidor RPC no está disponible” (RPC server unavailable) — related to communication issues between the workstation and the Windows server.

These errors typically appear in the main SAE window when starting the program or when trying to open a company database. In some cases, SAE freezes for several minutes before displaying the error.

Root Cause

Aspel SAE network connection errors arise from a combination of factors in the server and workstation configuration:

1. Windows Firewall blocking communication

Windows Firewall blocks incoming connections to port 3050 by default, which is the port used by Firebird for database communication. If the firewall does not have an exception configured for this port or for the Firebird executable, workstations will not be able to connect.

2. Incorrect shared folder permissions

The folder where Aspel SAE is installed (C:\Archivos de Programa\Common Files\Aspel\Sistemas Aspel) must be shared on the network with Full Control permissions for users who will access the system. If permissions are read-only, SAE may connect but will be unable to write data, producing intermittent errors.

3. Misconfigured server path on the workstation

Aspel SAE requires each workstation to configure the network path using the server’s IP address followed by the local path to the SAE directory. A common mistake is using the computer name instead of the IP, which fails if the local DNS does not resolve correctly.

4. Firebird service stopped or not installed

The Firebird database engine must be installed and running only on the server. If Firebird is also installed on the workstations, conflicts can occur. Additionally, if the Firebird Guardian service is not started on the server, no workstation will be able to connect.

5. Network protocol not enabled

In some Windows configurations, file and printer sharing protocols (SMB) may be disabled, preventing workstations from accessing the server’s shared resources.

Step-by-Step Solution

Step 1: Verify basic network connectivity

Before touching SAE configuration, confirm that the workstation can communicate with the server:

  1. Open Command Prompt (cmd) on the workstation.
  2. Run the following command with your server’s IP:
ping 192.168.1.100
  1. You should receive responses with no packet loss. If there is loss or timeout, the problem is with the physical network (cables, switch, IP configuration).
  2. Verify that both machines are on the same subnet. For example, if the server is 192.168.1.100, the workstation should have an IP like 192.168.1.x with subnet mask 255.255.255.0.

Step 2: Configure Windows Firewall on the server

This is the most frequent cause of the error. Configure the necessary exceptions:

  1. On the server, open Control Panel > System and Security > Windows Firewall with Advanced Security.
  2. In the left panel, click Inbound Rules.
  3. Click New Rule and select Port.
  4. Select TCP and enter 3050 as the specific port.
  5. Select Allow the connection and check all three profiles (Domain, Private, Public).
  6. Name the rule Firebird SAE and click Finish.

Additionally, create a rule for the Firebird executable:

  1. New Rule > Program.
  2. Browse to the executable path: C:\Program Files\Firebird\Firebird_2_5\bin\fbserver.exe (path may vary depending on version).
  3. Select Allow the connection for all profiles.

Repeat these firewall configurations on each workstation, especially the port 3050 rule.

Step 3: Configure shared folder permissions

On the server, configure the shared folder correctly:

  1. Navigate to C:\Archivos de Programa\Common Files\Aspel\Sistemas Aspel.
  2. Right-click the Sistemas Aspel folder and select Properties.
  3. Go to the Sharing tab and click Advanced Sharing.
  4. Check Share this folder and assign a share name (e.g., SistemasAspel).
  5. Click Permissions and add the Everyone group with Full Control permission.
  6. Go to the Security tab and verify that network users have Modify and Read & Write permissions.

To verify from the workstation:

  1. Open Windows Explorer.
  2. In the address bar, type \\192.168.1.100\SistemasAspel and press Enter.
  3. You should be able to see the SAE folders and have permission to create and delete test files.

Step 4: Configure the network path on workstations

On each workstation, configure the path to the server:

  1. Open Aspel SAE on the workstation.
  2. If SAE opens but does not find the company, go to Configuración > Ruta del sistema.
  3. In the path field, enter the network path using the server IP and the full path in Firebird format:
192.168.1.100:C:\Archivos de Programa\Common Files\Aspel\Sistemas Aspel\SAE8.00
  1. Important: Use the server’s IP address, not the computer name. The format is IP:LocalPath where the local path is the path on the server’s disk.
  2. Click Aceptar and restart SAE.

If SAE will not open to change the configuration, you can edit the configuration file directly:

  1. Navigate to C:\Archivos de Programa\Common Files\Aspel\Sistemas Aspel\SAE8.00 on the workstation.
  2. Find the file SAE.ini or Config.ini.
  3. Modify the ServerPath or DataPath line with the correct server path.

Step 5: Verify and configure the Firebird service

On the server, ensure Firebird is properly configured:

  1. Press Windows + R, type services.msc, and press Enter.
  2. Find Firebird Guardian - DefaultInstance and Firebird Server - DefaultInstance.
  3. Both services must be in Started state.
  4. Double-click each service and change the Startup type to Automatic.
  5. If the services were stopped, click Start.

Verify that Firebird responds on port 3050 from the workstation:

telnet 192.168.1.100 3050

If the screen goes black (no text), the connection was successful. If you see “Could not open connection”, the firewall is still blocking or Firebird is not running.

Step 6: Uninstall Firebird from workstations

A very common mistake is having Firebird installed on both the server and the workstations. This can cause conflicts:

  1. On each workstation, open Control Panel > Programs and Features.
  2. Look for Firebird in the list of installed programs.
  3. If it appears, uninstall it. Only the server should have Firebird installed.
  4. Restart the workstation after uninstalling.

Alternative Solution

If the error persists after configuring the firewall and permissions, you can try an alternative connection using mapped network drives:

  1. On each workstation, open Windows Explorer.
  2. Click This PC > Map network drive.
  3. Select a drive letter (e.g., Z:).
  4. In the path, type \\192.168.1.100\SistemasAspel.
  5. Check Reconnect at sign-in and, if necessary, provide credentials.
  6. Click Finish.

Now configure SAE to use the mapped drive:

  1. Open SAE and go to Configuración > Ruta del sistema.
  2. Use the path Z:\SAE8.00 instead of the direct IP path.
  3. This alternative can work when IP path resolution fails.

Another option is to temporarily disable Windows Firewall on the server to confirm it is the source of the problem:

  1. Open Control Panel > Windows Firewall.
  2. Click Turn Windows Firewall on or off.
  3. Temporarily disable the firewall for private networks.
  4. Try connecting from the workstation.
  5. If it works, the problem is confirmed in the firewall rules. Re-enable it and review the rules.

Important: Never leave the firewall permanently disabled. Only disable it momentarily as a diagnostic test.

Prevention

To avoid network connection problems with Aspel SAE in the future:

  • Document the network configuration: Keep a record of the server IP, shared folder paths, open firewall ports, and access credentials.
  • Use static IP addresses: Configure a fixed IP on the server to prevent it from changing on restart and breaking workstation connections.
  • Configure Firebird for automatic startup: Ensure the Firebird services start automatically when the server powers on.
  • Install a UPS on the server: An unexpected power outage can corrupt Firebird databases and make the system inaccessible.
  • Do not install antivirus that blocks Firebird: Some antivirus programs like Avast or Norton block database ports by default. Add exceptions for fbserver.exe and port 3050.
  • Keep Aspel SAE and Firebird updated: Maintain both programs at the latest version to avoid compatibility issues.
  • Perform regular backups: Configure automatic database backups from Utilerías > Respaldo/Restauración before making network changes.
IssueProbable CauseQuick Fix
SAE opens but shows no companiesIncorrect server pathCheck path in Configuración > Ruta del sistema
Slow connection or SAE freezesSaturated network or faulty switchCheck network infrastructure and cables
”File is in use” error when opening companyAnother SAE instance has an active lockRestart Firebird service on the server
SAE works on server but not on workstationsFirewall blockingConfigure exceptions for port 3050
”Database file not found” errorLocal path instead of network pathChange to path with server IP
Intermittent disconnectionsServer IP changes (DHCP)Configure static IP on the server

Summary

  • The “Cannot connect to data server” error in Aspel SAE is mainly caused by Windows Firewall blocking Firebird’s port 3050.
  • Configure firewall exceptions on both the server and workstations for TCP port 3050 and the fbserver.exe executable.
  • The Sistemas Aspel folder must be shared with Full Control permissions for network users.
  • Always use the server’s IP address (not the computer name) when configuring the network path on workstations.
  • Firebird must be installed only on the server, not on workstations.
  • Verify basic connectivity with ping and the port with telnet before modifying SAE configurations.
  • Keep a static IP on the server and set Firebird services to automatic startup.