Error SQLITE_CANTOPEN: unable to open database file

Troubleshooting
1

Hi,
I know this has been discussed several times in the forum, but I didn’t find a solution to my case.
I get the SQLITE_CANTOPEN: unable to open database file when trying to open a .tpy file stored on an external hard drive (together with the image files). I also updated to macOS 13.6 recently. Please let me know if you need more information.
Thanks in advance for your help

2

P.S. if I move the file to my hard drive I can open it (with the wrong image paths of course)

3

Can you elaborate on how you’re opening the file?

4

sorry if that wasn’t clear. I can open the file when I copy it to my mac HD. But the file is stored on an external disk, where also the image files are. If I copy it to my macbook I don’t get the error, but I can’t use the file either, because the images are on the external drive. Does that answer your question?

5

by the way, this problem occurs with all .tpy files I have stored on the external disk.

6

That’s odd. If for some reason Tropy didn’t have write access to the external drive it should at least open the file in read-only mode. And if it had no read access it would fail with a permission denied error. (Though it’s possible that you would see the can’t open error if any if there’s no read access to the parent directory).

How are you trying to open the file? Via the menu and the OS file picker? Or by dragging and dropping the file from Finder?

In either case, can you check the log file after you get the error? The log file should contain the full path to the .tpy file that Tropy was trying to open. Please check if that path looks like the correct path. If open the Terminal app you can use the following commands (with the full path to the file) to check the file permissions to see if there’s anything that could point to a permission-related reason:

ls -l /your/tpy/file
xatttr /your/tpy/file
7

Hi! Sorry I completely lost track of this. Thanks for your reply.
I find this in the .log file (see below) when searching for the file name (“Old Masters”). What it strange, I had only moved the file to Desktop to test if the file itself was damaged after the error. The path on the external storage seems correct.

{“level”:40,“time”:1702116629580,“type”:“renderer”,“name”:“project”,“stack”:“Error: ENOENT: no such file or directory, stat ‘/Users/ertlt/Desktop/Old Masters.tpy’”,“msg”:“failed to stat project file ‘/Users/ertlt/Desktop/Old Masters.tpy’”}
{“level”:30,“time”:1702116629580,“type”:“renderer”,“name”:“project”,“mode”:“r”,“msg”:“open db /Volumes/ScanDisk/Storage/Photos Kunstgeschichte/Old Masters.tpy”}