My DTPro default database Inbox is Locked. It shows thee DevontThink ‘lock’ symbol next to it. After searching numerous posts on the topic and applying fixes, permission changes with terminal, checking for lock in Get Info finder window, I have been unable to unlock the database. Interestingly, when accessing in Finder, the database file at location ~/Library/Application Support/Devonthink Pro 2, the file name: Inbox.dtBase2, and inspecting with ‘Show Package Contents’ I can see the lock file named: Devonthink.lock. I delete this file and then I watch that directory as I launch DTPro and see the file created again at that time.
Am I missing something in the DTPro interface that would allow me to easily unlock this inbox? Note: I have 4 other databases and those are fine.
Just a note… It’s really not wise to start deleting files that look promising.
Right-click (Control-click) the database and choose “Show in Finder”.
Quit DEVONthink.
In the Finder, move the Inbox.dtBase2 file to the Desktop.
Remove the .dtBase2 extension from the database file. The operating system will ask if this is ok - it is.
Press Command-I to bring up the Info window.
At the bottom make sure the permissions for your Account are set to “Read & Write”.
Click the button with the gear icon choose “Apply to enclosed items…”.
After this, add the .dtBase2 extension to the file, move it back to the App Support/DEVONthink Pro 2 folder and double-click it to relaunch DEVONthink.
Hello Bluefrog - Thank you very much for your reply and suggestion. I normally wouldn’t go down the road of deleting files that I don’t know anything about. However, I found that particular suggestion elsewhere on this forum in relation to this issue.
I applied your instructions, but no joy. The Inbox database is still showing as locked. I am open to any ideas/suggestions. Perhaps there is a way to preserve what is in the locked inbox and create a new one and move my info back into the new database?
This thread is seven years old. Probable best to open a support ticket rather than trying to troubleshoot using info that old. That is, unless you are running DEVONthink 2 on Snow Leopard!