File won't open
Solid Accounting company files are SQLCipher-encrypted SQLite databases
with a .solid extension. If yours won't open, work through these in
order.
"Wrong password"
The most common cause is, well, a wrong password. There's no way to recover or reset a forgotten password — the file is genuinely encrypted. Options:
- Try variants — case sensitivity, common typo patterns, or a previous password if you've changed it recently.
- Restore from a Cloud Backup (Settings → Cloud Backup → Restore). The backup uses a separate encryption phrase, not the file password — so this works even if you've forgotten the file password.
- Restore from a local backup (
.solid.bakfiles in your file's directory).
If you don't have a backup and can't remember the password, the data is unrecoverable — that's the security guarantee. Contact support and we'll help you start a fresh file from the most recent statements you have.
"File appears corrupted"
Two scenarios — different fixes.
App crashed mid-write
The file might have a stale write-ahead log (.solid-wal). Solid
Accounting auto-recovers on next open in most cases. If it still
won't open:
- Close the app completely.
- In the file's directory, you'll see
yourfile.solidplusyourfile.solid-walandyourfile.solid-shm. Don't delete those yet. - Open Solid Accounting and try opening the file again — auto-recovery triggers.
- If that fails, restore the most recent
.solid.bakover the corrupted.solidfile.
Disk hardware errors
The file's bytes are physically corrupted. SQLCipher won't open them.
Restore from Cloud Backup or local backup. Run disk health checks
(smartctl on Linux/Mac, CrystalDiskInfo on Windows) before continuing
to use that drive.
"Old file format"
You're opening a file from a much older version. Open the file from File → Open rather than double-clicking — the app will run a schema migration automatically. Make sure to back up first.
"File locked by another process"
Another instance has the file open. On Windows, check Task Manager for stray Solid Accounting processes. On Mac/Linux:
lsof | grep yourfile.solidKill the offending process and try again.
Multi-user mode
If you're using multi-user, only the host writes; clients connect via mDNS. If a client can't see the file, the host probably crashed — restart the host machine.