Page 1 of 1
licensing problem
Posted: Tue Aug 09, 2005 3:55 am
by 8125091
we updated TeeChart to new version 1.1.1879.21176 and graphs don't work.
Code: Select all
[NullReferenceException: Object reference not set to an instance of an object.]
Steema.TeeChart.FrAccessProvider.GetLicense(LicenseContext context, Type type, Object instance, Boolean allowExceptions) +158
System.ComponentModel.LicenseManager.ValidateInternalRecursive(LicenseContext context, Type type, Object instance, Boolean allowExceptions, License& license, String& licenseKey) +326
System.ComponentModel.LicenseManager.ValidateInternal(Type type, Object instance, Boolean allowExceptions, License& license) +44
System.ComponentModel.LicenseManager.Validate(Type type, Object instance) +32
Steema.TeeChart.Chart..ctor() +89
When our application used previous version it was ok.
version.licx file is placed into bin directory and into root directory of application.
Should we execute TeeReg.exe on server where our site is hosted?
thank you
Posted: Thu Aug 11, 2005 6:50 am
by Pep
Hi,
there is a licensing aspect that has recently come to light that we weren't aware of in time for the documentation and that may help to know..
The issue relates to applications that compile TeeChart into a DLL that is then used in turn by a different application. Might that be the case for your use of TeeChart? If so please note the comments from a TeeChart Developer who recently ran through runtime licensing steps:
"...
It was not enough to provide
the .licx entry in building the DLL that instantiates and uses TeeChart -
no! In fact, even though the main project (the EXE module) did not
reference TeeChart, apparently it was necessary to add the TeeChart
licensing entry to this project's own .licx file
..."
Please check that the point might not apply in your case. If that's not relevant or of help and the test below doesn't help either, please let us know what type of application TeeChart is being built into along with any other information you might feel is of use and we'll look for other causes of the problem.
Another test (assuming your application doesn't fall into the dll type described above), would be to recompile the TeeChart demo (assuming you ran the precompiled exe?) on your development machine and then test that on the runtime machine. That would confirm that the designtime license is correctly in place on your development machine and able to correctly 'compile-in' the license.
Please let us know if the above doesn't help resolve the issue.
I am having the same problem on a web server
Posted: Tue Aug 16, 2005 12:05 am
by 8119887
I've checked the licences.licx in the web project, and T-Chart is there, versions seem correct etc. And obviously, it's not a problem like above - the chart is being used directly in the web project.
Any suggestions? This fault has been intermittent - it occurred last week, then cleared itself - was fine this morning, and now has started happening again.
Posted: Wed Aug 17, 2005 8:06 am
by Marc
Hello,
As an intermittent error it may be harder to track down. Licensing when setup tends to work correctly always and until it has been setup it tends to fail consistently. Is it failing intermittently on the same server?
Licenses.licx should exist in your project as an embedded resource. You can cross-check config by looking at one of the web projects shipped with TeeChart.
The development key needs to be present only on the machine where the application is compiled. It does not need to be installed on any runtime machine (hence no need for teereg.exe on the runtime server).
Please check that your development machine only has one version of TeeChart for .NET installed. If your project is picking up an incorrect version then it will not compile the licenses.licx content into the compiled application dll. Compiling with licx not present in the project should report an error if the correct version of TeeChart is being referenced. Check that the licx file has content as described in the tutorial.
Please let us know with any information that may help if you continue to experience the problem.
Regards,
Marc Meumann