OL-295-A Error: Suncoast CU & Quicken Classic Desktop

JimInStPete

For the past few weeks, Suncoast Credit Union returns a 'OL-295-A' error when Quicken desktop app attempts a One Step Update (OSU). Via the Quicken Web assistant, Suncoast updates as expected. Anyone else experiencing issues with OSU and Suncoast Credit Union Web Connect?

Quicken Anja

Hello @JimInStPete,

We appreciate you bringing this issue to our attention!

You mentioned using "Web Connect" in your description, however, the OL-295 error is typically associated with Direct Connect. From what I can see internally, it appears that your account is currently set up using Direct Connect.

Before we begin troubleshooting, I’d like to gather a bit more information:

• Do you know if you normally use Express Web Connect or Direct Connect for this financial institution?
• To verify, please navigate to Tools > Account List and check the Transaction Download column. It should indicate which connection method is currently being used for this account.

Once you’ve had a chance to check, please report back and let us know!

JimInStPete

Anja, you are correct, I confirmed that the Suncoast Credit Union accounts are both Direct Connect. Why would bother of these accounts sync AOK when I launch the Web Assistant, and fail with an 'OL-295-A' error message when using the Quicken Desktop app?

Quicken Jasmine

Hello @JimInStPete,

Thank you for confirming that your Suncoast Credit Union accounts are connected via Direct Connect.

These errors usually appear when your computer cannot establish an internet connection with Quicken. Please note, these errors do not mean the computer has lost internet connection, simply that Quicken cannot establish an internet connection. Also, you may be able to successfully sign in to your bank's website but still receive the error in Quicken due to Quicken being unable to establish an internet connection. I suggest attempting the troubleshooting steps provided below in an attempt to resolve this issue. You can find these instructions and more information in this Support Article.

If you get this error with some (not all) of your banks

If only one bank is showing this error, it's likely a temporary issue; if this is the case, wait until the next business day and then try to update again.

In the meantime, make sure the settings are correct for accepting cookies.

1. Click the Start button and select the Control Panel.

• Windows 10: The Control Panel is located in the Windows System folder in the Start menu.

• Windows 11: Go to the Start menu and select All apps.

Then, go to Windows Tools and select Control Panel. 

1. Select Network and Internet... 

...then Internet Options.
​

1. Select the Privacy tab.
2. Click on the Advanced button.
3. If available, check the Override automatic cookie handling option.
4. Confirm that First-party and Third-party Cookies are both set to Accept.
5. Press OK, then Apply and OK again.
6. Close Internet Options and try updating Quicken again.

If the issue is not resolved after following the steps above, you will need to contact your financial institution to resolve this issue. Quicken does not have access to the financial institution's servers to correct the problem. This may require you ask to speak with an online services specialist that handles transaction download issues at the financial institution. If your financial institution states they can't assist, an escalation with the financial institution may be necessary. 

I hope this helps!

JimInStPete

Jasmine,

Thanks for your reply and I will try this last proposed resolution.

If this does not resolved the issue, I will not contact my financial institution as a next step to resolve this issue. Intuit Quicken should not provide features and capabilities that are unsupported by financial institutions, nor are end users in any position to resolve such issues.

If this is the level of support provide for complex technical issues, it's time to find a replacement for Quicken.

Quicken Jasmine

Hello @JimInStPete,

Thank you for your honest feedback—I completely understand your frustration, and I’m sorry this has been such a hassle.

I hear your concern about the burden being placed on the user when connection issues arise. The challenge is that, with Direct Connect, the financial institution is responsible for maintaining the connection servers and supporting the infrastructure that Quicken communicates with. That’s why, when something breaks on that end, we have to refer users back to the bank—Quicken doesn’t have access to those systems to make changes or fix the connection ourselves.

That said, I agree this can be frustrating, especially when the issue falls in a gray area. I’ll make sure your feedback is passed along internally, as we’re always looking for ways to improve the support experience and make this process less painful.

Please let me know how it goes after you try those last steps. I’m still here to help however I can!

JimInStPete

[Removed - Rant/Disruptive/Speculation]