Skip to main content

Fix the "Database connection failed" error when using external or NAS drives

Victor
  • Updated
Catalogue corrupted, database error, can't open catalog, can't repair catalog, database connection failed, can't open session, database connection failure, catalog won't load, database connection

If you're using an external drive or NAS to store your catalogs or sessions, you may run into the error message "Database connection failed." This typically happens when the database or its temporary files are interrupted during use, which can lead to corruption.

This article explains what causes this error, how to verify if your database or session is affected, and what steps to take to recover.

Contents

Compatibility

This article applies to users storing catalog databases or session files on external drives or network-attached storage (NAS), and who encounter the error "Database connection failed."

Why this error happens

SQLite uses a temporary file named .journal whenever it writes data to a catalog or session database. If your external or NAS drive has a weak connection, or if you quit Capture One unexpectedly, this .journal file may get stuck or corrupted. That can prevent both the catalog and session files from loading properly, resulting in a database connection error.

How to check if the database is corrupted

You can check your .cocatalogdb or .cosessiondb file using the following SQLite command in the Terminal:

sqlite3 "file:nameOfCatalog.cocatalogdb?mode=ro" "PRAGMA integrity_check;"

Here's how to run a command in the Terminal on Mac.

Before you run it, make sure to replace the nameOfCatalog.cocatalogdb  with the entire path to the document, e.g. /Users/<you>/Pictures/MyCatalog.cocatalog/Catalog.cocatalogdb

If the result is ok, the issue is likely with the .journal file — not the database or session file itself.

Note: For Windows, you may need to install SQLite3 from here.
The path would look something like this: 

C:\Users\<you>\Pictures\MyCatalog.cocatalog\Catalog.cocatalogdb
 

What to do if the .journal file is the issue

If a .journal file exists next to your .cocatalogdb or .cosessiondb file and the integrity check passes:

  1. Quit the app completely.
  2. Locate the .journal file (it has the same name as the database or session file, with .journal at the end).
  3. Delete the .journal file or rename the main file to disconnect it from the .journal.
  4. Restart the app.

Note: This may result in the loss of your most recent changes, including unsaved edits or session progress.

What to do if the database is corrupted

If the integrity check does not return ok, the catalog or session file itself is corrupted. Unfortunately, the app can't recover from this. If you have backups, restore from one of those following this guide: How can I recover a corrupt Catalog? or this one: How can I replace a corrupted/broken Session?

Preventing database issues

Related articles