License Validation - Failed because system date and time settings are incorrect

[Tyler Edmonds]

Hello Scott,

We've got a new dev starting and we are unable to get his IC licensed. 

We have a new key for him but we keep getting a date/time error when trying to activate the license. 

Error: An unexpected error occurred during license validation: Failed because your system date and time settings are incorrect. Fix your date and time settings, restart your computer, and try to activate again.

The error pops up every time you try to open IC licensing page in IntelliJ.  If you hit cancel, it seems to let you move onto the next stage.  We entered the license and clicked activate, but it throws another of the same error. Always says failed to activate. 

I checked the license key manager and it actually shows that it's associated with this devs laptop now and seems to be setup properly. IntelliJ and IC just seem to be miss reading his date/time.

- We have reset the time on his machine. Date/Time settings and toggle off/on "set time automatically". 

- set time zone manually

- set time zone automatically

- did the "sync now" with time.windows.com

- rebooted after each step

still getting same error. 

IntelliJ build: #IC-223.7571.182

Let me know your thoughts. 

Thanks!

Tyler Edmonds

[Scott]

Hi, Tyler. The licensing software used by IC2 can certainly be finicky, but it's generally about things like disabled network interfaces and such rather than the date/time. As I imagine you've surmised, it's checking the local date/time against the known date/time to guard against someone trying to trick it by setting the local system clock backward. Obviously I know that's not happening here for a variety of reasons. And it generally has some reasonable leeway in the allowed delta between local and server. The only times I've seen this happen in the past, it really mostly an issue with a machine that was being purposely locked into a specific date/time for testing purposes.

Before I loop in the licensing software vendor to help troubleshoot, let's try a few things that they're almost certainly going to suggest initially anyway:

1. Is this machine's OS completely patched to the latest level, and are the drivers similarly up-to-date? What is the OS version by the way?
2. Have you tried restarting the machine completely after configuring the time/time zone to be set automatically? Believe it or not, I actually saw a simple reboot resolve this once in the past. Literally the old "have you tried turning it off and back on again" thing...
3. Have you tried using an offline activation? I wouldn't expect that to behave any differently, just the same error during a different step, but it may be worth trying if the things above don't help.

If those don't whip it into shape, I'll likely need to check for a newer version of the licensing software and, if available, provide a test build with that integrated to see if this is something perhaps they've fixed recently. Otherwise that will (understandably) be their first question to me since they'll only want to troubleshoot this themselves against their latest-and-greatest.

Let's see how/whether that information helps first.

Regards,

Scott Wells