1/2/23 - OSU Problems & CC-501 Errors (QWIN)
Comments
-
As of 01/03/2023 16:30 EST I am still unable to update any account individually or using ONE STEP UPDATE. 36 hours of now "waiting 10 minutes and try again". Same error message for individual accounts as OSU. "ONLINE SERVICE NOT AVAILABLE"
0 -
Mine are updating the transactions finally (ALLY and Chase) but not the online account balances. Still shows the online balance as being that as of the last reconciliation. Ugh, grrrrrrrrrr0
-
Contrary to some of the other posts, there is an alert
https://community.quicken.com/discussion/7926613/update-1-2-23-one-step-update-delays#latest
The latest addendum says the issue is fixed. I would say "Kinda" fixed. I did finally get all accounts downloaded, but it took an extremely long time (like 15 minutes).
For now, I would suggest starting the OSU and getting a cup of coffee or walk the dog and come back later.0 -
All working for me at 2:04 PM PST. Banks included BofA, Chase, Capital One, and others. 100% up and running.0
-
This is working for me once again as of 1/3/23 5:18pm ET.0
-
Patience rewarded! All accounts now connecting and downloading correctly. Thank you Quicken engineers - you can stop tearing your hair out.0
-
My Quicken is doing the same thing. But I have been having many issues with the program since this Fall. I am wondering if it may be due to my upgrade to Windows 11?
Does anybody know if Customer Support has been contacted about this issue?0 -
It is not working for me as of 1/3/23 5:45 Eastern Time0
-
Just tried downloading transactions again, time 5:55 Eastern. The program locks up after it says that the download from each institution is completed. When I reboot the program, no new transactions are posted to any of the accounts.0
-
CC-501 error when updating Bank of America at 6:15 pm ET. (Chase & Citi both updated without any problem.)0
-
This is about as messed up as I’ve ever seen from an Intuit/Quicken issue. What changed to cause this disaster?0
-
Clearly something wrong with the update. My laptop on build 27.1.44.28 still works fine with the same file, same accounts.0
-
TD Bank sync still failing after 2 days. When will the clowns stop getting out of the quicken development clown car...-1
-
> @Eric Tiffany said:
> TD Bank sync still failing after 2 days. When will the clowns stop getting out of the quicken development clown car...
when will Quicken users stop acting like you are? problem was evidently nothing to do with the software but was with third party services...blaming Quicken is just kicking the dog because it's there1 -
@quickenuser69 - while I agree it could have been couched differently, I can't let Quicken off the hook. They are the ones we bought this product from (and not the 3rd party) and THEY are the ones that decided to engage with this 3rd party. Where are the contractual terms, controls, etc. that require a levtel of performance of that 3rd party (which I think is Intuit) that gives the Quicken customers the performance level we expec - THAT is Quicken's responsibility.1
-
It doesn't help to presume that Quicken employees are inept. I really don't know why all of this happened, but to assume any of us understands the problem doesn't make any sense to me. Bottom line is they did respond and for me, everything now works.
I did reset the EWC accounts, and now the update is better than it has been in months. I truly hope that Quicken does well. There are no real alternatives, and I depend upon this application daily.
Thank you for working to resolve the issues.-1 -
One step update is updating USAA and Wells Fargo, but not AAmex and FCCU. Has anyone tried going to the unupdated accounts and deleting them on the bank, then re-connecting?0
-
Right click on your account, Edit/Delete Account, Online Services, Reset Account. That fixed all of my accounts that are EWC.-1
-
That did not work. In fact, it asked that SETUP to download as if it had never been done. The error I get has no number. Just that"Quicken's online service is unavailable at this time." Then says wait 10 min and try again.
1 -
Midfirst Bank is the only one not working for me...was several more yesterday...so progress.0
-
Is there any resolution to this yet? I still have one bank that will not update for 3 days now...all others are fine. Tried disconnecting the bank and reconnecting it and won't allow me to do that either.1
-
Wells Fargo direct connect accounts working fine but Wells Fargo express connect accounts still a problem.0
-
After 48 hours of OSU generating the message that Quicken online service is unavailable, I decided to restore a backup. May be purely coincidence, but OSUY worked after that.
0 -
So my banks are now updating but when Quicken tries to process and update accounts, the program freezes and I have to restart. None of the downloaded transactions update to accounts. Quicken, please fix.0
-
Update - all accounts are downloading new transactions (still a several minute process) but they are still not updating the online account balances for the accounts. They have not done so since Jan 1. Attempting an account reset does not remedy the problem and in at least one account it deactivated the online access and now is forcing me to go through a fresh setup. AND EVEN WORSE,... after redoing the online setup it no longer even shows an online balance or last online balance date for the account and now the whole register is off by the amount the balance was as of 1/1/23. This is really ridiculous! The only thing I have yet to try is entirely deactivating an account and restarting it.
(UPDATE - Deactivated online access for the affected Chase account, restarted Quicken, and setup online access again and STILL NO FIX. No online balance shown or available for reconciling). This is the same for my ALLY accounts and probably others I have not checked/messed with for fear of making things worse.
This is a royal headache for a vital piece of software.
Contrary to any moderator post suggesting the OLA problem is fixed, the failure to download a current accurate online balance means that only half the issue is resolved in some cases.
I created a new post about this elsewhere to try to get Quicken's attention to the Reconciliation part of this fiasco.0 -
Seems to work for me now, save for an issue with one of my AMEX CC accounts which has been an issue for a few months. One works the other does not. Quicken advised that this was a known issue. I understand that AMEX is changing formats shortly so I am hopeful this will be resolved.0
-
Similar to Tom above - I am having some success. Some of my accounts have downloaded the latest transactions and the balances reconcile, and the Mobile app is syncing again, but everyone once in a while it will error out and the next time finish with no issues. Note I had to go in to each OSU account and reset them before they started to work.
Overall some type of issue remains, as of 1141 PST the OSU took 5 mins before it did anything, and another five minutes before it successfully downloaded some new transactions.
When you exit the app, and it does that final mobile sync - that can be another 5 mins waiting for things to complete and shutdown.
In the long run - slow progress to a resolution, but not confident that everything will be up to date the next time I use OSU..
To Marks inquiry - I am using Win11 (latest update).0 -
Does anyone know why this is happening or will it magically disappear then reappear again at random? For the amount of money, they charge you think we would at least get an explanation. [Removed - Violation of Community Guidelines]0
-
@divina12253858 - it appears this latest issue (and maybe some of the others?) relates to the 3rd party that sources the transactional data from the banks and other financial institutions. so it appears that the way the process works is Intuit (the 3rd party) sources the data from the banks and other financial institutions and passes it along to us. So it's not the Quicken software that causes this issue, but "hiccups" in the ability for Intuit to either grab the information from the financials instituions and banks OR its ability to pass it to us.0
This discussion has been closed.