"Corrupt" QEL file

John Dozier

Every time I run the Validate and Repair routine, I get the message: "QEL: The old file was corrupt and only some of the data has been recovered." What do I do about that? Is there a way to delete a QEL file and start from scratch? This error message seems to be related to the problem with my budgets always getting deleted. Everything else seems to work about as expected. I am a very long time Quicken user.

markus1957

Try the damaged data file troubleshooting process from the Quicken support site.

https://www.quicken.com/support/advanced-data-file-troubleshooting-correct-problems-quicken-windows

Note that the QEL file does exist; it is packed inside the qdf container that is the Quicken data file.  A long time ago it was a separate file.

A super-validate can be accessed by holding Shift + Ctrl keys while clicking Validate and Repair. Use that if the regular Copy/Validate process does not resolve the issue. Don't skip Copy; it is a record by record copy routine and not a Windows file copy.

Frankx

Hi @John Dozier,

Can you tell us what version of Quicken you are running?  I don't think recent versions (i.e. for the last 8 or 9 years) have used separate QEL files.

NotACPA

Actually, the QEL file, along with several other "helper" type files is encapsulated into the combined QDF ... within which is the actual QDF/etc.

markus1957

Try the damaged data file troubleshooting process from the Quicken support site.

https://www.quicken.com/support/advanced-data-file-troubleshooting-correct-problems-quicken-windows

Note that the QEL file does exist; it is packed inside the qdf container that is the Quicken data file.  A long time ago it was a separate file.

A super-validate can be accessed by holding Shift + Ctrl keys while clicking Validate and Repair. Use that if the regular Copy/Validate process does not resolve the issue. Don't skip Copy; it is a record by record copy routine and not a Windows file copy.

John Dozier

I am running 2020 Version R24.14 Build 27.1.24.14

John Dozier

Thanks Markus1957. I did the Copy routine, opened the new copy, and ran the normal validate. The resulting validation log showed no QEL read errors. Now to test drive it for a while.