manuelpehin your license settings you have set this to dissalow: Activations on virtual machines & hypervisors are not allowed. just set it to allow and problem solved
XP VM activation problem
radioHi,I have a program installed on a XP Virtual Machine (Oracle VM). The activation was working fine. I then installed service pack 3 to be able to use Chinese locales. In the meantime, the VM activation allowing was removed on the LimeLM server. I then put it back.Now I try to activate my program (by launching turboactivate directly) and I have the following happening.- If I use a new key, I get first the message that TurboActivate can't reach the activation servers. I Try again and then I get the following message : "You cannot activate Xeocoder inside a virtual machine or a hypervisor. Please use a real computer."- If I keep trying with this key I get all the time this messageIt doesn't make sense since the VM activation is allowed, and was working fine previously.So, is there an issue with a service pack, or any windows xp update, or is there any problem related to the changes I made on the lime lm server side ?
Precisions : I'm using last turboactive.exe and .dll versions, and I also downloaded turboactivate.dat after the changes I made on limelm server.
Regards
manuelpehradioNo, this settings had been put to dissalow and then to allow again. So activations on virtual machines & hypervisors are allowed in licence settings, but turboactivate.exe display a message which says the contrary anyway.As I was saying, it used to work, and since I made changes both on server and in my OS (updates), it's not working anymore.
Change the setting either on the product key or in the version to allow VM activations. Only after doing that will vm activations be allowed. It's entirely in your control.
radioAs I was telling I already allowed VM activations in the settings. So the reason is something else.I was thinking that some lime lm registry keys could have been not correctly erased maybe. Any other idea ?
Deactivate and remove the product key. Then log into your LimeLM account and find a key to use. Before you copy and paste the key make sure the key says that VM activations are allowed. If it doesn't say that then change the setting (either for the entire version or just for that key).
Then, and only then, activate your product with the key.
radioIt seems that there is a bug in the settings interface. In the key details, I have :"Activations on virtual machines & hypervisors are allowed."
Then when I edit this key, the check box Default (currently: allow) was checked in front of "Allow virtual machine activations?"If I change this to the allow check box, the activation works. If I return to default, the activation doesn't work anymore.
The default behavior is to allow activations (and it's confirmed by what the text beside the check box), but the interface actually dissalow them.
We can't reproduce this behavior.