QFX import broken after update to R65.17 (Vanguard OL-221) [Edited]

Thank you.

I got a little lucky to find an old Vanguard download that imported w/o any problems. That helped a lot to figure out what changed.

Apparently Quicken does not have a Vanguard account for testing. If they did, they would have seen right away what the problem was. Quicken, if you're listening, consider getting a Vanguard account. I know you can't enroll in every financial institution but Vanguard is a big one - you probably have lots of customers who get upset if the Vanguard import breaks.

By the same token, Vanguard should have a copy of Quicken to test imports if the QFX output code changes. I think it's on sale at Walmart now :) . They also could have quickly figured out what had happened and avoided this whole situation.

Thank you though, Vanguard, for the quick turn around.

As I said earlier, this was not a Quicken problem. In fact, I think Quicken handled it pretty well. They opened an issue and the Quicken error messages posted here were relevant. I didn't notice those message until after doing the debugging grunt work - they would have saved some time.

I just tried to download from Vanguard and import QFX. I still received the same message. I did a search for "

<INCOMETYPE>REINVEST" and did not have any text in my QFX file. Not sure what the next steps are (wait for quicken ?)

I had the same sequence that I experienced last time. When I double-click on the QFX file, I get a message that the "feature you are trying to use is on a network resource…." and wants me to identify the quicken.msi file location. I don't have the MSI file and not sure why it wants me to reconfigure quicken. I also tried to reassociate the Qfx file with quicken app (even though it is the default app) and got the same message. I am a windows 10 user on latest update with quicken ver. R65.17 Build 27.1.65.17

Not sure exactly what to look for in the quicken log files. The ".QXF file import results" indicates that there are no file import results.

This was working (early November?) and failed recently - along the same time that others reported on this message thread.

Yay! The issue seems to have been resolved!

I am having what I think is the same problem, but with every .qfx file I download after R65.17. When I double click the file it launches the quicken installer.

If I go into the quicken menu it lets me import the files correctly, so I'm at least functional.

This just happened to me, but I'm not sure if it is from the end of November release everyone is talking about. I can't believe I didn't try downloading any QFX files in December. Possible, but it would surprise me. I really don't want to uninstall and reinstall. After a long day at work dealing with software issues, I'm just exhausted with this stuff! It will need to wait until the weekend, and a strong cup of coffee.

@mwheeler… at least the current instance of this problem (I am experiencing it myself since 17 JAN and I download two QFX almost daily) and IMHO, it starts with the QFX file from the banking institution. The QFX download is not from Quicken … it is from whatever banking institution being used that formats the file for its customers who use Quicken. Granted, there maybe some bank institution / Quicken middle-layer service formatting the file, but these latest files downloaded FROM USBANK (in my case) are CORRUPTED (Note: the QFX download for my Commerce Bank account still works fine). The QFX files are way inflated size-wise and full of duplicated OFX tags. My normal size file is 3-8KB. Since 17 JAN those files are 96-300KB filled with duplicated tags. One unique <FITID> tag was seen 32x. Quicken is choking on the file. And for those of us in the software industry (yes, I spent a few years of my career messing with ONES and ZEROES too) … this is a GIGO problem (Garbage In, Garbage Out)! Until the QFX files are fixed (by the banking institution or middle-layer service) … Quicken will keep barfing up the OL-221 errors.

How I suspect it works … Quicken obviously sets the QFX file format (a Quicken proprietary flavor of OFX) and publishes that to the banking institutions who want to provide that downloadable format to its customers. Given many banking institutions seem to be having this problem over a time spread, possibly Quicken has changed the specification for that format and banking institutions are picking it up sporadically, changing their files. And Quicken's latest release is not importing it properly. Obviously there is a reason, but the files appear CORRUPT. When a known good file is DIFFd with a problem file, all sorts of BAD JUJU is seen!

LarryG

"There are only 10 types of people who understand BINARY ... those who DO and those who DON'T!"