Fidelity One Step Update Error - No Error Code

aDail

Much like the Merrill Lync One Step Update Error I am now seeing the One Step Update Progress window showing an error

Nothing is downloaded but the Update Summary says everything completed successfully.

I have reported this problem to Quicken Support.

Would this be normal behavior when there are no transactions to download?

Boatnmaniac

No, this is not the normal behavior when there are no transactions to download. No new transactions will not result in any kind of OSU error.

Have you tried going to Account Register > upper right Gear icon > Update Now? It is not uncommon for Fidelity to return some OSU errors on Monday morning. I don't know why that is. But often Update Now will return a successful account(s) update.

aDail

Yes I did try using the Update Now within the Fidelity account register. It gave the same error behavior.
This is new as I've had my Fidelity connection working for a very long time. It started happening around the time frame that I got the announcement to update the connection method for my Merrill accounts (which is working as expected).

aDail

Update: I decided to try and updated my password on the website and within the Quicken password vault. It is working fine.

So my issue must have been a password / account locked issue causing that error. It would have been nice for the Update Summary screen to list a login issue as opposed to not showing any error.

Boatnmaniac

I'm glad you got it working for you. It does seem odd that you did not get an error code for the PW issue since an error code usually is present when there is a PW issue.

BTW, there are some special characters that should be avoided in PWs because they can cause Quicken connection issues. This is more of an issue with DC connections than it is with EWC connections but it can happen with either. Here is the link to the Support Article regarding this: https://www.quicken.com/support/password-vault-your-bank-could-not-use-password-you-entered/ .

aDail

@Boatnmaniac Yep…I had a "bad" special character in the other password. Now, I need to update my password notes to not hit this one again. Thanks for the assist you were a big help!