cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Intuit

Resolve Bank Feeds System Exception errors

This article provides troubleshooting steps for common System Exception errors, System.Argument.Exception and System.TypeInitializationException, that you may get while working on QuickBooks Desktop Bank Feeds.

System.Argument.Exception

While working in or accessing the Bank Feeds Center, one or more of the following errors are displayed:

System.Argument.ExceptionSmiley Tonguearameter 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.

The error can occur when:

  • A payee, vendor or rule is damaged.
  • The vendor name contains special characters such as "&".
  • QuickBooks detects an issue with an installed Microsoft component such as .Net framework.

Intuit recommends more than one solution for this problem. The first solution may solve your problem, or you may need to try all of them to resolve the issue. For best results, perform the solutions in the order shown.

Solution 1: Check vendor names for special characters

  1. From the Vendors menu, select Vendor Center.
  2. Click the default Active Vendor drop-down and select All Vendors.
  3. Review the vendor names for special characters, specifically the ampersand (&).
  4. Remove or if needed, rename "&" to "and".
  5. Save your changes.

Solution 2: Switch to the Classic (Register) mode

  1. From the QuickBooks Edit menu, click Preferences.
  2. On the left pane, choose Checking then go to the Company Preferences tab.
  3. In the Bank Feeds section, click Classic Mode (Register Mode).
  4. Click OK.

If you're able to add/match in classic mode without receiving an error, the problem is not with the bank but could be with a specific downloaded transaction or a damaged Rule, Vendor/Payee or Microsoft component. Proceed to Solution 3.

Solution 3: Restart computer and try to access Bank Statement again

  1. Close QuickBooks Desktop.
  2. Restart computer.
  3. Open QuickBooks Desktop.
  4. Access Bank Feeds Center and try to open and download your bank statement.

Solution 4: Review the QBWin.log for error messages

When reviewing QBWin.log, scroll to the bottom to view the most recent entries. If errors are identified, resolve data damage on your company file

Solution 5: Fix Microsoft .NET Framework, MSXML, and C++ issues using the QuickBooks Install Diagnostic Tool

Solution 6: Refer to troubleshoot Bank Feeds issues and errors, including OL and OLSU errors for additional solutions.

Solution 7: Reinstall QuickBooks for Windows using clean install

System.TypeInitializationException

When attempting to connect to Bank Feeds, you receive the error:

“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

The issue may occur when QuickBooks Desktop is unable to access the fiblueprint.xml file due to restricted user permissions. You are more likely to get the error message in a Hosted, Terminal Services or Citrix environment.

Intuit recommends more than one solution for this problem. The first solution may solve your problem, or you may need to try all of them to resolve the issue. For best results, perform the solutions in the order shown.

Solution 1: Grant the appropriate User permissions to the C:\ProgramData folder (with subfolders and files).

  1. Log-in as the User needing access.
  2. Manually go to the file location.
    (Note: Replace the 'X' with the year of QuickBooks Desktop you are using).
    • QuickBooks Pro/Premier/Accountant:  C:\ProgramData\Intuit\QuickBooks 201X\components\olb\branding\filist\
    • QuickBooks Enterprise:  C:\ProgramData\Intuit\QuickBooks Enterprise Solutions 1X.0\components\olb\branding\filist\
  3. Open fiblueprint.xml to verify if permissions are correct.
    • If you’re able to manually open fiblueprint.xml by double-clicking, close the file and restart QuickBooks Desktop.
    • If you’re unable to open file manually, provide the User full access to C:\ProgramData folder for the User account.
      1. Right-click the white space inside the "filist" folder.
      2. Choose Properties > Security tab > Edit.
      3. In Group or user names, select Everyone.
      4. In the Allow column, put a check mark in the Full control box.
      5. Click OK in the Edit window, then OK in the Properties window.
      6. Restart QuickBooks and Windows.
        Note: If you are unable to set permissions to this folder, you will need to work with an IT professional or with their hosting provider to update these permissions.

Solution 2: Fix Microsoft .NET Framework, MSXML, and C++ issues using the QuickBooks Install Diagnostic Tool

Solution 3: Reinstall QuickBooks for Windows using clean install