Page 1 of 1

License not valid (code: 1). Please view "Licensing" topic in dotConnect for MySQL documentation for details or contact

Posted: Tue 12 Jan 2016 15:31
by kim10987
Hi devart dotConnect Team,

We have embeded license file into our projects. It was working fine more than 5 months, and today it suddenly start throwing the following exception:

License not valid (code: 1). Please view "Licensing" topic in dotConnect for MySQL documentation for details or contact Devart technical support..

Could you tell me what other defects/things can cause this issue?

version info: 8.4.478

Thanks in advance!

Re: License not valid (code: 1). Please view "Licensing" topic in dotConnect for MySQL documentation for details or contact

Posted: Tue 12 Jan 2016 19:05
by kim10987
The problem has been resolved by resetting the server. Still would like to know the root cause of this...

Re: License not valid (code: 1). Please view "Licensing" topic in dotConnect for MySQL documentation for details or contact

Posted: Wed 13 Jan 2016 17:00
by Pinturiccio
This error means that an invalid license resource was built into your project. Unfortunately this information is not enough to determine the reason of this error. There can be several possible reasons for the "License not valid..." error. For more information, please refer to https://www.devart.com/dotconnect/mysql ... oubleshoot

Re: License not valid (code: 1). Please view "Licensing" topic in dotConnect for MySQL documentation for details or contact

Posted: Wed 13 Jan 2016 21:13
by kim10987
I am suspecting "4. Something's wrong with the operating system".
Do you guys have more information(reported cases) on that?

Re: License not valid (code: 1). Please view "Licensing" topic in dotConnect for MySQL documentation for details or contact

Posted: Thu 14 Jan 2016 14:59
by Pinturiccio
Lots of reasons can cause it. Maybe the operating system didn't allow reading information from the GAC or registry, or maybe Devart assemblies were unloaded from the domain by the operating system. Maybe there was a failure in a tool, embedding the license resource. There can be lots of reasons, and it is very hard to find out the true one without detailed analysis of the specific environment, on which the issue is reproduced reliably.