QuickBooks Error OLSU-1024 -- Online Banking Setup Update Failure

Error OLSU-1024 blocks QuickBooks Desktop from updating online banking setup; our engineers walk through every trigger and the steps to restore connectivity.

QuickBooks Desktop error OLSU-1024 appears when you are activating, updating, or deactivating online banking services (Web Connect or Direct Connect) for one or more accounts. The error halts the setup wizard before the connection to your financial institution is finalized, leaving the account in a partially configured state. Resolving it requires identifying which layer of the connection stack failed — the bank's profile data inside QuickBooks, the QuickBooks desktop configuration, or the financial institution's own servers — and then re-running setup cleanly.

What the Error Message Says

The full on-screen text reads:

"Your last online connection was not successfully completed. QuickBooks is having a problem going online. [OLSU-1024]"

In some installations the message is preceded by a shorter line: "There was a problem completing your request" before the OLSU-1024 code appears in the detail pane.

What the Code Means

The OLSU prefix identifies the failure as an online services setup error — not a live download or send-payments failure. The 1024 suffix specifically indicates that QuickBooks received an unexpected or incomplete response from the financial institution's server while negotiating the initial service-activation handshake. In practice, the bank server accepted the credentials but never returned the account-profile data QuickBooks needs to finalize the link, or QuickBooks could not parse the response because the local bank-branding file was stale.

What Triggers It

Our engineers see OLSU-1024 most often in these scenarios, listed from most to least common:

1. Stale or corrupted FIDir (financial institution directory) file inside the QuickBooks installation folder.
2. Damaged .ND and .TLG network descriptor files preventing the company file from communicating with the online services module.
3. Bank-side provisioning gap — the account is enabled for online access on the bank's website but not yet activated for Direct Connect or Web Connect delivery.
4. Outdated QuickBooks Desktop release that no longer matches the current OFX server standards the bank publishes.
5. Conflicting or duplicate account mapping left behind from a previous failed setup attempt.

How to Fix It

Scenario 1 — Refresh the financial institution directory (most common)

1. Close QuickBooks Desktop completely.
2. Open the File Explorer and navigate to C:\ProgramData\Intuit\QuickBooks (enable hidden folders if you do not see ProgramData).
3. Locate the folder named FMS and rename it to FMS_OLD.
4. Inside the same QuickBooks folder, locate the file FIDir.txt and rename it to FIDir_OLD.txt.
5. Reopen QuickBooks, then go to Banking → Bank Feeds → Bank Feeds Center.
6. Select Set Up Bank Feeds for the affected account. QuickBooks downloads a fresh FIDir.txt and rebuilds the FMS folder automatically.
7. Complete the setup wizard and test the connection.

Scenario 2 — Rebuild the .ND and .TLG descriptor files

1. Close QuickBooks on every workstation.
2. In the folder that holds your company file (.QBW), find the two files that share the same base name as your company file but end in .ND and .TLG.
3. Right-click each one and rename it by appending .OLD (for example, CompanyFileName.QBW.ND.OLD).
4. Reopen QuickBooks. The program recreates clean descriptor files on launch.
5. Retry the Bank Feeds setup.

Scenario 3 — Verify bank-side provisioning

1. Log in to your financial institution's online banking portal through a browser.
2. Confirm that the account in question shows online banking as Active and that Direct Connect or Web Connect is listed as an available delivery method.
3. If the bank requires a separate sign-up for Direct Connect (some do), complete that enrollment first.
4. Note the exact legal name and routing number the bank displays, then match them character-for-character in the QuickBooks setup wizard.

Scenario 4 — Update QuickBooks Desktop to the latest release

1. With QuickBooks open, press F2 to open the Product Information window.
2. Check the Version and Latest Release lines. If they differ, close the window.
3. Go to Help → Update QuickBooks Desktop → Update Now.
4. Check Reset Update, then click Get Updates.
5. When the download finishes, close and reopen QuickBooks, accepting the prompt to install the update.
6. Restart the computer if prompted, then retry setup.

Scenario 5 — Clear a partially configured account

1. Go to Lists → Chart of Accounts.
2. Right-click the affected account and choose Edit Account.
3. On the Bank Feeds Settings tab, select Deactivate All Online Services and click Save & Close.
4. Reopen the account, return to the Bank Feeds Settings tab, and run Set Up Bank Feeds from scratch.

How to Prevent It Recurring

• Install QuickBooks maintenance releases as soon as they ship; outdated releases are the single most preventable cause of OLSU errors we encounter.
• Before reactivating an account after a bank merger or rebrand, deactivate the old connection first rather than editing it in place.
• Avoid running Bank Feeds setup while antivirus or firewall software is pushing an active scan; schedule scans for off-hours so they do not intercept the OFX handshake.
• Keep only one instance of QuickBooks open on the network when configuring online services for the first time.

If none of the scenarios above resolves the error, the company file itself may have structural damage in the online-services tables. In that situation our engineers can run a targeted data repair on the affected account records and restore clean Bank Feeds connectivity.