Steema Central

Hi,

I have an issue running TChart from a network drive, and running from a PC that has Windows 2K.
I have updated my .Net Security Policy for the TeeChart.dll but I still seem to have problems.

I have managed to catch the exception that is occuring, see below:-

at Steema.TeeChart.FrAccessProvider.GetLicense(LicenseContext context, Type type, Object instance, Boolean allowExceptions)
at System.ComponentModel.LicenseManager.ValidateInternalRecursive(LicenseContext context, Type type, Object instance, Boolean allowExceptions, License& license, String& licenseKey)
at System.ComponentModel.LicenseManager.ValidateInternal(Type type, Object instance, Boolean allowExceptions, License& license)
at System.ComponentModel.LicenseManager.Validate(Type type, Object instance).

Any Help or advice would be appreciated.

Cheers
Eddie

Hello Eddie,

This may be related to the compilation of your project rather than the actual network security. ...the Win2K test was run locally, correct?

Please check that you're compiling your project with licenses.licx. There are some notes on use in Tutorial 17. Let us know if the steps there don't help.

Regards,
Marc Meumann

Hi Marc,

Thanks for you response, but that is not the issue. I have compiled the project with the Licenses.licx, as I can get it to run on an XP machine from a network server.

I actually found that the problem is related to the running of my application from a shortcut. If I run from a short cut then I have the problem, but if I run straight from my executable then I can run successfully.

Cheers
Eddie

Hello Eddie,

Please check that your shortcut runs in the folder where you wish to launch the application if there are any dependant elements in that folder.

Tests here confirm correct running of a NET executable between machines provided that rights are granted to the executable being run (that in turn uses TeeChart) via .NET Framework Configuration policy settings in the machine from where you're running the exe. Policy in the tests was set adding elevated rights (Full Trust or Everything) to the Hash of the exe itself. Further tests might confirm exactly what rights level is required.

We didn't encounter any difference in the behaviour between the exe directly and its shortcut.

Regards,
Marc