nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SQLite Corruption of 2017 Records

dwchapmanjr

Version 9.1.0 (Build 901.61320.100)

macOS 26.5.2

But this started around Quicken for Mac 6 or 7 and MacOS 15. I've excluded the quicken file from AV scanner (ESET) and it still happens.

I've been dealing with this problem for a few years now where periodically I'll get an error about having to relaunch because of difficulties with the file.

It seems to be one account that has transactions going back to 2011 and its always a record in 2017. When I reconcile its off. I find the transaction by exporting a backup to CSV and comparing the differences between that last known good backup and the export of the current file.

Sometimes its a few days or even a few weeks and then it happens again.

CoreData: error: (11) Fatal error. The database at /Users/XXXXX/Documents/Quicken/XXXX.quicken/data is corrupted. SQLite error code:11, 'database disk image is malformed'
CoreData: error: SQLCore dispatchRequest: exception handling request: <NSSQLFetchRequestContext: 0x60000258e840> , Fatal error. The database at /Users/XXXX/Documents/Quicken/XXXX.quicken/data is corrupted. SQLite error code:11, 'database disk image is malformed' with userInfo of {
NSFilePath = "/Users/XXXX/Documents/Quicken/XXXX.quicken/data";

Find more posts tagged with

Accepted answers

All comments

Jon

I see you're storing your Quicken file in your Documents folder. Is your Documents folder being synced to iCloud? That can cause file corruption issues with Quicken.

If you're not sure, open System Settings, click on your Apple account at the top of the sidebar, then select iCloud and click on the Drive button. The "Desktop and Documents Folders" option should be turned off. If it's on and you don't want to turn it off, then you need to move your Quicken data file out of your Documents folder to somewhere else.

John_in_NC

Database corruption is quite rare, but can happen.

If you have a working file, I would File:Export:Quicken Transfer File (QXF)

Hopefully, that should work. If so, reimport that resulting QXF file into a new data file and it will have a fresh data base.

Note: this is a lower fidelity transfer format. Your transactional data will be retained, but things like reports, split orders, attachments, etc. will be lost. But, it will be in a fresh database.

See what that yields for you.

And as @Jon mentioned, make sure you never network or keep your active file on a web store. (Backups are fine.)

dwchapmanjr

No, I use Google Drive too but not synching Documents folder on iCloud nor Google Drive

dwchapmanjr

Yes, when I reopen, most of my data is there, mins a few transactions (always from 2017). I'll try the QXF. I don't use many of the features but if the transfers are gone, that'll be a pain. File is local and not synchronized.

John_in_NC

Transfers will not be lost in a normal QXF export→import.

dwchapmanjr

}
CoreData: error: (11) Fatal error. The database at /Users/XXXX/Documents/Quicken/XXXX.quicken/data is corrupted. SQLite error code:11, 'database disk image is malformed'
CoreData: error: SQLCore dispatchRequest: exception handling request: <NSSQLFetchRequestContext: 0x60000353f8e0> , Fatal error. The database at /Users/XXXX/Documents/Quicken/XXXX.quicken/data is corrupted. SQLite error code:11, 'database disk image is malformed' with userInfo of {
NSFilePath = "/Users/XXXX/Documents/Quicken/XXXX.quicken/data";
NSSQLiteErrorDomain = 11;
}
2026-07-10 15:08:28.708 Quicken[1178:9571] Sent 1 sessions to Bugsnag
2026-07-10 15:08:29.294 Quicken[1178:9527] Cloning database /Users/XXXX/Documents/Quicken/XXXX.quicken/data to file /var/folders//5tcykdn93l1dv63h0gvrrzv40000gn/T/RepairDocument.YsoPk1/data
2026-07-10 15:08:30.972 Quicken[1178:9527] Copying cloned database /var/folders//5tcykdn93l1dv63h0gvrrzv40000gn/T/RepairDocument.YsoPk1/data to replace /Users/XXXX/Documents/Quicken/XXXX.quicken/data
2026-07-10 15:08:30.976 Quicken[1178:9527] Database repair has completed

John_in_NC

And this means? I don't think many of us here can decipher those logs. :-) We're fellow Quicken users, not programmers.

Was this from trying to export to QXF? I sure hope not.