nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OL-362A Errors

arlingpj

On October 26, 2023, I have been getting OL362 A errors from 3 separate financial institutions across 3 Quicken Files. This started after updating to the most recent Quicken version. As of 4:30 PM on October 27, 2023, Quicken is informing me to contact the 3 financial institutions to resolve the problem on my own. They claim they have not received enough customer complaints for them to contact the financial institutions to resolve the problem. Is anyone else having this issue?

Find more posts tagged with

Investments

Online Banking

Windows

Comments

Quicken Kristina

Hello @arlingpj,

To help with this issue, could you please provide more information? I can see when you reached out to support, they had you deactivate and reconnect the accounts. Did they also have you check for any hidden accounts that may be trying to connect?

If you haven't checked for hidden accounts yet, please do so. You can do that by going to Tools>Account List. If you have hidden accounts, there will be a checkbox near the lower left of the window that gives you an option to show them.

You will want to check for any accounts that are trying to connect, but shouldn't be (for instance, accounts that are no longer active, or were closed on the financial institution side). If an account thinks it is connected in Quicken, you will see the word "yes" in the Transaction download column.

If you do have any inactive or closed accounts that are trying to connect when they shouldn't be, please backup your Quicken file, then deactivate those accounts and test to see if the issue persists.

Thank you.

arlingpj

Thanks for the reply. I do not have any hidden accounts that are trying to connect. I continue to get the OL362A errors today. Again, this was not an issue until I updated to the latest Quicken version. My next step is to go back to the earlier version if you cannot get this corrected.

Thanks

Quicken Kristina

Thank you for your reply,

Since there aren't any hidden accounts causing the issue, the next step would be checking for file specific issues. I suggest that you try validating and/or super validating your data file. Please save a backup file prior to performing these steps.

Validate:

File
Validate and Repair File...
Validate File
Click OK
Close the Data Log
Close Quicken (leave it closed for at least 5 secs)
Reopen Quicken and see if the issue persists.

If the issue persists, proceed to Super Validate. If the issue is resolved after performing validation, then please disregard the instructions to Super Validate.

Super Validate:

File
Hold CTRL + Shift and click Validate and Repair File...
Super Validate File
Click OK
Close the Data Log
Close Quicken (leave it closed for at least 5 secs)
Reopen Quicken and see if the issue persists.

Please let me know how it goes!

arlingpj

I validated the file and successfully completed 2 updates!

Quicken Kristina

Thank you for the follow up,

I'm glad to hear it was able to successfully update. Are all accounts successfully updating now, or are any still throwing that error?

Thank you.

arlingpj

Kristina,

Unfortunately, I am getting the OL362 A errors once again. ????

Quicken Jasmine

Hello @arlingpj,

Thanks for reaching back out!

First, backup your Quicken file.

Navigate to Edit
Preferences...
Quicken ID & Cloud accounts
Click Sign in as a different user (or it might say Sign in using a different Quicken ID)
Follow the prompts to Sign Out
Sign back in using your Quicken ID (email) and password

Let me know how it goes!

arlingpj

Thanks for the prompt response. I followed your instructions. Unfortunately, I am still receiving the OL 362A error from both Fidelity and Vanguard.

UKR

Please follow these instructions carefully: https://www.quicken.com/support/message-when-using-online-services-ol-362

arlingpj

This was the first step that I tried last week. I still maintain it is related to the latest Quicken update since I did not have this issue prior to updating. What do you suggest I do next?

UKR

If you haven't done so already, I'd say it's time to call Quicken Support on the phone during posted hours of operation and request help. Let them do a screen share session with you to review the situation on your computer, to determine the nature of the problem and to figure out how to fix it.

Quicken Support:

To contact Quicken Support, please use this link only: https://www.quicken.com/support#contact-support and select ~~Chat or~~ Phone support.
Support is only available during posted hours of operation
The phone number can be found at the support website.
To start Chat or see the support phone number, your browser must allow popup windows from https://www.quicken.com
See https://community.quicken.com/discussion/7870684/faq-talk-to-support-does-not-respond#latest
If you are eligible for Premium Support (purchased separately or included as part of your subscription to Quicken Premier or HB&R) call the number that can be found at the top of your My Account page at https://www.quicken.com/my-account (US) or https://www.quicken.com/canada/my-account (Canada) when you log in with your Quicken ID. Place the call using the phone whose number is recorded in your account profile.
Other links or phone numbers found elsewhere on the Internet, even in some posts or emails received from other Community members, may not be from Quicken or may not be up-to-date. Use those at your own risk.
Unlike other so-called "Quicken support providers", the real Quicken Support is free for all currently supported versions.