Hi,
We have a customer who has applied the LDK license. Due to some reason they changed the underlying hardware. So, they are detecting the "Cloned Sentinel SL secure storage detected: code 64". We asked them to generate the new request file (c2v) and tried to generate the updated (v2c) file. But, license generator throwed another message while generating as "Container is clone detected. [Licgen Status Internal Identifier: 0x210f00b3000000000]"
Is there any way to cleanup the machine so that they can install the software again and we can generate the new license for them (It is RHEL 6.2 machine)?
or provide the new v2c file which can be applied in their machine to resolve the issue?
Even if they reinstall our software, machine has imprints of license and c2v still throw error while generating the license.
Now, customer can not use our software and they are stuck. One ugly solution is throw away the machine and get the new machine, install the software and generate c2v file and get/apply the v2c file.
We have a customer who has applied the LDK license. Due to some reason they changed the underlying hardware. So, they are detecting the "Cloned Sentinel SL secure storage detected: code 64". We asked them to generate the new request file (c2v) and tried to generate the updated (v2c) file. But, license generator throwed another message while generating as "Container is clone detected. [Licgen Status Internal Identifier: 0x210f00b3000000000]"
Is there any way to cleanup the machine so that they can install the software again and we can generate the new license for them (It is RHEL 6.2 machine)?
or provide the new v2c file which can be applied in their machine to resolve the issue?
Even if they reinstall our software, machine has imprints of license and c2v still throw error while generating the license.
Now, customer can not use our software and they are stuck. One ugly solution is throw away the machine and get the new machine, install the software and generate c2v file and get/apply the v2c file.