Skip to content
logo Knowledgebase

Company Opening: ‘Error during system tree load! [TBriliantPackageManager.E01] The type initializer for ‘System.Data.Common.DbConnectionOptions’ threw an exception’ error opening Evolution Company

Created on  | Last modified on  Highlight Matches

Summary

Learn how to fix the ‘Error during system tree load! [TBriliantPackageManager.E01] The type initializer for ‘System.Data.Common.DbConnectionOptions’ threw an exception' error opening a Sage 200 Evolution Company.

Description

This article discusses how to resolve the following error when opening an Evolution company: 

Image

 

 

Resolution

Consider the following advice to resolve the above error:  

 

A. Recent Windows Updates - Incomplete

In some cases, a Windows update may not have completely downloaded when it was installed on one or more PCs.

Therefore,  with the assistance of your local IT technician, force the same Windows Update to be re-downloaded and re-installed on the same PC where the above error is observed.

If you still observe the same error afterwards, apply the advice in the rest of the article below. 

 

B. Recent Windows Updates - General impact on Windows applications 

Sage 200 Evolution, as with other Windows based applications, can be negatively affected by certain Windows updates that are excused on the local PC where Evolution is installed on.

This is due to the Windows update regarding certain Evolution system files as a threat. In this case, these files may be either deleted or deregistered, especially for *.DLL files.

Therefore, consider the following 2 phases to apply when the above error is observed after a recent Windows update on the local PC:

 

Phase 1: Uninstallation  

Open this link for a detailed article that discusses how to uninstall Evolution.

Do this on the affected workstations (with Evolution locally installed) or the main RDP/hosted Evolution server (as relevant).

 

Phase 2: Installation  

Open this link for a detailed article that discusses how to install Evolution.

Do this on the affected workstations (with Evolution locally installed) or the main RDP/hosted Evolution server (as relevant). 

 

If you still observe the same error afterwards, apply the advice in the rest of the article below. 

 

C. Windows vs Sage 200 Evolution version incompatibility

Older versions/builds of Evolution may be incompatible with your current version/build of MS Windows.

For instance, you are running Evolution version 7.10 on Windows version 11.

Therefore, upgrade your Evolution package and all Evolution companies, by uninstalling and reinstalling the latest Evolution version.

Refer to and apply the Uninstallation and Installation phases as discussed above. 

 

If you still observe the same error afterwards, apply the advice in the rest of the article below. 

 

D. Closely Similar Error

Open this link for an article that explains how to resolve a similar error:

'The type initializer for ‘System.Data.Entity.Internal.AppConfig’ threw an exception’

 

If you still observe the same error afterwards, apply the advice in the rest of the article below. 

 

E. Formatting the PC 

As a last resort, the only other option is to format the local PC where the above error is observed. 

This proved to be the only solution on an actual support ticket raised with Evolutions Support.