I have a similar issue with a single institution - Investor360
I pulled the following from the Quicken logs:
20230707 16:56:51: QFN: Beginning send to https://api2.advisor360.com/external/quicken/ofx 20230707 16:56:53: QFN: End send to https://api2.advisor360.com/external/quicken/ofx, netstatus 0 20230707 16:56:53: Parse error. Current object: OFXFILERS Missing Tag: TAG UNKNOWN 20230707 16:56:53:
Looks to me like either the file received from Investor360 is bad, or the Quicken Parser is broken.
Who can assist?
Hello @jdnewman66,
Thank you for reaching out to the Community and telling us about this issue. I'm sorry to hear you're running into this problem. Is this happening when you are importing a .QFX file directly from the financial institution into Quicken, or is this happening when trying to download from the financial institution using One Step Update in Quicken?
Thank you.
Kristina,
This occurs when trying to download from the institution using One Step Update.
Thank you for your response,
If you haven't done so already, please follow the troubleshooting steps from this article:
If completing the Update Now process doesn't clear up the issue, try updating your accounts the next business day. This error may be caused by a temporary financial institution server outage or maintenance that may be resolved the next day.
If the issue is not resolved after waiting, you will need to identify the connection type of the affected account(s) to determine what next steps need to be taken. To do this, go to Tools > Account List, find the affected account(s), and confirm the connection type in parentheses in the Transaction Download column.
I resolved the issue on a call with Investor360 - The password for Investor360 cannot contain any special characters. Once I set a new password with no special characters, everything began to work.
[Removed - Language/Rant]
Please mark as resolved.
Thank you for your reply,
I'm glad to hear its working now, and thank you for posting the resolution, since that can help anyone else encountering the same issue.