Fix QuickBooks Desktop Error OL-334: Bank Feed Troubleshooting

Last reviewed 2026-07-04 4 min read

Resolve QuickBooks Desktop error OL-334 and similar OL/OLSU bank feed codes. Learn why Direct Connect fails and how to permanently switch to QBO or CSV imp

When QuickBooks Desktop displays Error OL-334 during an online banking session, it means the software encountered a problem communicating with your financial institution's servers. This error belongs to the broader OL/OLSU family of bank-feed errors. If you are running an older, discontinued version of QuickBooks Desktop, this error is increasingly common—but it is entirely fixable without upgrading your software.

Understanding the OL/OLSU Error Family

Error OL-334 is part of a larger family of online banking errors in QuickBooks Desktop (which includes nearby codes like OL-301, OL-332, OL-362, OLSU-1016, and others). When you see an OL or OLSU code, it generally indicates a breakdown in the data transfer between your bank and your company file. The exact numerical code often depends on the specific bank and how its servers respond to QuickBooks' connection attempts. For anyone keeping an older Desktop version alive, these errors usually signal that the automated connection method is failing.

Common Causes of Error OL-334

Several factors trigger this error, particularly on unsupported versions of QuickBooks:

Server-side changes: Your bank updated its online banking protocols or security certificates, rejecting the older connection from legacy QuickBooks.
Expired Direct Connect: Intuit discontinues Direct Connect services for older software versions at the end of their lifecycle. Once this happens, automated downloads simply fail.
Temporary outages: Routine bank website maintenance or temporary server downtime.
Company file damage: In some cases, the bank feed data within your .qbw company file has become corrupted.

How to Fix Error OL-334

Follow these steps to restore your banking downloads. Because the exact steps and menu labels vary slightly depending on your specific version of QuickBooks Desktop, these instructions are kept intentionally general.

Check for temporary outages: Wait 24 to 48 hours. If your bank is experiencing routine server maintenance, the error will often resolve on its own.
Update your bank list: Go to your Bank Feeds center and choose to update your financial institution directory. This ensures QuickBooks is pointing to the correct current URLs for your bank.
Deactivate and reactivate the feed: In the Chart of Accounts, edit the affected bank account, toggle the Bank Feeds settings to "Deactivate All," and then attempt to set it up again. This forces QuickBooks to establish a fresh connection.

The Durable Fix: Web Connect and Manual Import

For users on discontinued versions of QuickBooks Desktop, automated Direct Connect will eventually fail permanently. Intuit shuts down the servers that facilitate these direct, automated connections for older software. Attempting to force an automated connection will only result in recurring OL-334 errors.

The permanent, durable solution is to bypass the automated server connection entirely. Instead, log into your bank's website directly, download your transactions as a QuickBooks Web Connect (.qbo) file, and import them manually into your Desktop software. If your bank does not offer .qbo files, you can usually download a standard CSV or Excel file and convert it for import. This method keeps your older QuickBooks Desktop fully functional indefinitely, entirely independent of Intuit's server lifecycle. For comprehensive, step-by-step instructions on formatting and importing these files, review our master guide to importing bank transactions with QBO, CSV, and IIF files.

Preventing Future Bank Feed Errors

To keep your Desktop installation running smoothly, rely on manual Web Connect (.qbo) imports as your standard workflow rather than relying on automated Direct Connect. Additionally, keep your QuickBooks Desktop updated to the final released patch for your specific year. If you operate in an offline environment, ensure your computer's system clock and date settings are perfectly accurate, as severe clock drift can cause secure connection failures when downloading data from your bank's website.

When to Suspect Company File Damage

If you have switched to manual .qbo imports and are still receiving OL-334, or if the error is accompanied by sudden sluggishness, missing lists, or the "Verify/Rebuild" utility flagging problems, your company file itself is likely damaged. The bank feed data structures within the file may be corrupted. In this scenario, running the built-in Verify and Rebuild Data utilities is your first step. If the utilities fail to clear the error, you may need professional intervention to repair a damaged QuickBooks company file to restore full banking functionality.