TL;DR — Quick Summary
Fix Aspel COI error 503 with Abort and Retry buttons: Firebird service, BDE alias, port 3050 firewall, and step-by-step recovery for accounting DB.
When Aspel COI cannot reach its Firebird database, users see error 503 with Abort and Retry. This guide covers service restarts, BDE alias fixes, lock files, and firewall rules for port 3050.
Prerequisites
- Administrator access on the database server
- BDE Administrator installed
- Maintenance window to close all COI sessions
Troubleshooting steps
- Stop every
COI.exeprocess on workstations and the server. - Restart the Firebird Windows service.
- Validate the COI BDE alias points to the live
.GDBfile. - Remove orphan
.lckfiles only when no user is connected. - Open TCP 3050 on the server firewall and test with
telnet.
Summary
- Error 503 is a connectivity problem, not automatic data corruption.
- Fix Firebird, BDE alias, locks, and port 3050 before repairing tables.
- Document alias paths after every migration.