Fix System Exception Errors in QuickBooks Desktop

Fix System Exception Errors in QuickBooks Desktop

In this article, we’ll discuss in detail how to fix system exception errors in QuickBooks Desktop. Users usually come across system exception errors while they work in their QuickBooks Desktop bank feeds center.

What’s mean System.Argument.Exception

  • System.Argument.Exception: The parameter is not valid.
    at System.Drawing.Image.FromStream(Stream stream, Boolean useEmbeddedColorManagement, Boolean validateImageData)at System.Drawing.Image.fromStream(Stream stream)at System.Windows.Forms.PictureBox.Load()at System.Windows.Forms.PcitureBox.set_ImageLocation(String value)at OLB_ Workflow.UICtrl_OLBWorkflow.SetILogo(String strFILogoPath)
  • System.ArgumentOutOfRange.Exception: The index was out of range.

Causes of System Exception Errors in QuickBooks Desktop

The error occurs due to…

  • Some special characters such as !@#$%^&* are included in the payee or vendor name.
  • Damaged or corrupt vendor, payee, or rule.
  • An Issue with the Microsoft that is installed in your system.

How to Fix System Exception Errors in QuickBooks Desktop

However, there are several ways to solve this problem and there are pretty chances the first solution itself solves the problem. Know how to resolve the System Exception errors in QuickBooks Desktop such as “System.Argument.Exception“ or “System.TypeInitializationException” when you work in your QuickBooks Desktop Bank Feeds Center.

The actions below should be followed to continue working on your bank transaction.

Step 1: Remove special characters from your vendor names

  • First, you have to go to Vendors and then you have to select Vendor Center.
  • Choose All Vendors from the Vendors drop-down option.
  • Look for Vendor names that contain special characters (!@#$%&*).
  • If so, choose Edit Vendor from the context menu when you right-click the vendor.
  • Select OK after removing the special character from the vendor’s name.
  • Instead of the special character, you can substitute words like “and” for “&“.

Solution 2: Switch to the classic (Register) mode

  • Begin by going to Edit and then you select Preferences.
  • Navigate to the Company Preferences tab after selecting Checking.
  • Select Classic Mode (Register Mode) under the Bank Feeds section.
  • Then you have to select OK.
  • Try again to match or add new bank transactions.

Solution 3: Restart the computer and try to access the bank statement again

  • Firstly, close your QuickBooks Desktop then restart your system once again.
  • After that open QuickBooks Desktop
  • Finally, access your Bank Feeds Center and try to open and download the bank statement.

Solution 4: Review QBWin.log for Error Messages

To see what might be generating the bank feeds error, you have to check your QBWin.log file. To do this you have to.

  • Locate and then open the QBWin.log file.
  • Look for any LVL_ERROR at the bottom of the window as you scroll down.
  • If you do, locate the solution by searching for it on our QuickBooks Learn & Support site.

Solution 5: Resolve Microsoft Component Issues

  • Another option is System.Argument when your computer has harmed Microsoft components, an exception error may occur.
  • Use the QuickBooks Install Diagnostic Tool to automatically identify and resolve problems with these components by downloading and running it.

Solution 6: Fix QuickBooks Banking Errors

  • For additional solutions, see Resolving Bank Feeds issues and errors including OL and OLSU errors.
  • When using the Bank Feeds Center, do you continue to receive errors? The problem could be with your bank account in QuickBooks or with your financial institution.
  • Not to worry, simply follow these standard bank feed troubleshooting methods to help identify whether the issue is with your bank or the link between it and QuickBooks.

Solution 7: Completely uninstall QuickBooks

After checking with your bank, if the error persists, clean reinstall QuickBooks. This replaces the installation files for your QuickBooks Desktop software and fixes a variety of problems, including bank feed failures.

You can be sure that your company file and everything connected to it won’t be impacted.

Read more-- QuickBooks Windows Firewall Disabled Exceptions Not Defined

Troubleshoot Exceptions Errors – System.TypeInitializationException

The problem can arise when the QuickBooks Desktop is unable to access the fiblueprint.xml file because the permissions for this file are limited. In a Hosted Terminal Services or Citrix environment, you may get that error.

The type initializer for ‘OLB_Center.WPF.Model.FIBluePrintParser’ threw an exception. —> System.UnauthorizedAccessException: Access to the path ‘C:\ProgramData\Intuit\QuickBooks 2014\components\olb\branding\filist\fiblueprint.xml’ is denied.


When user permission constraints prevent QuickBooks from accessing the fiblueprint.xml file, this error may show up. When using QuickBooks in a hosted, terminal service, or Citrix environment, this typically occurs.

Continue using these solutions to work at your bank feeds center:

Solution 1: Make sure you have appropriate user permissions to C:\ProgramData

  • Open the C:\ProgramData folder where your QuickBooks file is located. Keep in mind that XX refers to your QuickBooks version. Pro 2018 equals 18, and Enterprise 19.0 equals 19.
    • Pro, Premier, or Accountant: C:\ProgramData\Intuit\QuickBooks 20XX\components\olb\branding\filist\
    • Enterprise: C:\ProgramData\Intuit\QuickBooks Enterprise Solutions XX.0\components\olb\branding\filist\
  • You have to double-click the fiblueprint.xml file after finding it.
  • If the file opens,  then you have to shut it down and launch QuickBooks again. Try again to work on your bank feeds.
  • If you are unable to, you must grant everyone access to your profile. To do this you have to.
    • Anywhere in the folder, you have to right-click and then you have to select Properties.
    • Select Edit under the Security tab.
    • Choose Everyone from the list of Group or user names “there.
    • Select Full Control under the Permissions for Everyone column.
    • Then you have to close the Edit and Properties windows.
    • Start up QuickBooks after your computer has restarted. Try again to work on your bank feeds.

Solution 2: Fix Microsoft .NET Framework, MSXML, and C++

  • This message may also appear if your computer has damaged Microsoft components.
  • Use the QuickBooks Install Diagnostic Tool to automatically identify and resolve problems with these components by downloading and running it.

Solution 3: Completely uninstall QuickBooks

Your QuickBooks Desktop program and its installation files are replaced by a clean install. This resolves a variety of problems, including bank feed errors. You can be sure that your company file and everything connected to it won’t be impacted.

The above-provided solutions enable you to get rid of the common system exception errors in QuickBooks Desktop. Still seeking any help, connect with the QuickBooks error support toll-free help desk number.

Frequently Asked Questions

What is the type of initializer exception?

The TypeInitializationException error typically denotes an extreme circumstance (the runtime is unable to instantiate a type) that renders an application unusable. The TypeInitializationException is most often thrown in reaction to a change in the application’s executing environment.

Where is the QuickBooks error log?

You have to press F2 on your keyboard. Then, on your keyboard, press F3. Scroll down to QBWIN. LOG on the Open File tab after selecting it.