Fidelity OL-293-A error

2»

Comments

  • halzenner
    halzenner Quicken Windows Subscription Member ✭✭

    I think I might have solved my problem based on some clues mentioned above. Months ago a Fidelity deferred annuity was changed from Metlife to Nationwide. The Metlife transactions (and all other accounts) updated when I downloaded transactions. The Nationwide transactions did not download, so I had to manually enter transactions (they don't support direct downloads unfortunately). Anyway, couple of days ago all my Fidelity transactions stopped downloading and I got an error. I just DEACTIVATED just the Nationwide account and suddenly everything started to work again. Your mileage may vary…..

  • roenie
    roenie Member ✭✭✭

    I am having the same issues. My last update was Jan 29 at 4:12 pm. Has not updated since. Hope this gets fixed fast.

  • Jimzim
    Jimzim Quicken Windows Subscription Member, Windows Beta Beta

    Same problem - both Quicken Mac and Quicken Windows. Last update was Jan 29. Problem goes beyond Quicken. Same problem downloading from Fidelity with "Investment Account Manager." However, Banktivity was still downloading correctly as of 2/1.

  • jhaninger
    jhaninger Quicken Windows Subscription Member ✭✭

    Having the same problem for the last 3 days. Screenshot above is exactly what I am receiving.

  • jhaninger
    jhaninger Quicken Windows Subscription Member ✭✭

    Same issue for 3 days

  • Bill O'Neil
    Bill O'Neil Member ✭✭✭

    I deactivated my Fidelity Annuity after reading the above comment and it is downloading correctly now. Must be something with the annuity downloads ???

  • Dave508
    Dave508 Member ✭✭✭

    I have had the same experience. I deactivated the Fidelity Deferred Annuity (Right-click on the annuity account in account bar → Edit account → Online services tab → Deactivate). After doing that all of my other Fidelity accounts update normally. So as said earlier - it's something to do specifically with Annuity accounts. They all use the same login information (of course), so they're treated as a group when updating. If one account update fails, the others don't get updated, so deactivating the specific Fidelity problem account (Annuities) is (evidently) the only way to circumvent the error until it gets resolved.

  • warferg
    warferg Quicken Windows Subscription Member ✭✭

    I did as Dave508 described - Deactivated my Deferred and Inherited Annuity accounts. My remaining Fidelity Accounts updated normally.

  • Quicken Jasmine
    Quicken Jasmine Quicken Mac Subscription Moderator mod

    Hello All,

    Thank you for joining this thread and coming to share more information. We truly appreciate your patience and support as we continue to investigate this issue!

    -Quicken Jasmine

    Make sure to sign up for the email digest to see a round-up of your top posts.

  • Marvin Gardens
    Marvin Gardens Quicken Windows 2017 Member ✭✭✭

    I just spoke to Fidelity, They said the problem has been identified and they will install a fix tonight (Monday, 2 Feb 2025) so downloads should work tomorrow.

  • JHVT
    JHVT Quicken Windows Subscription Member

    2/3/25 11:33AM EST still not fixed

  • Joannkv
    Joannkv Quicken Windows Subscription Member ✭✭

    Worked for me also. Deactivated the Fidelity annuity account and the other accounts downloaded.

  • cwinkler
    cwinkler Quicken Windows Subscription Member ✭✭
    edited February 4

    Updated my Quicken this morning (OSU) and Fidelity completed with NO ERRORS! For now looks like the fix works :-). And I do have a Deferred Annuity.

  • pdmcmanus30
    pdmcmanus30 Quicken Windows Subscription Member ✭✭

    I was able to reconnect all my Fidelity accounts this morning (02/04/2025).

  • Dan DeWeese
    Dan DeWeese Quicken Windows Subscription Member ✭✭

    Since January 31 I was getting error code OL-293-A for my Fidelity accounts, when updating. The problem seemed to be resolved on the morning of Feb 4. By evening the problem was back with a different error code (OL-332-A).

    Quicken Version R60.20

  • Jeff Howe
    Jeff Howe Member ✭✭✭
    edited February 5

    I have started getting the OL-332-A too.

  • Marvin Gardens
    Marvin Gardens Quicken Windows 2017 Member ✭✭✭

    Now I am getting OL-332-A which says my userId/password is incorrect, but I it works logging on to the web site.

    This is getting old.

  • mrphil
    mrphil Member ✭✭
    edited February 5

    Me too, started 2/4, 2/3 and before was fine.

  • Sven79
    Sven79 Member
    edited February 5

    Same here. We have two separate accounts. When I went online via browser, I had to re-verify my ID with texts to phone, or texts to app. After that was done, I was able to login via browser with no issues; so I thought the quicken issues were over, but it was still no dice.

    I tried resetting the account, but quicken responded that it was "unable to do so". I then deactivated one of the two quicken Fidelity accounts, but now I can't reactivate it.

    Quicken acts like I'm an idiot and that my pw or user ID is wrong, which it absolutely is NOT! (i use the same credentials now via browser or phone app, and it works perfectly for this account.)

    I saw that they "closed out" some error with Fidelity for Quicken Mac users today; I'm guessing that their "fix" introduced a new issue for this with PCs. It's just too great of a coincidence that this error "Close-out" perfectly coincided with PC users getting locked out of their Fidelity accounts.

    Quicken has no way to talk back with additional verification questions that sometimes occur during the login process, but perhaps it's high time they start looking for a way to do so. They could just do some regular coding, call it "AI" and then charge more for the product.

  • Geobrick
    Geobrick Member ✭✭✭✭
    edited February 5

    Update 2/5/2025 3:20pm Pacific time - It worked for me today.

    That's the error I'm getting today. I'll wait until things settle before I try deactivating or resetting the accounts

    .

  • PatrickP
    PatrickP Quicken Windows Subscription Member ✭✭

    Just started having a problem with Fidelity connection. Basically telling me my password is incorrect. It's not.

    Hope they are working on this. I sent the log from the problem.

  • craigcabrey
    craigcabrey Quicken Mac Subscription Member

    For what it's worth, I am seeing this issue on the Mac version.

  • RichardScheel
    RichardScheel Quicken Windows Subscription Member ✭✭
    edited February 5

    I am also encountering this bug. I download my Fidelity data every evening, and suddenly tonight it fails consistently with OL-332-A. I verified that the password in the Quicken password vault is identical to the password that I just used to log in to my Fidelity account through my web browser. I also tried closing & restarting Quicken, and the error continues to occur.

  • cwinkler
    cwinkler Quicken Windows Subscription Member ✭✭

    Mine is so far working OK since the recent fix (knock wood). Hope your issues get sorted out soon, and it doesn't start doing that with mine.

  • Dave508
    Dave508 Member ✭✭✭

    All of my Fidelity accounts updated fine beginning yesterday (Tuesday 2/4/2025) and continue today. Thanks Quicken Support for working this out!

  • dmann54
    dmann54 Quicken Windows Subscription Member ✭✭

    A couple of things that came to light in the recently resolved Fidelity Investments OL-293-A login error:

    Fidelity does not show Quicken, as a third party app, having access to my accounts. Other financial institutions that I use with One Step Update list Quicken as having third party data access. I am curious if other Quicken users are experiencing the same issue. I wonder if this is a potential security vulnerability with Fidelity and or Quicken. If you log into Fidelity.com account, click on PROFILE, scroll down to SECURITY, then scroll down to LOGIN & EXTERNAL DATA SHARING. If you click on VIEW FIDELITY ACCESS it will show how your data is being shared. I believe Quicken SHOULD be listed as a THIRD PARTY USING YOUR USERNAME AND PASSWORD. When I brought this to Fidelity's attention they did not have an answer.

    One other item is that when I perform a OSU in Quicken, there are no security "KEYS" following the Fidelity accounts to be updated. All other OSU accounts indicate the KEY.

  • Marvin Gardens
    Marvin Gardens Quicken Windows 2017 Member ✭✭✭

    I have an automatic update scheduled for about 9:00 AM. It failed with OL-332-A. At 10 AM I tried again and now it works. Go figure

  • cwinkler
    cwinkler Quicken Windows Subscription Member ✭✭

    I just checked mine. Fidelity is the same, no mention of Quicken as a 3rd party app. But my OSU does work so I'm OK for now. In Quicken, none of my investment accounts / institutions have the key after them, only the banking and credit card accounts. So that may be what you're seeing in yours.

  • philjuli
    philjuli Quicken Windows Subscription Member

    This Fidelity error is fixed for me now, however whenever I do a One-Step Update, all of my other connected accounts get a receive a CC-800 error, and I have to re-authorize all of the accounts. Even after I fix the CC-800 error, each time I do a One-Step Update, this happens all over again.