Activation FailedSolved

License key '_________________________________' activation failed.

No more deactivations are allowed for the product key. This product is still activated on this computer.

This license works on other machines fine. We have tried the firewall and antivirus shutdown.

If this is the error "No more deactivations are allowed for the product key. This product is still activated on this computer."

... then it's telling you exactly what the problem is. You've limited the number of deactivations allowed for a product key. And the customer has exceeded that number: https://wyday.com/limelm/help/activations/#deactivate

Hi,

So the problem is that we get this error message even when we have created a new license key. I thought it was that we had run out of deactivation as well, however we have set the deactivation limit to unlimited and set number of machines to 5.

The really strange part is if I use the license on my computer, it activates our software. However if I try to activate the license on a laptop computer, it fails to activate and instead throws the "No more deactivations" Exception (TA_E_NO_MORE_DEACTIVATIONS).

Steps we have tried:- Turning off all firewalls on antivirus- Connecting via different networks, both private and public- Ensuring its not an internet error - Trying new license keys that we make on the spot

I also Wiresharked the network traffic on both PCs, and both seem to be in contact the WyDay server however we just keep receiving the Deactivation error, even when the license has not even been activated.

Any insight into this issue would be much appreciated.

Thanks

Hi

UPDATE: We have figured out the issue regarding this.

Since licenses on the same computer will overwrite each other, we had implemented a function on activation to first check to see if the software was already activated, and if it was to deactivate it.

However the license it was trying to deactivate was an old license that had "expired", which had a deactivation limit of 1, and that was the license it was trying to deactivate.

Which is why trying to activate a new one it would throw a NoMoreDeactivations error.

Thank you for your help regarding this