Troubleshooting

Solutions to common issues with database connections, schema validation, and runtime execution in an5 ORM.

Active Context: Troubleshooting for Java on Sqlserver.

Connection Issues

1. Connection Refused or Host Unreachable

Symptom: ECONNREFUSED, Connection refused, or timeout trying to open database connection.

Diagnostic Checklist:

  1. Confirm the database service is running on the host and port.
  2. Verify network firewalls allow incoming traffic from your application IP.
  3. Validate connection string syntax for Sqlserver:
# Valid connection format for Sqlserver
DATABASE_URL=sqlserver://localhost:1433;database=mydb;user=sa;password=yourpassword;trustServerCertificate=true

SQL Server specific notes:

  • If connecting with self-signed TLS certificates, append ;trustServerCertificate=true.
  • Verify the SQL Server Browser service and TCP/IP protocol are enabled in SQL Server Configuration Manager.

Connection Diagnostic Test

Run a quick connection health test using your active language:


Schema & Code Generation Issues

1. Type Mismatch in Schema

Error: Invalid field type 'X' for provider 'Y'

Cause: The schema .an5 uses a type specific to another database dialect (e.g. BIT on SQLite or BOOLEAN on SQL Server).

Solution: Align field types in an5Schema/ with the dialect rules of Sqlserver:

  • Consult the Field Types reference for valid types per provider.

2. Output Directory Not Found

Error: Directory does not exist for generator output

Solution: an5Orm generates directories automatically. Ensure your user has filesystem write permissions in the workspace and verify outputs paths in an5Orm.config.js.


Next Steps