CC-601 Error - Fidelity Brokerage Accounts not updating.

124»

Comments

  • bobadel
    bobadel Quicken Windows Subscription Member

    I just spoke with Fidelity and the tech INSISTED that Quicken ticket #12266898 (which refers to this thread) represents Quicken taking complete responsibility for the CC-601 problem, which I presume also means complete responsibility for fixing it.

    The tech also INSISTED that Fidelity has not provided QFX or QIF files for manual download in the 4 years he has been with Fidelity. Fidelity does provide a CSV file, but Quicken will not accept it because the provided data elements, and their order, do not meet Quicken's specifications. I was not able to fix this. Has anyone?

  • bdantes
    bdantes Member, Windows Beta Beta

    Did you speak specifically Fidelity Electronic Channel Support (which is a different group than standard technical support)? It’s true that Fidelity has not supported QIF for awhile, but it has definitely not been FOUR years — that rep was mistaken.

  • jeffrub27
    jeffrub27 Quicken Windows Subscription Member ✭✭

    I'd like to understand more about the Quicken files that are working. I've tried reverting back several versions back into 2025, creating a new file and adding just one simple Fidelity account and still have the issue. It confusesd me when I hear that some files are working and others are not. I thought everyone that was using Fidelity with Quicken was having the same CC-601 error.

  • bdantes
    bdantes Member, Windows Beta Beta

    I also find it confusing. As I noted in an earlier post, with my file that is still working, I actually see TWO connections to Fidelity during OSU: one for my cash management account, and one for all the rest. I have zero explanation how that ended up that way. But there were so many attempts over the last six months in disconnecting and reconnecting to Fidelity I’m not surprised. It does seem that everyone making brand new connections to Fidelity are caught up in this current error. I tried briefly to see if I could detect any difference in logs between the two files when connecting to Fidelity to see if I could spot a problem, but it became too tedious.

  • jeffrub27
    jeffrub27 Quicken Windows Subscription Member ✭✭

    Guess what everyone, I think it may be fixed. I just updated all of my accounts and see new transactions. I need to go through and verify for sure that everything is working, but there appears to be progress! Fingers crossed.

  • jeffrub27
    jeffrub27 Quicken Windows Subscription Member ✭✭

    It looks like I am being blcoked from this thread. Why?

  • jeffrub27
    jeffrub27 Quicken Windows Subscription Member ✭✭

    I think it may be fixed now. I just updated and see downloaded transactions.

  • NiralS
    NiralS Quicken Windows Subscription Member ✭✭

    Just tried to update my account and it worked. Values are updated and match!!!

  • Philip107
    Philip107 Quicken Windows Subscription Member ✭✭✭✭

    The OSU passed just now so that looks fixed, but I don't see any new transactions. My Fidelity accounts are set up for simple so there isn't a lot of activity in them.

    ----Quicken User since 1998 ----

  • jeffrub27
    jeffrub27 Quicken Windows Subscription Member ✭✭

    Oh my bad. I was on the wrong page ;-(

  • bobade
    bobade Quicken Windows Subscription Member ✭✭

    I just updated. The Fidelity Elan VISA updated! Unfortunately, the brokerage accounts and CMA did not update, though the CC-601 error was gone.

  • bdantes
    bdantes Member, Windows Beta Beta

    I wouldn't celebrate success yet. While the CC-601 errors disappeared from my new file on OSU, only transactions from the credit card came down. No transactions from my cash management account (that did come down in the old file) were downloaded. My fear is that they've re-introduced the bug where auto-redemptions of MMFs were missing as well as others. We should wait for @Quicken Kristina or @Quicken Laura to comment here or in the general announcement.

  • bdantes
    bdantes Member, Windows Beta Beta

    "Reset Account" worked to bring down those missing transactions. So I'm going to start off with a fresh copy of the old working file and see how things go the next few days. Jury is still out.

  • OTN
    OTN Quicken Windows Subscription Member ✭✭
    edited 2:16PM

    Olaf UPDATE: It appears that for me as of an hour ago the 601 errors (visible and hidden) are now fixed and the dead re-link process is now live and works. I will copy/paste the exact process I used to rebuild this link below. I used Gemini AI and augmented per below:

    Olaf To Gemini: I use Quicken Deluxe (latest client Windows version) and have 10 brokerage accounts at Fidelity Investments with a single Web Fidelity log-on, and 10 matching accounts in Quicken. I use quicken to download Fidelity transactions on a daily basis.  Quicken and Fidelity have recently established a new transaction download protocol via a Intuit-owned link-connection interface named "Express Web Connect +" that uses the OATH/Token protocol.  This link often breaks without error display or other warning. In addition, the relink process is not defined, is not reliable, and relink success or failure is not displayed.  The user can think everything is fine, but after a reauthorization and re-linking that appeared successful, transactions still do not download, again with no error display.  This is very frustrating as the vendor reauthorization and re-linking process in Quicken TAKES A LONG TIME and when not successful the complete process needs to be repeated in the hope that "this time it will work".

    Olaf To Gemini: Question:   What is a reliable follow-on process and steps to re-establish the "Fidelity Investments transaction download link to Quicken"?  Be sure at the beginning to include  steps and reasons to: (1) Refresh Sign in, then (2) Reset Cloud Data.

    RESPONSES BELOW ARE ALL GEMINI "AI": They work!

    Gemini To Olaf: Re-establishing a reliable connection with Fidelity after the transition to Express Web Connect+ (EWC+) can be exceptionally finicky because the "token" that authorizes Quicken to talk to Fidelity often gets "stuck" or out of sync between your local data file and Quicken’s cloud servers.

    To fix this, you must perform a "deep clean" of the connection data. Following these steps in this specific order is the most reliable way to clear out the "ghost" settings that cause the silent download failures you are describing.

    Step 1: Refresh Sign In

    Reason: This forces Quicken to refresh your Quicken ID registration token. If this token is stale, it can't properly negotiate the OAUTH/Token handshake with Fidelity, leading to successful-looking logins that don't actually pass data.

    1. Go to Edit > Preferences.
    2. Select Quicken ID & Cloud accounts on the left.
    3. Click Sign in as a different user (this is effectively a "Sign Out" button).
    4. Type yes to confirm and sign out.
    5. Quicken will prompt you to sign back in. Use your existing Quicken ID and password.

    Step 2: Reset Cloud Data

    Reason: Quicken uses a "Cloud Dataset" to manage EWC+ connections. If there is a mismatch between your local file and the cloud (which happens often when a link "breaks"), Quicken may think it’s connected when it isn't. Resetting the cloud data wipes the cloud's memory of your bank links so you can start fresh.

    1. Go to Edit > Preferences > Mobile & Web.
    2. Click Reset your cloud data.
    3. Follow the prompts to complete the reset. This does not delete your transactions; it only clears the sync and connection metadata.

    Step 3: The "Deep Clean" Re-Link Process

    After refreshing your ID and the Cloud, follow these steps to re-establish the Fidelity link. Crucial: You must deactivate all 10 Fidelity accounts before trying to reconnect any of them.

    A. Deactivate All Fidelity Accounts

    1. Go to Tools > Account List.
    2. Check Show hidden accounts at the bottom left (important in case a "ghost" account is hogging the connection).
    3. For every Fidelity account, click Edit > Online Services tab > Deactivate.
    4. Switch to the General tab and delete the "Financial Institution" name and "Account Number" fields. (This ensures Quicken doesn't try to use old, cached ID info).
    5. Click OK and repeat for all 10 accounts.

    B. Revoke Access at Fidelity (External)

    1. Log into the Fidelity website directly.
    2. Go to Profile > Security > External Data Sharing.
    3. Find Quicken (or "Intuit") and Revoke or Remove access. This clears the token from the bank's side so a brand-new one can be generated.

    C. Reconnect and Link

    1. In Quicken, go to Tools > Add Account.
    2. Search for Fidelity Investments.
    3. Follow the prompts to log in. This will open your web browser for the OAUTH/Token authorization.
    4. Crucial: On the Fidelity authorization page, make sure all 10 accounts are checked.
    5. Once redirected back to Quicken, you will see a list of accounts. Do not click "Add".
    6. In the Action column for each account, click the dropdown and select Link to existing account.
    7. Carefully match each Fidelity account to its corresponding Quicken account name.

    Summary Table: Why it fails.

    Problem

    Root Cause

    Solution

    No Error Display

    Quicken thinks the Token is valid, but the Bank has revoked it.

    Refresh Sign-In (Step 1).

    Silent Fail (Success msg, no data)

    Cloud Data is out of sync with Local Data.

    Reset Cloud Data (Step 2).

    Link won't "stick"

    Hidden or old "Direct Connect" settings are interfering.

    Deactivate all accounts & clear "General" tab (Step 3A).

  • bdantes
    bdantes Member, Windows Beta Beta

    But I'll just say again for the record, if any of the engineers at Quicken actually read these forums, the amount of acrobatics necessary to keep Quicken running correctly (Validate, Super Validate, Reset Account, fresh copy of the file, on and on) are just absurd. The product should use a bonafide ACID database and "just work." Nothing should go into production without rigorous QA.

  • GGmaster
    GGmaster Quicken Windows Subscription Member ✭✭

    Just tried the update based on recent thread entries. The process took a lot longer but returned now with CC-501 error and no updates. I was consistently getting CC-601 errors since 3/2. So it looks as if the issue is still not resolved.

  • lmacmil
    lmacmil Quicken Windows Subscription Member ✭✭✭

    Quicken just downloaded all the February transactions from my Fidelity account. I didn't do anything different from what I've done in the past. The problem is fixed for me.

  • Scott BJ
    Scott BJ Quicken Mac Subscription Member ✭✭

    All is working for me as well! No error messages and the amounts are as expected.

  • bobschwa
    bobschwa Quicken Windows Subscription Member

    Thankyou, even though the fidelity/quicken link was reestablished, I kept getting error codes, until I tried this. Extremely helpful, thankyou !!!

  • Houstee
    Houstee Quicken Windows Subscription Member ✭✭

    Working for me again. Did nothing on my side.

  • bobade
    bobade Quicken Windows Subscription Member ✭✭

    After Olaf's "Deep Cleaning" I have received all of the Fidelity data EXCEPT two Fidelity Elan VISA transaction dated 3/10/26 (today). BUT …these two transactions are pending on Fidelity's website.

    Good work! Not only do we have a fix, but we have a procedure to use IF (WHEN?) the problem occurs again.