Backing up information in Aspel SAE is a critical process to ensure the integrity of the company’s data, such as customers, inventory, invoices, and policies. However, a common problem users encounter is an error when trying to generate this backup, where the system indicates it was not possible to create it.

The Error

When going to the company or configuration menu and selecting the option to back up the database, after a few seconds or instantly, SAE throws an error message similar to:

  • “Error generating the backup.”
  • “The backup file could not be created in the specified path.”
  • “Access violation” or errors related to file reading/writing (Write fault).

This error prevents the user from securing their database, leaving the company prone to data loss in case of equipment failure or native database corruption (Firebird or SQL).

Root Cause

The most frequent causes of this problem in Aspel SAE include:

  1. Windows Permissions: The Windows user does not have sufficient permissions to write or create files in the specified destination path.
  2. Antivirus or Firewall: Security systems frequently block the packaging and compression process (the .zip file that SAE generates), assuming it is a suspicious action when manipulating hundreds of database files quickly.
  3. Network Problems: If you try to back up directly to a shared network folder or mapped network drive (NAS), and micro-cuts occur, the compressed file gets corrupted and the system aborts.
  4. Open Files: Another user on the multiuser network is querying or modifying records aggressively, locking the tables and preventing the service from copying them for the backup.
  5. Non-existent Folder or Space: The path selected in previous windows no longer exists or the destination drive is full.

Step-by-Step Solution

1. Change the Destination Path and Run as Administrator

This is the fastest solution to 80% of permission problems:

  1. Close all Aspel SAE sessions on this computer and ask other users to temporarily log out of the system.
  2. Right-click the Aspel SAE icon and select Run as administrator (confirm Windows prompts).
  3. Go to the backup option and click the button to browse for the destination directory or path.
  4. Choose a new local folder, for example by creating a folder at C:\Backup_SAE_Today. Do not choose a network drive, USB, or the default DAC folder.
  5. Try generating the backup, selecting only the database (uncheck temporary files and indexes).

2. Check the Antivirus / Windows Defender Process

If SAE closes unexpectedly when attempting to compress:

  1. Open your antivirus interface or the Windows Security Dashboard.
  2. Temporarily turn off real-time protection (only for the minutes the backup takes).
  3. Optionally, add the SAE executables folder (C:\Program Files (x86)\Aspel\Aspel-SAE X.0) and the DAC data folder to your antivirus Exclusions.
  4. Try to make the backup again.

3. Backup Data Directly from the Database Engine (Advanced)

If SAE continues to fail internally, you can copy and backup the physical files. If you use Firebird (default in SAE):

  1. Go to Windows Services (services.msc) and stop the Firebird Server service.
  2. Navigate to the DAC path (Common Files Directory), usually: C:\Program Files (x86)\Common Files\Aspel\Sistemas Aspel\SAEX.00\Empresa01\Datos.
  3. Copy the file ending in .FDB (e.g., SAE80Empre01.FDB) to another secure folder, external hard drive, or the cloud.
  4. Start the Firebird service again to reactivate SAE.

4. Recovery of Corrupted Firebird Files or Defragmentation

If it is a problem that indicates an error reading some specific tables or indexes, we suggest consulting manuals for repair in Firebird with the GSTAT and GFIX tools, although this is suggested only for database analysts; contacting technical support may be the best move before engaging the database in a severe fix without prior experience.

Prevention

As continuous prevention measures:

  • Implement a strict routine; when a backup is generated, all user staff on the multiuser network should log out of Aspel to unlock the records.
  • Make the SAE backups to the C: drive and later, with a Windows utility, move them, or copy them to the cloud or server at night. Do not point the Aspel SAE Backup directly to the network.
  • Aspel COI or NOI backup error: The causes are usually exactly identical in all Aspel suites that handle Firebird and internal compressors.
  • EEFFACE when backing up: This signifies disconnection or corruption with the database when it is read.

Summary

  • Generating backups over a network can abort the backup; try to back up to a local drive.
  • Elevating privileges by running SAE as an administrator avoids write problems.
  • Restrictions such as storage space, active database disconnection, or Windows Antivirus prevent and block files temporarily in use by Aspel SAE.