QuickBooks Error OLSU-1011 -- Bank Feed Setup Directory Connection Failure

Error OLSU-1011 blocks bank feed setup when QuickBooks cannot reach the financial institution directory, and our engineers can resolve it with targeted connectivity and configuration steps.

When adding a bank or credit card account for online banking in QuickBooks Desktop, the setup can fail before it even presents a list of financial institutions. Error OLSU-1011 is one of the more common blockers our engineers see during that initial directory-contact phase, and it is almost always tied to a network, configuration, or outdated-software condition rather than a problem with the bank itself.

What the Error Message Says

The full dialog typically reads:

"QuickBooks is having a problem connecting to the bank. Please check your Internet connection and try again. (OL-301, OLSU-1011)"

In some installations the wording is shorter:

"There was a problem connecting to the financial institution directory. Error: OLSU-1011."

The message appears during the Add Account flow — after selecting Banking, then Bank Feeds, then Add Account — when QuickBooks attempts to download the live list of supported financial institutions.

What the Code Means

The OLSU prefix identifies a category of errors that occur during the setup and activation phase of Bank Feeds, before any transactions are ever downloaded. The 1011 suffix specifically indicates that QuickBooks could not establish a connection to the financial institution directory server. Think of it as a handshake that never completed: QuickBooks reached out, but the response it expected never came back intact.

What Triggers It

Our engineers trace OLSU-1011 to a handful of recurring causes, listed here from most to least common:

1. Outdated QuickBooks release. The Bank Feeds directory protocol changes over time. A QuickBooks installation that has not been updated in several releases cycles may be using a deprecated connection method.
2. Internet Explorer configuration issues. QuickBooks Desktop relies on Windows Internet Explorer components for secure connections, even on systems running newer browsers. If IE's security zones, TLS settings, or cache are misconfigured, the directory call fails.
3. Firewall or antivirus blocking QuickBooks. Security software may silently block the QuickBooks executable from reaching external servers, especially after a signature update.
4. Bank Feeds tracking data is corrupted. The local files that track activation state can become damaged, causing the setup wizard to fail on contact.
5. Intermittent network outage. A temporary DNS or routing issue between the workstation and the directory servers.

How to Fix It

Work through the following scenarios in order. Stop when the Add Account wizard successfully loads the bank list.

Scenario 1: Update QuickBooks to the latest release

1. With your company file open, go to Help and select Update QuickBooks Desktop.
2. Go to the Options tab and select Mark All, then Save.
3. On the Update Now tab, check Reset Update and select Get Updates.
4. When the download completes, close QuickBooks and reopen it. When prompted to install the update, accept and restart.
5. After restart, return to Bank Feeds > Add Account and test.

Scenario 2: Reset Internet Explorer settings

1. Close QuickBooks.
2. Open Internet Explorer (if it is not pinned, search for it in the Start menu).
3. Go to Tools > Internet Options (or the gear icon).
4. On the Advanced tab, scroll to the Security section and confirm that Use TLS 1.2 is checked. Uncheck TLS 1.0 and TLS 1.1 if enabled.
5. Click Restore advanced settings, then Apply and OK.
6. On the Security tab, select Trusted Sites, click Sites, and add https://*.intuit.com and https://*.quickbooks.com.
7. Close Internet Explorer, reopen QuickBooks, and test the Add Account flow.

Scenario 3: Configure firewall and antivirus exclusions

1. Open your security software and locate the application permissions or firewall rules section.
2. Add the following executables to the allow list:
   • QBW32.exe (located in the QuickBooks install directory)
   • QBW32Pro.exe, QBW32Premier.exe, or QBW32Enterprise.exe depending on your edition
   • FileMovement.exe
3. If you are on a domain network, ask your IT administrator to verify that ports 80 and 443 are open for outbound traffic from the QuickBooks workstation.
4. Temporarily disable antivirus real-time scanning, test the Add Account flow, then re-enable it. If the test succeeds, the exclusion is confirmed.

Scenario 4: Create a new Bank Feeds configuration

1. Close QuickBooks completely.
2. Open the folder containing your company file (the .QBW location).
3. Look for files with the extensions .ND and .TLG that share your company file name, along with any files named FMServer.ini or located in a Bank Feeds subfolder of the QuickBooks installation directory.
4. Rename the Bank Feeds configuration file to include .OLD at the end (for example, FMServer.ini.OLD).
5. Reopen QuickBooks and attempt Add Account again. QuickBooks rebuilds the configuration on launch.

Scenario 5: Verify general connectivity

1. Open a browser and navigate to a standard website to confirm the workstation has internet access.
2. If the browser also fails, restart the router or contact your network administrator.
3. Flush DNS by opening a Command Prompt as Administrator and running ipconfig /flushdns.

How to Prevent It Recurring

Keep QuickBooks on the latest maintenance release by enabling automatic updates. Periodically verify that TLS 1.2 remains enabled in Internet Options, as Windows updates can occasionally reset it. If your organization pushes security software updates centrally, confirm that the QuickBooks executables remain on the allow list after each update cycle.