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; } } }

State Employees Credit Union NC - OL-220-A Errors

UNCLogans

Is anyone else experiencing One Step Update, OL-220-A errors with NC SECU this morning?

I'm running Quicken Deluxe R29.12 (27.1.29.12)

Find more posts tagged with

Accepted answers

Quicken Anja

Hello All,

Thank you for reaching out to the Community to tell us about your issue, though we apologize that you are experiencing this.

We have opened an escalation ticket with our service provider for this issue and are working on getting this resolved. However, in order to assist the investigation while the issue remains ongoing, we are requesting that you please submit your log files by navigating to Help > Report a problem.

Alternatively, you can also contact Quicken Support directly so our support agents can collect your log files.

The more log files we receive, the better, and we apologize for any inconvenience this may cause! In the meantime, please, refer to this open Community Alert for updates.

Thank you.

All comments

Kasidea

Got this yesterday from SECU NC --so far fingers crossed it is working:

Dear Member,

Thank you for the message. We implemented a change in our direct connect method that should allow members to connect freely to Quicken using your login credentials. Could you please attempt to run a one-step update on your Quicken software and attempt to download your transactions again? Please let us know if this does not work for you so we can troubleshoot further. Thank you.

Kasidea

Oh and also I received a Quicken update Release R 33.19 this morning 5-7-21. I loaded the update before doing a transaction update with SECU NC so not sure whose fix worked or maybe it was a combination

Chris_QPW

@Kasidea I think is just how the message sent to you stated, your financial institution fixed it. If you read back there is a person didn't get the patch yet and still is working for him/her. You will also note that the release notes for the patch say nothing about it.

Barbara207

[removed - no soliciting] I think it is a Quicken problem and not on the bank's end because Quicken "fixed" it but then the errors started coming in again. Bank says it is Quicken and there is nothing they can do. Does anyone know for sure if it is a Quicken or bank problem??

jjmdj

All I know is that my SECU downloads have been working without problems since my system got the R33.19 update. It wouldn't surprise me if both parties had a hand in the fix.

Kasidea

OK my SECU downloads have been working since my May 7 message. Today I did the R33.24 update and NOW I'm getting error code OL-330-A and just now OL-294-A. NEVER FAILS updates for me cause issues. I usually don't do them right away because of this but today I read what it was about so did it. Sigh . . . These is becoming quite ridiculous!

Ken McAdams

Kasidea, I also have the R33.24 version. I just did a successful SECU download. You might want to start a new topic, mentioning those error codes.