System.TypeInitializationException - WHEN WILL THIS BE FIXED

DPeronteau · ‎February 07, 2022

Dear QuickBooks,

WHEN WILL THIS ERROR BE ADDRESSED AND FINALLY FIXED BY INTUIT.

For years now, I/we have dealt with this nagging continuing issue with no resolution or barely a recognition from Intuit that the problem exists. Whenever I have called about it, I get no result and no callback from a higher level team member at Intuit.

Now, with Version 2022 Premier Accountant's Version on a Server 2016 Machine, I am having to fix the security settings for FLBlueprint.xml file and add back all my employees every other day or so.

This annoyance has gone on too long. Does anybody here have a fix for this ongoing error and clear issue.

thank you,

Dale

Dale Peronteau

American Eagle Consulting, Inc.

Jovychris_A · ‎February 07, 2022

I'd also get disappointed when I encounter an error message and only get fixed for a short time, @DPeronteau.

I've seen that you're also replied on this thread to share your sentiments and find solutions further in the Community: https://quickbooks.intuit.com/learn-support/en-us/banking/re-system-typeinitializationexception-erro.... And I'm here to hear it and share with you ways to help ease this permanently.

In your case, since you have done all these fixes and workarounds for years and the error still comes back, I'd suggest submitting a bug report. This will help alert our product engineers and fix this promptly without undergoing many troubleshooting steps:

Go to the Help menu.
Select Send Feedback Online and then choose Bug report.
Provide the details, especially your email, so you'll receive updates.
Hit Send Feedback.

That way, they'll take action on this and be able to share critical fixes specific to System.TypeInitializationException error that may require you to update QuickBooks Desktop in the latest release soon.

Additionally, here's an article you can read for more solutions about fixing System Exception errors. You'll want to bookmark this article for future use.

Feel free to tag me in your comment if you have other QuickBooks-related concerns. I'm always here to help. Keep safe and more power to your business, Dale!

bgarrett012 · ‎November 15, 2022

We are also experiencing the same issue with fiblueprint.xml file permissions being modified by the quickbooks program, even when we set "Authenticated Users" to Modify only in a multi user Azure Virtual Desktop. Quite annoying! We are currently testing the following as a resolution:

- Remove inheritance for the file and remove all permissions.

- Set file owner as your administrator account

- Set Authenticated Users to Modify

- Set Local Administrators (or domain administrators if you choose) to Full Control

- Make sure all other permissions including SYSTEM are removed and only Authenticated Users and Administrators are in the permissions.

We are not experiencing this issue for any other files. This shows up when users work in the bank feed. Additionally, here are the permissions we set on a multi-user environment:

$user = New-Object -TypeName 'System.Security.Principal.SecurityIdentifier' -ArgumentList @([System.Security.Principal.WellKnownSidType]::AuthenticatedUserSid, $null)

$MyPath1 = "C:\ProgramData\Intuit"

$acl1 = Get-Acl -Path $MyPath1

$rule1 = New-Object System.Security.AccessControl.FileSystemAccessRule($user, 'Modify', 'ContainerInherit,ObjectInherit', 'None', 'Allow')

$acl1.SetAccessRule($rule1)

Set-Acl -Path $MyPath1 -AclObject $acl1

$MyPath2 = "C:\ProgramData\Common Files\Intuit"

$acl2 = Get-Acl -Path $MyPath2

$rule2 = New-Object System.Security.AccessControl.FileSystemAccessRule($user, 'Modify', 'ContainerInherit,ObjectInherit', 'None', 'Allow')

$acl2.SetAccessRule($rule2)

Set-Acl -Path $MyPath2 -AclObject $acl2

$MyPath3 = "C:\Program Files\Intuit"

$acl3 = Get-Acl -Path $MyPath3

$rule3 = New-Object System.Security.AccessControl.FileSystemAccessRule($user, 'Modify', 'ContainerInherit,ObjectInherit', 'None', 'Allow')

$acl3.SetAccessRule($rule3)

Set-Acl -Path $MyPath3 -AclObject $acl3

$MyPath4 = "C:\Program Files\Common Files\Intuit"

$acl4 = Get-Acl -Path $MyPath4

$rule4 = New-Object System.Security.AccessControl.FileSystemAccessRule($user, 'Modify', 'ContainerInherit,ObjectInherit', 'None', 'Allow')

$acl4.SetAccessRule($rule4)

Set-Acl -Path $MyPath4 -AclObject $acl4

$MyPath5 = "C:\Program Files (x86)\Intuit"

$acl5 = Get-Acl -Path $MyPath5

$rule5 = New-Object System.Security.AccessControl.FileSystemAccessRule($user, 'Modify', 'ContainerInherit,ObjectInherit', 'None', 'Allow')

$acl5.SetAccessRule($rule5)

Set-Acl -Path $MyPath5 -AclObject $acl5

$MyPath6 = "C:\Program Files (x86)\Common Files\Intuit"

$acl6 = Get-Acl -Path $MyPath6

