"...your trial period has expired" on a non-trial deployment

"...your trial period has expired" on a non-trial deployment

Postby sumit » Tue 05 May 2009 21:21

Hi,

We are using MySQL .net 3.55.17 version of the drivers (Corelab.MySQL.dll) with our C# (windows and ASP.Net) application. We include licenses.licx file with your project that licenses the corelab binaries. The ASP.Net deployment has App_Licenses.dll file in the bin folder with appropriate mysql corelab reference.

On one of the test machines at our facility, we started to see the following exception when one of our QA analysts tried to do something against our ASP.Net application.

Code: Select all
Error Message: Sorry, your trial period has expired.
To order registered version please visit Core Lab site at
http://www.crlab.com/mysqlnet/ordering.html
Error Source: CoreLab.MySql
Error Target Site: Void Open()


The machine was left idle over the weekend and this happened on Monday morning. We tried to identify the source of the problem and could not find anything that would lead to presence of a trial version of Corelab libraries. We have other machines that are running without any issues.

At last, we rebooted the machine and the error went away. It seems like something got messed up within Corelab binaries that caused it to think that it was a trial version. Obviously, it will be embarrassing for us if one of our customers runs into this situation. We want to understand what could have caused this problem and what are the chances that this will come back again?

Thanks.
sumit
 
Posts: 62
Joined: Wed 03 Jan 2007 22:23

Postby Shalex » Wed 06 May 2009 12:27

This error can arise if the assembly with CoreLab trial license is loaded to the process of your application. Please make sure all assemblies have non-trial license embedded resource.

Otherwise, if you generate App_Licenses.dll with non-trial version of MyDirect .NET, and the error appears again, look carefully at the assemblies that are loaded to the process of your application. If you find another assembly with the CoreLab license embedded resource, probably it will have trial license embedded resource, and it will be the reason of the problem.
Shalex
Devart Team
 
Posts: 7475
Joined: Thu 14 Aug 2008 12:44

Postby sumit » Wed 06 May 2009 17:38

Thanks for the reply.

How do I tell which assemblies are loaded by the process and which Corelab assembly has a trial license embedded in it vs non-trial? Now that we don't see that message, is there a way to find an assembly on the machine that has trial license embedded in it?
sumit
 
Posts: 62
Joined: Wed 03 Jan 2007 22:23

Postby Shalex » Thu 07 May 2009 11:19

We don't know the way to find an assembly on the machine with a trial license embedded in it. We think it is possible to look inside every assembly that is loaded to the process of the application that has the mentioned problem at the moment, and check by some tool the license resource of all assemblies. If you find the CoreLab name in the license resource of some assembly except App_Licenses.dll, probably this will be the reason of the problem. There is no way to identify the problem for sure.
Shalex
Devart Team
 
Posts: 7475
Joined: Thu 14 Aug 2008 12:44

Postby sumit » Fri 08 May 2009 16:11

Thanks. We will see if the problem happens again and if it does, try to identify the assembly with trial license.
sumit
 
Posts: 62
Joined: Wed 03 Jan 2007 22:23


Return to dotConnect for MySQL