QuickBooks HelpQuickBooksHelpIntuit

Fix System Exception errors

SOLVED•by QuickBooks•4•Updated over 1 year ago

Find out how to fix “System.Argument.Exception” or “System.TypeInitializationException” when you work in your QuickBooks Desktop Bank Feeds Center.

System.Argument.Exception

  • System.Argument.Exception: 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: Index was out of range.

System.Argument.Exception errors are mostly caused by:

  • Special characters in a vendor name.
  • Damaged payee, vendor, or renaming rule.

To continue working on your bank transaction, follow these steps:

  1. Go to Vendors and select Vendor Center.
  2. From the Vendors ▼ drop-down menu, select All Vendors.
  3. Check if there are vendor names with special characters (!@#$%^&*).
  4. If there are, right-click the vendor and select Edit Vendor.
  5. Delete the special character from the vendor name, then select OK. You can use words in place of the special character such as “and” for “&”.
  1. Go to Edit and select Preferences.
  2. Select Checking, then go to the Company Preferences tab.
  3. In the Bank Feeds section, select Classic Mode (Register Mode).
  4. Select OK.
  5. Retry adding or matching your bank transactions.

If you still see the error, it might be caused by issues with your file, financial institution, or Microsoft components. Proceed to step 3 to continue fixing it.

Before continuing, make sure to refresh your system:
  1. Go to File and select Close Company.
  2. Close QuickBooks Desktop.
  3. Restart your computer.
  4. Open QuickBooks Desktop.
  5. Retry to add or match your bank transactions.

You can use your QBWin.log to see what might be causing the bank feeds error. To do this:

  1. Find and open your QBWin.log file.
  2. Scroll to the bottom of the window and check if you see any LVL_ERROR.
  3. If you do, go and search for it in our QuickBooks Learn & Support site to find out how to fix it.

You might also see System.Argument.Exception errors when your computer has damaged Microsoft components.

Download and run the QuickBooks Install Diagnostic Tool to automatically diagnose and fix issues with these components.

Still get an error while working in the Bank Feeds Center? Your financial institution or your bank account in QuickBooks might be the one that has issues.

Don’t worry. Just follow these common bank feeds troubleshooting steps to help determine if the problem lies with your bank or its connection with QuickBooks.

If you still get an error after checking in with your bank, “clean install” your QuickBooks. This replaces your QuickBooks Desktop software and its installation files which fixes different issues including bank feeds errors.

Rest assured that it won’t affect your company file and everything linked to it.

System.TypeInitializationException

System.TypeInitializationException:
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.

User-added image

This error might appear when QuickBooks can’t access the fiblueprint.xml file because of user permission restrictions. This usually happens when you use QuickBooks in a hosted, terminal service, or Citrix environment.

To continue working in your Bank Feeds Center, follow these solutions:

  1. Find and open your QuickBooks folder in C:\ProgramData. Note that XX stands for your QuickBooks version. Example: Pro 2018 = 18 or Enterprise 19.0 = 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\
  2. Find and double-click on the fiblueprint.xml file.
  3. If the file opens, close it and restart QuickBooks. Retry working on your bank feeds.
  4. If you can’t, you need to grant full access to your profile. To do this:
    1. Right-click anywhere in the folder and select Properties.
    2. Go to the Security tab, then select Edit.
    3. In the “Group or user names” section, select Everyone.
    4. In the “Permissions for Everyone” section, select Full control.
    5. Close the Edit and Properties windows.
    6. Restart your computer, then open QuickBooks. Retry working on your bank feeds.

Note: If you can’t set the permissions, you need to work with your hosting provider or an IT professional to update it.

You might also see this error when your computer has damaged Microsoft components.

Download and run the QuickBooks Install Diagnostic Tool to automatically diagnose and fix issues with these components.

Note: If you’re working on QuickBooks remotely, make sure to run the tool on the computer where you installed QuickBooks.

Clean install replaces your QuickBooks Desktop software and its installation files. This fixes different issues including bank feeds errors.

Rest assured that it won’t affect your company file and everything linked to it.

Was this helpful?

You must sign in to vote, reply, or post
QuickBooks Desktop AccountantQuickBooks Desktop PremierQuickBooks Desktop ProQuickBooks Enterprise Accountant

Sign in for the best experience

Ask questions, get answers, and join our large community of QuickBooks users.

More like this