1. SSL connect error
If you attempt to install and activate an LDK license under Windows 7 or Windows Server 2008 R2 without SP1 installed you may see an “SSL connect” error (see http://support.microsoft.com/kb/975858).
The Harlequin RIP is not supported under Windows 7 or Windows Server 2008 R2 without SP1. Therefore, you should install SP1 and try again. Note that this error does not use up the activation on the EMS server.
2. Login by product key failed: SSL connect error
If you attempt to activate a license and the following Login by product key failed: SSL connect error the machine’s root certificate might be out of date, (possibly because Windows updates have not been applied). YOu can check this by using a web browser to go to https://ev‐root.digicert.com/. This page should load without any SSL certificate warnings.
If warnings do appear, you should download the latest root certificate
and install it in the Windows Trusted Root Store.
There are instructions on how to do this here:
3. Error 33
On very rare occasions the activation to the EMS server succeeds, but the local installation of the V2C file fails. An Err (33) error message is displayed followed by a dialog stating that “Activation was successful but creating the software key failed”, you must accept the prompt to save the v2c file so that it can be applied later (see the post How can I apply a saved V2C file).
4. Error 48
If you decide not to install the LDK runtime when installing the RIP or when an installation is not successful you may see the error: Err (48). This means that no vendor library is available, which points to a problem with the LDK runtime.
You can install the LDK runtime (post RIP install), by running the RIP installer and selecting LDK only (for use with remote RIP). Once haspdinst.exe is installed run that executable from an admin command prompt using:
5. Error 400—incompatible enforcement type
If the Sentinel Runtime Environment has not beeninstalled and you try to activate a RIP, the following message will appear:
Activation failed (400) Could not generate the license because: enforcement type is incompatible
This should not occur when using the Global Graphics installer, as that will have installed the correct runtime environment. See the post How do I check and manually install the LDK components? for installing the LDK components locally.
6. Error 400—concurrency count exceeded
If you ship dongles for use with the LDK, each one has a limit to the concurrency of the license that it supports (that is, the number of RIPs that can be licensed from that dongle); see the post What are concurrency and activation counts?. If you try to activate a license with concurrency higher than that allowed by the dongle hardware the following message will appear:
Activation failed (400): Could not generate the license because: The concurrency count defined in Feature id 410 of Product id 10410 exceeds the maximum limit of 10 supported on the target device
The top line of data printed on the back of the dongle will be ‘Net10’, ‘Net50’ or ‘Net250’; the number at the end shows the maximum concurrency that the dongle can support.
7. Error 400—No more activations
If you try to use a Product Key which has already been activated the following message appears:
Activation failed (400): No more activations available for this Product Key
8. Error 400—Not a valid C2V
If you attempt to use an SL Product Key to program a dongle the following message appears:
Activation failed (400): Not a valid C2V
This error will not decrement the available activation count, you can try again with the right key.
9. Error 400—Protection Key ID activated or does not belong to this Product Key
If you try to activate a product key for an update but you select the wrong protection key in the LDK Tool, the following message appears:
Activation failed (400): Protection Key
ID (nnn) either activated or does not belong to this Product Key
This error will not decrement the available activation count, you can try again with the right key with no ill effects.
10. Security software
In rare cases the LDK activation may fail because of interactions with security software. At present the only known problematic software is Lumension Endpoint Security (LES) before v4.5 SR1. If an activation fails you should stop any anti‐virus and other malware defense and retry the installation.