License Exception Occurred in Chartfx.dll Error on .NET Environment

Asked By chyna 0 points N/A Posted on - 10/09/2011

Dear .Net users,

I am facing a savvier problem with the following message. I am pretty new to the .Net environment, and have little experience in error handling. I tried to find a solution in MSDN, but it messed up my mind.

Please discuss the matter in a simple way.

Microsoft Development Environment

An unhandled exception of type 'System.ComponentModel.LicenseException' occurred in chartfx.dll

Additional information: Couldn't get Run Time license for 'SoftwareFX.ChartFX.Chart

Break Continue Ignore Help

Regards,

Chayna

• Status: Open
• Question Views: 2421
• Answer Count: 2
• Vote Up 0 Vote Down

• Answer Accepted: Yes
• Question Category: Misc Databases

Best Answer by metex

Go To Solution

Best Answer

Best Answer

Answered By metex 5 points N/A #90329

License Exception Occurred in Chartfx.dll Error on .NET Environment

You can also try to uninstall the whole product: Chart and the extensions and try to reinstall it again. Chart Installers must be run with an administrator account, since it modifies some registry entries.

So, please try to uninstall it and install it again. Then please try to open map sample application (the ones that are in the sample folder on the installation directory) or create an empty application and drop a chart and add the extension.

Hope this will help. If it doesn't, then contact at [email protected], with your product serial numbers as well.

Thank you.

About metex

Questions
2

Answers
37

Best Answers
27

• Vote Up 0 Vote Down

• Posted on - 10/14/2011
• Question Category: Misc Databases

Answered By Clair Charles 15 points N/A #90330

License Exception Occurred in Chartfx.dll Error on .NET Environment

The workaround is to that problem will be to make an entry in the config file of that application. 

When working with the .NET environment, you will find that some applications will need to use the MD5 hashing algorithm for compatibility with an older communication protocol, or maybe a file format that may be a little bit older. 

Before the .NET 3.5 was introduced, the AES algorithm was only available when it had to be used for the implementation which was not FIPS certified, and in that case if you needed to use that algorithm then the FIPS check could also block you, but the situation has been changed.

-Clair Charles

About Clair Charles

Questions
1

Answers
495

Best Answers
109

• Vote Up 0 Vote Down

• Posted on - 12/20/2011
• Question Category: Misc Databases