Hi Sam,First up, we are currently deploying v3.4.0 of TA. Is there anything you can think of that would be different here? It would be a big pain to make a maintenance release for just this issue now so we will avoid it if we can. I've not seen this error before, with about 1000 active users. As a follow-up here - is it possible to send the user the new version of TA and have him run that independently? That might be worth a try, if so.
As far as I can tell from the screen shot the customer has sent, he has entered the key absolutely correctly. I assume via cut & paste. Could the Russian locale affect things here?
He is definitely using a real key, that he has recently purchased.
How would tampering affect things here? I did have some issues with users circumventing the trial (especially in Russia, actually), and took measures to prevent that behaviour by limiting the features in trial mode. This *could* be a user that has decided to "go legit" (I don't want to cast aspersions - I don't know if this is the case in this situation) . Could prior tampering affect this transition? If so, how to resolve? Of course, I want to welcome all such prior-miscreants into the fold 🙂
thanks,Matt