Was entering health data and got this error. I see others have had this issue. My database is stored on my hard drive and not in the cloud. Any steps I need to take?
Run the Tools when you open database.
If you can’t open the database you will need to do a Restore.
Thanks. No problems opening, ran the tools. I’d discovered those yesterday, as I had a crash with no error.
1 Like
Slow down? Maybe you are getting ahead of the background updates of the database. If the app is stuck on that error, you may have to force it closed and reopen to clear the problem. Then pickup where you left off.
LOL. I do entries fairly quick as I have a gazillion keyboard shortcuts setup for genealogy via Typenator (awesome for data entry!). I don’t think that’s the issue though 
Even though your data base is not stored “in the cloud”, I still have to ask: exactly where is it stored? What is the full file path to the database, like starting with C:\ if you are on Windows or starting with the root folder of the disk if you are on a Mac.
/Users/username/RootsMagic/Keller Hanch Family Tree.rmtree (username removed for privacy)
Mac user. Only my backup file is in my Documents folder, which is synced to iCloud.
1 Like
Under those circumstances, it’s very difficult to think of anything that would lock the database. I’m pretty well stumped. But here is one more wild guess. Are you running Time Machine? I suspect you are not.
1 Like
Yes, I run Time Machine. But I fail to see how that would have any effect.
Time Machine not a cloud sync, but it’s a sync. Time Machine can be trying to do a backup at the same time RM is trying to update the database.During that time, the database might appear locked to RM.
I’m not a Mac user, so I’m not fluent with all its nuances. So for example, I’m by no means certain that it was Time Machine that locked your RM database. But certainly there was something that locked your RM database. And Time Machine has to be a prime suspect.
The fundamental problem is that Time Machine as well as cloud based sync services are designed to recognize that what you might call “normal” files are being saved and to avoid syncing them or backing them up during the save. But database files such as the RM database are saved as they go. There is not a save at the end because RM has already saved as it goes. Syncing services seem to be unable to recognize when a database that saves as it goes is actively saving, and therefore such services seem to put a database that saves as it goes at risk.
It’s not just RM. It’s really any app that uses SQLite as its database. And the best I can tell, it’s not just SQLite, its any database that saves as it goes.
There are very expert Mac users who assert that Time Machine does not have this problem. But there is also a great deal of discussion online about Time Machine having this problem. Do an online search for SQLite and Time Machine and make up your own mind.
I’m a heavy DevonThink pro user, (database); it’s basically always running. Zero issues with Time Machine. Actually, I have zero issues with any of my software, up until RM. But everything is else is built for Mac.