I'm running the latest version of Quicken Premier under the latest version of 64-bit Windows Professional. I tried doing a OSD this morning and it was taking a long time to complete, so I shut down Quicken (with task manager; the upper right hand X didn't work) and tried again,
It still didn't complete, so I rebooted the computer and tried again. It still was taking a long time, so I let it keep trying and went on to doing other things on the computer. After about half an hour, I checked it again, and it still hadn't completed. I opened task manager and was about to shut it down again, but it then completed with messages about several banks, saying Quicken was having a problem with their server.
Not a giant problem. If I need to I can wait a day or two to get updates from those banks, but I was curious as to why it took so long for Quicken to tell me it was having a server problem. Anybody know?
FWIW, I'm seeing the same this. I'm using Quicken for Windows, version R45.21 on Windows 11 Home.
Experiencing the same problem here, starting today. One Step Updates don't complete, and I'm forced to use Task Manager to close Quicken.
I do notice that if I update Direct Connect accounts individually, there is no problem at all. These accounts update just fine. The issue seems to be only with the accounts using either EWC (like Discover), or EWC+ (like BOA and Chase). They hang on "Updating Account..." until I close Quicken with the Task Manager.
I have experienced OSU slowness also in recent weeks, but up to now, the process always completed. Today it doesn't, each time I've tried.
I had a similar experience this morning (Jan 2, 2023). Using Quicken R43.26 & R45.13; Windows 10 Pro 64-bit.
My problem today was limited to my accounts at the financial institutions that stopped offering "Direct Connect" downloads during 2022: namely, BofA, Chase, Discover and Schwab. Discover switched to only Express Web Connect; the other three switched to only Express Web Connect+. I still have quite a few Direct Connect financial institutions in Quicken and they had no download errors this morning (and their downloads completed promptly).
Each logon for each of the above financial institutions failed with a cc-501 error (when using One Step Update or Update Now).
[While the initial download process (OSU or Update Now) did take noticeably longer than usual, it completed successfully. Subsequent OSU attempts did not complete, and a subsequent attempt to Update Now for Chase took a long time, and still received the CC-501 error.]
Here is a link to the Quicken KB article for CC-501:
formatting link
The KB article is not particularly instructive as to the underlying cause of the error, and I doubt that following its suggestion to contact Quicken support will be very productive. I already see a lot of Quicken Community discussions reporting the same problem, so I suspect everyone will just have to wait until the responsible party (or parties: Quicken, Intuit, or the financial institution) is identified, and the problem repaired.
[When subsequent download attempts finished today, the CC-501 error text in Quicken said a "reauthorization" was required; but the "Reauthorize" button was inactive, so that approach was out. And initiating a reauthorization at the FI's (Chase, in my test) web site did not correct the CC-501 error. This doesn't seem like a true need-to-reauthorize issue.]
[All my financial institutions downloaded promptly with no errors yesterday (Jan 1, 2023)]
I forgot that I have accounts with Navy Federal Credit union that use Express Web Connect. I never include NFCU in One Step Update because NFCU requires 2FA which interrupts the OSU (I use Update Now to initiate downloads from NFCU, and I infrequently download from NFCU as there is very little activity there).
After my first post in this thread, I tested downloading from NFCU, and they too now have the CC-501 problem. So it appears that EWC and EWC+ are both involved in the problem, and it does not matter whether the financial institution was previously setup for Direct Connect downloads or not (NFCU has never offered Direct Connect).
When I restarted Quicken again, I got this message:
Known Issue: Errors or Slowness Updating Accounts
Due to an issue with our service provider, some users may experience errors or slowness while updating accounts. We are working with our providers to fix this as quickly as possible.
We recommend you try to update your accounts at a later time today. For updates on this issue, or to be notified when this issue is resolved, please follow the alert here.
Quicken, Inc. seems to have conflated some Community discussions whose symptoms are similar to what's being discussed here, but whose cause is not likely the same.
However, I noticed the following Community Discussion, which does appear to cover the problem discussed in this newsgroup thread:
NEW 1/2/23 Various banks - CC-501/Error 101; slowness in account updates
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.