Resolve Bank Feeds System Exception Errors

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

System.Argument.Exception
While employed in or accessing the Bank Feeds Center, a number of of the following errors are displayed:

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.
The error may appear when:

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

Intuit recommends significantly more than one solution with this problem. The initial solution may solve your problem, or you might need to try them all to eliminate the problem. For best results, perform the solutions into the order shown.

Solution 1: Check vendor names for special characters

Through the Vendors menu, select Vendor Center.
Click 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.

Relate darticle: http://accountingpride.bravesites.com/entries/general/resolve-bank-feeds-system-exception-errors
Solution 2: change to the Classic (Register) mode

From the QuickBooks Edit menu, click Preferences.
On the left pane, choose Checking then go directly to the Company Preferences tab.
Into the Bank Feeds section, click Classic Mode (Register Mode).
Click OK.
If you possibly could add/match in classic mode without receiving a mistake, the issue is not aided by the bank but could be with a certain downloaded transaction or a damaged Rule, Vendor/Payee or Microsoft component. Check out Solution 3.

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

Close QuickBooks Desktop.
Restart computer.
Open QuickBooks Desktop.
Access Bank Feeds Center and attempt 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 up-to-date entries. If errors are identified, resolve data damage on your own company file

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

Visit: https://www.proaccountingxpert.com/system-exception-errors-in-quickbooks-bank-feeds/

System.TypeInitializationException
When attempting to connect with Bank Feeds, you will get 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 occur when QuickBooks Desktop is unable to access the fiblueprint.xml file as a result of restricted user permissions. You are almost certainly going to have the error message in a Hosted, Terminal Services or Citrix environment.

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

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

Log-in since the User needing access.
Manually go directly to the file location.
(Note: Replace the 'X' utilizing 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, provide the User full access to C:\ProgramData folder for the User account.
Right-click the white space within the "filist" folder.
Choose Properties > Security tab > Edit.
In Group or user names, select Everyone.
Within the Allow column, put a check mark within the Full control box.
Click OK when you look at the Edit window, then OK into the Properties window.
Restart QuickBooks and Windows.
Note: If you are struggling to set permissions to this folder, you need to make use of an IT professional or along 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

Related post: https://accountingspro.usite.pro/blog/resolve_bank_feeds_system_exception_errors/2020-10-20-96