SafeCoreError Error:104: Why can’t I open my Safe?

In SimpleumSafe 3, the complete current message is “Cannot open Safe database (SafeCoreError Error:104)”. It means that at least one internal encrypted database could not be opened. Another error with additional technical details may appear below this message. Only that additional information may narrow down the cause; SafeCoreError Error:104 alone does not automatically mean that the Safe is damaged.

What SafeCoreError Error:104 means

SimpleumSafe uses several internal databases for encrypted metadata, settings, synchronization information, and transaction information. The current code uses SafeCoreError Error:104 as an umbrella error when one of these databases cannot be opened. The message alone therefore does not prove one specific cause.

The underlying technical error may, for example, point to one of these situations:

• The previous storage location or its parent volume is unavailable.
• The database cannot be read or written.
• The affected volume does not have enough free storage.
• SQLite reports that the database may be damaged.
• Another technical error prevents the database from opening.

The complete display and, if necessary, support review are needed to determine which situation actually applies. Incorrect file permissions are not established as a general cause of this error. When the underlying message indicates database corruption, the app explicitly directs the case to support instead of suggesting a manual repair.

1. Record the complete message

Write down the complete error text starting with “Cannot open Safe database (SafeCoreError Error:104)”, including every error name and code shown below it. A screenshot is also helpful if you can redact personal names and path components while leaving error names and codes readable.

Expected result: You can later tell support exactly which technical detail was named without opening files inside the Safe.

2. Check only the parent storage location

On Mac

1. In Finder, check whether the volume and the folder containing the Safe are accessible. Do not open the Safe package contents.
2. If the Safe is on an external drive, reconnect that same drive and wait until it is mounted in Finder.
3. If the Safe is on a network share or inside a folder synchronized by a file service, do not move it. Actively using a Safe in these locations is unsupported and can put data at risk; contact support for a controlled relocation.

Expected result on Mac: If the existing local storage location becomes available again, you can make exactly one new opening attempt after observing the backup and stop boundary below. If the volume or folder remains unavailable, stop and contact support.

On iPhone or iPad

Do not try to edit app-internal Safe files through the Files app or other tools. No further file check is intended here on iPhone or iPad; continue directly with the available device storage check.

3. Check free storage

Check the available storage on the Mac, iPhone, or iPad and—if the Safe is stored on a directly attached external drive—on that drive as well.

• Enough storage is available: Continue with the controlled restart.
• Storage is full or nearly full: Do not change anything inside the Safe. Free space only outside the Safe using your normal, backed-up process. If doing so would require moving or deleting the Safe, its package, or existing backups, stop and contact support.

Backup and stop boundary before another opening attempt

4. Restart SimpleumSafe once

1. Quit SimpleumSafe completely.
2. On Mac, confirm that the existing local volume is still mounted.
3. Start SimpleumSafe again and try to open the same Safe exactly once.

Expected result: If the Safe opens normally, do not make permission or package changes. If a documented backup process is already configured for this Safe, use it to create a current separate backup. If no backup process is configured or you are unsure, make no further changes and ask support. If SafeCoreError Error:104 appears again, do not repeat the attempt; continue to the support path.