Resolve Bank Feeds System Exception Errors

Resolve Bank Feeds System Exception errors
This short article provides troubleshooting steps for common System Exception Errors In QuickBooks, System.Argument.Exception and System.TypeInitializationException, that you may get while taking care of QuickBooks Desktop Bank Feeds.


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

System.Argument.Exception:Parameter is certainly 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)
Related post:

System.ArgumentOutOfRange.Exception: Index was out of range.
The error can happen when:

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

Intuit recommends more than one solution with this problem. The very first solution may solve your trouble, or perhaps you could need to try them all to solve the issue. For best results, perform the solutions within the order shown.

Solution 1: Check vendor names for special characters

Through the Vendors menu, select Vendor Center.
Click on the default Active Vendor drop-down and choose All Vendors.
Review the seller names for special characters, specifically the ampersand (&).
Remove or if perhaps needed, rename "&" to "and".
Keep your changes.

Solution 2: Switch to the Classic (Register) mode

Through the QuickBooks Edit menu, click Preferences.
On the left pane, choose Checking then go to the Company Preferences tab.
When you look at the Bank Feeds section, click Classic Mode (Register Mode).
Click OK.
When you can add/match in classic mode without receiving a mistake, the issue is not using the bank but might be with a specific downloaded transaction or a damaged Rule, Vendor/Payee or Microsoft component. Go to Solution 3.

Solution 3: Restart computer and you will need to access Bank Statement again

Close QuickBooks Desktop.
Restart computer.
Open QuickBooks Desktop.
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 look at the newest entries. If errors are identified, resolve data damage in your company file

Solution 5: Fix Microsoft .NET Framework, MSXML, and C++ issues utilizing 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

When trying to hook up to Bank Feeds, you obtain the error:

“System.TypeInitializationException: The type initializer for ‘OLB_Center.WPF.Model.FIBluePrintParser’ threw an exception. ---> System.UnauthorizedAccessException: usage of the path ‘C:\ProgramData\Intuit\QuickBooks 2014\components\olb\branding\filist\fiblueprint.xml’ is denied.”

The problem may possibly occur when QuickBooks Desktop is unable to access the fiblueprint.xml file as a result of restricted user permissions. You will be prone to obtain the error message in a Hosted, Terminal Services or Citrix environment.

Intuit recommends significantly more than one solution because of this problem. The initial solution may solve your problem, or you may prefer to try all of them to resolve the matter. For best results, perform the solutions in the order shown.

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

Log-in since the User needing access.
Manually go to the file location.
(Note: Replace the 'X' using the year of QuickBooks Desktop you may be 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\
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, supply the User full access to C:\ProgramData folder for the User account.
Right-click the white space in the "filist" folder.
Choose Properties > Security tab > Edit.
In Group or user names, select Everyone.
Within the Allow column, put a check mark into the Full control box.
Click OK into the Edit window, then OK in the Properties window.
Restart QuickBooks and Windows.
Note: If you are unable to set permissions for this folder, you will have to make use of an IT professional or along with their hosting provider to update these permissions.

Related article:
Solution 2: Fix Microsoft .NET Framework, MSXML, and C++ issues making use of the QuickBooks Install Diagnostic Tool

Solution 3: Reinstall QuickBooks for Windows using clean install


Private comment