I’ve added much of this as a comment on another user’s post, "Continuing download issues with Fidelity (OL-220-A)" (
https://community.quicken.com/discussion/comment/20257715), but am starting a new thread in the hopes of getting a direct response from Quicken developers.
For the past several months I’ve had similar issues (OL-220-A) with Fidelity Investments and have had two open tickets (926-3521 & 914-7645) with no success.
We have validated and super-validated the file, and even using file copy to create a new version of the file. I get the same results each time, regardless.
When I deactivate the online access to all 5 of my Fidelity accounts, and then reconnect, Fidelity data downloads perfectly. Subsequent downloads succeed until new data is available from Fidelity. The next attempt after that successful download will then fail with OL-220-A, specifically with the following from the CONNLOG.TXT:
Parse error. Current object: INV401KBAL Missing Tag: TAG UNKNOWN
All subsequent downloads will fail until I deactivate/reactivate. Note that the data goes back to 1985, but only about 3200 transactions total between the 5 accounts.
I’ve contacted Fidelity and we’ve confirmed that creating an empty file and downloading transactions always works, even on subsequent downloads, and even when the downloads continue to fail in my main file.
I’ve been a Quicken user since 1987, and a software developer even longer. There is CLEARLY a bug in the Quicken software where some aspect of my file is putting the download into an unexpected state causing the download parsing to fail.
I commend most of your frontline tech support for doing their best to help, but they are understandably limited in how far they can go. When I asked to have this escalated to the software developers as a bug, one particular manger repeatedly insisted that I was wrong, and there was no way the issue was on the Quicken side.
As a software developer and experienced debugger, I'm happy to offer my services to help debug the download process in Visual Studio along with one of your developers, to help isolate the problem, or any other means to find a way to debug this.