$rule6 = New-Object System.Security.AccessControl.FileSystemAccessRule($user, 'Modify', 'ContainerInherit,ObjectInherit', 'None', 'Allow')

$acl6.SetAccessRule($rule6)

Set-Acl -Path $MyPath6 -AclObject $acl6

Write-Output "C:\ProgramData\Intuit"

(Get-ACL -Path $MyPath1).Access | Format-Table IdentityReference,FileSystemRights,AccessControlType,IsInherited,InheritanceFlags -AutoSize

Write-Output "C:\ProgramData\Common Files\Intuit"

(Get-ACL -Path $MyPath2).Access | Format-Table IdentityReference,FileSystemRights,AccessControlType,IsInherited,InheritanceFlags -AutoSize

Write-Output "C:\Program Files\Intuit"

(Get-ACL -Path $MyPath3).Access | Format-Table IdentityReference,FileSystemRights,AccessControlType,IsInherited,InheritanceFlags -AutoSize

Write-Output "C:\Program Files\Common Files\Intuit"

(Get-ACL -Path $MyPath4).Access | Format-Table IdentityReference,FileSystemRights,AccessControlType,IsInherited,InheritanceFlags -AutoSize

Write-Output "C:\Program Files (x86)\Intuit"

(Get-ACL -Path $MyPath5).Access | Format-Table IdentityReference,FileSystemRights,AccessControlType,IsInherited,InheritanceFlags -AutoSize

Write-Output "C:\Program Files (x86)\Common Files\Intuit"

(Get-ACL -Path $MyPath6).Access | Format-Table IdentityReference,FileSystemRights,AccessControlType,IsInherited,InheritanceFlags -AutoSize

bgarrett012 · ‎November 15, 2022

We have also run into this same issue with fiblueprint.xml permissions being modified by the program/system somehow and breaking bank feeds for others in a multi-user environment. We are currently testing the following to fix this:

- Remove inheritance of permissions on fiblueprint.xml and remove all permissions

- Set ownership to your administrator account of choice

- Set Administrators to Full Control

- Set Authenticated Users to Modify

- Confirm only these two permissions exist in the permissions, and that you are the owner. Additionally we set Modify (NOT full control as recommended by Intuit) permissions to Authenticated users on the following folders in multi-user environment:

C:\ProgramData\Intuit
C:\ProgramData\Common Files\Intuit
C:\Program Files\Intuit
C:\Program Files\Common Files\Intuit (if exists)
C:\Program Files (x86)\Intuit
C:\Program Files (x86)\Common Files\Intuit

bgarrett012 · ‎November 17, 2022

Even after changing ownership on fiblueprint.xml and removing all full control permissions the program is still allowing an ownership change somehow. I've removed all permissions from filist folder (one level higher) to see if this helps force permissions to stick. This seems to be by design in reading other forms, Intuit is intending to lock the bankfeed files to one user at a time, but this is causing major issues in multi-user environments.

RCV · ‎November 17, 2022

I can see you’ve done your due diligence trying to get this resolved already, bgarrett012.

I appreciate you for performing some solutions to get this sorted out. This occurs when QuickBooks can’t access the fiblueprint.xml file due to user permission restrictions. It'll usually happen when you use QuickBooks in a hosted, terminal service, or Citrix environment. To fix this, let's start by ensuring you have the appropriate user permissions to C:\ProgramData. Here's how:

Find and open your QuickBooks folder in C:\ProgramData.
Find and double-click on the fiblueprint.xml file.
If the file opens, close it and restart QuickBooks.

Once done, try working on your bank feeds again. If you can’t, you need to grant full access to your profile.

Right-click anywhere in the folder.
Tap Properties.
Go to the Security tab.
Choose Edit.
In the “Group or user names” section, select Everyone.
In the “Permissions for Everyone” section, select Full control.
Close the Edit and Properties windows.
Restart your computer, then open QuickBooks. Retry working on your bank feeds.

If unable to set the permissions, I recommend working with your hosting provider or an IT professional to update it. If the same thing happens after following the steps above, continue with Solution 2: Fix Microsoft .NET Framework, MSXML, and C++ in this article: Fix System Exception errors.

If the issue persists, please contact our Technical Support Team. They'll pull up your account in a secure environment and investigate what's causing this issue. Here's how to reach them:

Go to Help, then select QuickBooks Desktop Help/Contact Us.
Hit Contact Us.
Give a brief description of your issue, then select Continue.
Sign in to your Intuit account and select Continue and then Continue with my account. If you don't already have an account, make sure to Create a new account.
We'll email you a single-use code. Enter your code and select Continue. If you have more than one account, select the account you want to use and then Continue.
Tap to chat with us or Have us call you.

For future reference when managing Bank Feed transactions, check out this article: Add and match Bank Feed transactions in QuickBooks Desktop.

Let me know how things go on your end and if you need other help in QuickBooks. Just leave a comment below and I'll get back to you. Take care always.

Topics

Training

Community

Resources

System.TypeInitializationException - WHEN WILL THIS BE FIXED