Issue is NOT RESOLVED with USAA Federal Savings Bank (Direct Connect) - OFX Error 2000
Quicken Anja posted on 5/25 that the issue was resolved: RESOLVED 5/25/23 This issue has been marked as resolved. However, this Alert will remain available for those who may still be experiencing this. Thank you!
The issue just occurred again this morning. Error Code: 2000. Error Last Seen: 2023-05-27 12:36:05 +0000
Comments
-
Hello @mcevilley,
Thanks for reaching out to the Community!
Our internal servers show this issue as resolved which is why the Alert was marked resolved. If you are still experiencing this issue after the Alert was marked resolved, then you will need to contact Quicken Support directly for further assistance and possible escalation if they see fit.
We apologize for any inconvenience! Thank you.
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
I posted to inform the community that the issue remains despite the statement that it is resolved. I engaged support just now and they confirmed issues with USAA persist. Unfortunately, with the holiday weekend, it will be Tuesday before any follow up investigation/troubleshooting can resume.
1 -
Maybe we get an update now that it's Wednesday?0
-
I'm having the same issue with USAA: connectivity throws "Error 2000" and it says "this is usually a temporary issue" but it's been on and off (mostly off) all week.
0 -
As of this morning and after re-authorizing my 6 USAA accounts, "Quicken Connect" is connecting and downloading transactions without error. I did have to re-authorize on Monday and again on Tuesday.
"Direct Connect" has not worked at all this week and reported "Error 2000".
Per a Quicken notice - last updated 5/22/2023 - USAA is phasing out "Direct Connect".
"USAA has discontinued Express Web Connect, and is in the process of discontinuing Direct Connect. They are updating to a new method of providing data to applications like Quicken, called EWC+ (Quicken Connect in Mac)."
Hope this helps …
1 -
Thank you, mcevilley. Have changed to Quicken Connect and hope it resolves the issue.0
-
Still an issue. Part of the phase out of Direct Connect was to notify customers of the switch.
That has not happened.
0 -
Still an issue on Direct Connect. Worked a couple of times in the last week, but not yesterday or this morning. I switched over to Quicken Connect per @mcevilley's suggestion (thanks, BTW!) and it works again.
0 -
Good to know that folks are having some success with Quicken Connect.
It remains frustrating because again today I had to reauthorized all the 'already authorized successfully' accounts. There was a note in that Quicken Notice cited above about the need for reauthorization. However, it should not be a persist requirement, it should not be the norm.
0
