Here’s How to Efficiently Debug QuickBooks Error OL 222

The moment you come across the QuickBooks error OL 222, you incur the following alert warning message that says, “WebConnect Branding- QuickBooks is unable to verify the Financial Institution Information for this download. Please try again later”. You mainly get the error when in the process of importing the .QBO file from your online bank account. As a result, in this informative article, we have explained every crucial piece of data about the technical issue. The blog focuses on the reasons that trigger the error along with three methods to fix the same. You must give it a complete read till the end in order to gain every minute detail and get a better clarification on the error code OL 222 in QB.

If you are struggling with the QuickBooks Desktop banking error OL 222 or have any questions about it, we recommend you connect with the team of certified QuickBooks professionals by dialing our Toll-Free 1.855.738.2891. Our experts’ team is available for you round the clock and helps you fix various issues that pop up in QuickBooks.

Top Factors That Gives Rise to the Bank Feed Error Message OL 222 in QuickBooks

If you are not aware of the fact why such an issue is coming up constantly, then you must have a look at the listicle we have provided below. All the reasons have been mentioned briefly-

1. One of the major reasons for encountering the glitch could be some formatting issues in the .QBO file.
2. Another quite common factor can be that you are using the outdated version f your QuickBooks Desktop, due to which the error triggers continuously.
3. Last but not least, if there has been some technical issue with the FIDIR.txt file, there is a higher possibility of receiving the error.

If you are looking for different ways of resolving the bank institution error, move on to the next section of this blog.

You may also read : QBDBMgrN not running on this computer

What are the Debugging Procedures to Remove the QuickBooks Desktop Error Code OL 222 Appropriately?

Are you facing trouble in rectifying the issue even after trying out multiple attempts? Do not get worried! We have explained three different troubleshooting methods that will definitely help you fix it successfully. Refer to each solution concisely-

SOLUTION 1: Make Changes in the .QBO File

1. In the very beginning, you must move to the location where the .QBO file has been saved.
2. Now, make use of any text editor app to access and open the file.
3. After that, you are required to search for ‘&’.
4. Once found, delete ‘&’ for the text. Since it is an invalid character, you need to remove it.
5. In the next step, move on to the ‘File’ section and tap on the ‘Save’ button.
6. In the final step, quit the current screen and make an attempt to access it in the QuickBooks Desktop.

SOLUTION 2: Check for the Newly Released Updates for Your Version of QuickBooks Desktop to Update It

1. Before proceeding with the QB Desktop update process, you must make sure that you are not using the QB application.
2. Now, move to the Windows desktop and look for QuickBooks.
3. Once found, right-click on its icon and tap on the ‘Run as Administrator’ option.
4. After that, you are required to open the No Company Open window. To have access to the window, keep holding the ‘Ctrl’ key and double-click on the QuickBooks icon together.
5. In the further step, shift to the ‘Help’ section and click on the ‘Update QuickBooks Desktop’ option.
6. Next, jump to the ‘Options’ tab and hit ‘Mark All’ and ‘Save’.
7. Now, move towards the ‘Update Now’ tab and checkmark the ‘Reset Update’ checkbox.
8. Tap on the ‘Get Updates’ option to download the currently available updates.
9. The final step is to close the QuickBooks program and restart it to install the updates.
10. Once you reopen your QuickBooks, a message pops up on the window asking you to install the update; tap yes to confirm the action.
11. After it is done, reboot your computer device.

Although these two methods must work in eliminating the problem, if you still continue to receive the glitch, check out the third solution.

You may read also : QuickBooks Connection Has Been Lost

SOLUTION 3: Fix the Issue By Re-Downloading the FIDIR.txt File

1. If the QuickBooks software is already running on your system, close it.
2. Now, you must open the FIDIR.txt file and copy all the text available in it.
3. To paste the text, create another text file.
4. After you paste it, store the file on the Windows desktop and give it the same name, ‘FIDIR.txt’.
5. Permanently remove the former FIDIR.txt file. To do it, on your keyboard, press the ‘Option’ key.
6. Next, from the Finder app, tap on the ‘Go’ button and after that, ‘Library’.
7. You are now required to move to the following path- ApplicationSupport / com.intuit.QuickBooks 20XX/ Downloads.
8. Remove the FIDIR.txt file and go back to the Finder app.
9. Click on ‘Applications’ and access the No Company Open screen. You can open it by pressing the ‘Ctrl’ key and clicking twice on the QB Desktop icon.
10. Further, shift to the contextual menu and hit ‘Show Package Contents’.
11. Now, go to the ‘Contents’ folder and double-click on it.
12. After that, click twice on the ‘Resources’ folder and look for the ‘FIDIR.txt’ file to delete it.
13. From the desktop, copy the FIDIR.txt file and paste it into the Downloads and Resources folder.
14. Finally, perform the same set of instructions for the .QBO file.

As we come to a conclusion, we are hoping that by now, you must have been able to get rid of the QuickBooks error OL 222 accurately. Our pro-advisors have entirely tried and tested each troubleshooting method given here. However, at times, even while performing these fixing methods, you might unexpectedly encounter other problems. In such a circumstance, we suggest directly getting in touch with the technical support team to have a one-to-one conversation with one of the experienced professionals through our Toll-Free 1.855.738.2891. You can also connect with them if you require any further assistance regarding the same issue.

You may read also : QuickBooks Error 1722