Date/system is invalid. Please reboot your system...

Hey Laurent,

Is he using offline activation? If so, then he must generate new Activation request and use the new activation response file.

Also, he should make sure the timezone for his computer is correct (along with the date and time).

Hello,

No, he doesn't use offline activation.

I will ask him to check the timezone.

Thanks for you help,

Laurent

Hi,

I checked the time zone vs date/time. All is ok.Here is the message from our customer :"Thank you for the mail, but time/date and timezone are not different. I use mac OS X (10.6.8) and the program was running without problems. Suddenly - i worked with it in the morning it does not start a few hours later, and I get always the same messages? I try to restart, to reboot, new-installation nothing is working. Sorry, but I need this excellent softwarewhat else can I do?"

He also tried to set the time to time+1h, without success.

Thanks for your help,Laurent

What did he change on his computer? Any apps added/settings changed/etc. between the time your app was working fine and your app was not working fine?

If he can't find the cause then we'll need to remotely debug this for him. What timezone does he live in?

Also, what version of TurboActivate do you have included with your app? You can get the version number like so:

otool -L libTurboActivate.dylib

Hi,

thanks for your fast response.The customer didn't change anything from the time when the app is working to the NOK time. I don't know if he has installed another app in this interval.I checked personally via TeamViewer the datetime/settings and Timezone. The only thing I found is that, on his Mac (SnowLeopard), the automatic update of the time was not checked.I have enabled this settings + reboot, without success.

The version we're using is = "current version 2.13.0" We didn't have any problem with this version until this day. We have several customers who don't have this kind of problem.

He's living in Germany. He has Teamviewer on his Mac also.

Please recompile your app with the latest version of TurboActivate. We fixed a bug similar to the one the customer was having sometime in the 3.x branch.

Ok, Thanks, we'll make it.

Hi,

We didn't rebuild the app : we just replace the libTurboActivate.dylib on the customer's computer.Before, we made the test on our computer. It works with the new lib (3.2.2).On the customer's computer, he didn't have the message with "date/system invalid" but he has "the key is invalid".We tried with another new key => same message "the key is invalid".

What can we do now ?

thanks,L

We didn't rebuild the app : we just replace the libTurboActivate.dylib on the customer's computer

You absolutely must rebuild your app when you're switching from TurboActivate 2.x to 3.x. Also use the latest TurboActivate header (if you're using C++, or other bindings if you're using another language).

If you just replace the file you get errors.

We don't need to rebuild the app because we're using Unity3D tech in C# with Mono VM and we always put the lib when the build is finished in the right directory.We can build a new version without the dynlib found by the Mono compiler/builder.

So, our project contains TurboActivate.cs, that loads the dynlib if the Os is MacOs dynamically, that's it and it works well from the beginning.

Did you change some calls in TurboActivate.cs ?Shall we change the .dat with the 3.2.2 version ?

If you suspect some bug in the 2.x version we're using, and fixed in the 3.x version, maybe we can fix something on the customer's computer that can solve the problem because you know the source of the problem...

Thks,

We don't need to rebuild the app because we're using Unity3D tech in C# with Mono VM and

Yes, you do.

Did you change some calls in TurboActivate.cs ?

Yes.

If you suspect some bug in the 2.x version we're using, and fixed in the 3.x version, maybe we can fix something on the customer's computer that can solve the problem because you know the source of the problem...

There are bugs in Mac OS X that we workaround. You'd have to fix Mac (at the kernel level).

Hi,

Upgrading to 3.2.2 when it's not scheduled is a lot of work to upgrade for a problem that occurs only for one customer..I upgrade the TurboActivate.cs.I added the function SetCustomTurboActivateFile() for MacOs we call in other module.

/// <summary> /// Set a custom path to look for TurboActivate.dat file /// </summary> public static void SetCustomTurboActivateFile() { switch(Native.PDetsFromPath(Sport.TurboActivatePath+"TurboActivate.dat")) { case 0: // SUCCESSFUL return; default: throw new ProductDetailsException(); } }}

We have rebuilt the app and put the new dynlib in the right directory.But the app crashs during the start.In the Mac Console, I have this error message :Activation check failed: GUIDMismatchException: The product details file "TurboActivate.dat" is corrupt.

Of course, it's always the same .dat we used for a long time...

Any idea ?

Send me your old versions of the TurboActivate.cs file (the one you modified) to support@wyday.com and I'll adjust it so it works in TurboActivate 3.x.

The File has been sent.

Thanks a lot.