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

OLB Error with update that was rolled out 11-6-26

ChrisBiggers

The latest update caused the common OLB error when trying to download transactions. Rolled back to version R69 to fix it.

This has gotten to be a common error with updates!

Find more posts tagged with

Windows

download transactions

Update

OLB

Direct Connect

Comments

NotACPA

Care to clarify what the "OLB error" is?

If you mean "Online Banking", there are a great number of possible errors. Which SPECIFIC error are you getting?

Sceptic

@NotACPA It is the error that has been happening to quite a few FIs this morning that use Direct Connect.

https://community.quicken.com/discussion/7977556/ol-290-b-error-multiple-financial-institutions-direct-connect

https://community.quicken.com/discussion/7977559/update-11-6-26-multiple-financial-institutions-ol-290-b-error

NotACPA

Found that OL-290-B was posted after I replied here.

This thread STILL needed clarification as there are many possible Online Banking errors. OP might have gotten some other error

ChrisBiggers

There was a post from Quicken in the Community about the OLB-290-B error that was happening after they rolled out the update on 11-6-26. I wasn't getting that SPECIFIC error, but assumed the update was causing the OLB-221-A (Specific enough for you?) error I was getting.

I have had updates cause OLB errors before, but they might not always be the same number, so I left the number off on purpose.

Rolling back to version R69.25 Build 27.1.69.25 (Specifics again) fixed my issue.

I was trying to help and assumed people could Google or search the Community for more help.

I sincerely apologize for not meeting the high standards you have for making posts on this subject.

Sceptic

@ChrisBiggers No worries! There were several posts yesterday about the OL-290-B error. There were other posts yesterday about users getting the OL-221-A error as well. They seem to be related to the new release R70.20. Quicken is currently looking into it and hopefully it will be resolved soon.

Rolling back was a good idea. I have done so myself and will try to update again to R70.20 when we get an "all clear" from Quicken.

Just as a general note, when community members ask for error codes or other specifics, it's usually because the same update can sometimes trigger different symptoms for different users. The extra details help determine whether everyone is dealing with the same underlying issue or several separate issues that happen to appear at the same time.

Hopefully we're all a little closer to understanding what's going on with R70.20. Every report helps build a clearer picture, so thanks for sharing the details of what you experienced.