coreduetd

This is what I did to fix this issue on my MacBook Pro with Yosemite 10.10.1:

1. Download unzip sqlite-shell-osx-x86-*.zip from sqlite.org
2. Unzip it in the Downloads directory.
3. Open Terminal then
   1. mkdir ~/bin
   2. mv ~/Downloads/sqlite3 ~/bin
   3. cd /var/db/CoreDuet
   4. sudo cp coreduetd.db coreduetd.db.backup
   5. sudo sqlite3 ./coreduetd.db.backup .dump | sudo sqlite3 coreduetd.db.sqlite
   6. sudo mv coreduetd.db.sqlite coreduetd.db
4. In Console, coreduetd.log shows a stack trace starting with: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException'
5. There will be no more log entries after that.
6. Restart the computer.
7. Open Console again and inspect coreduetd.log - the file will be empty.

Hi there,

I had a similar problem on my iMac 21" - running Yosemite 10.10.2. After scouring around for solutions, I was going down the route described partly here and elsewhere of making a copy of coreduetd.db, dumping the contents and making a new copy and then importing the contents, and you get a clean data base.

Having done this in a working folder I was about to copy the new version (which according to Valentina Studio db manager, is now error free). I noted that my new version was pretty well half the size of the current working version (although with the same number of tables and fields, which is good).

I did my "usual" safe route of making another copy of coreduetd.db in the working folder (/var/db/CoreDuet/coreduetd.db) by renaming it (in this case to coreduetd_old.db). The instant I did this a a new copy of coreduetd.db appeared! Guess what, it was the same size as the "cleaned up" version I had just made. Problem cured, no issues...

So the simple solution for me is; rename the working copy of coreduetd.db (which is also now a copy you could go back to if required) and the OS automatically generates a new one, without errors!

Cheers, Derek