OL-393-A error with Wells Fargo bank
I have been getting this error for two days. Transactions are downloading. I have tried to re-set the account, but no help. I see a post for the same error in September that has since been closed. The last comment on that post said, We are aware and working on it. Pleae provide info on the status for the current error. This error began yesteday. Today, I was presented an update to Quicken, which I performed. The program is now slower, and the problem persists.
Comments
-
Hello @Roger Everson,
This error can occur for a number of reasons. For more information as well as troubleshooting instructions that may help resolve this error, please refer to this error-specific support article.
Hope this helps!
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
I have reviewed that article and followed the guidance there several times. No help.
0 -
Thank you for confirming you have already tried those steps, though I’m sorry to hear that the issue persists.
However, as stated at the bottom of the article, if the issue persist you will need to contact the financial institution for further assistance:
"You will need to contact your financial institution for assistance. Quicken does not have access to the financial institution's servers to be able to correct the problem.
This may require you request to speak with an online services specialist that handles transaction download issues at the financial institution. If your financial institution states they can't assist, an escalation with them may be necessary."
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 -
@quickenAnja
I contacted Wells Fargo. Their accounts are behaving as they should. Transactions are being downloaded to Quicken and transactions generated within Quicken are being performed properly by bank, such as sending checks and online transfers. Account balances are being updated and reconciled as they should, yet the error persists. They believe that the error is being generated erroneously by Quicken software. Please look into this.
0 -
See above.
0 -
Quicken live support was able to resolve the problem. This is in reference to case number: 10609887. This thread can be closed.
0