Skip to main content
Skip table of contents

Software PRM licence server error codes

The following error codes are not generated by the player but are generated by the software PRM licence server and are passed to the player as extras. for more information, see SWPRM extra codes.

The following error code details are per the SSP 20.49 documentation version.
Error codeDescription
5000Internal error.
5002Missing EJB.
5101No active player for this crypto version.
5102Unknown operator.
5103Unknown device.
5104Forbidden zeroed sender ID.
4001No connection to KSS, either KSS failure or SLS configuration.
4002Unmanaged protocol version.
6101PRM Credentials authorisation - Denied.
6102PRM Credentials authorisation - Error.
6103PRM Credentials authorisation - Error while converting the viewingWindow.
6104PRM Credentials authorisation - Mismatch content ID.
6105PRM Credentials error.
6200Whitebox crypto error.
6201Whitebox crypto error - Key obfuscation error.
6202Whitebox crypto error - PRM Keys generation error.
6203Whitebox crypto error - Unsupported crypto version.
6300Service KSS error.
6301KSS does not return EMI for this content ID.
7100Service credentials error.
7101Failed to build DCM (builder returned null).
7102Failed to build DMM (builder returned null).
7103Error while building HomeDomain entitlements.
7201Incoherent secret ID / sender ID.
7202Secret ID not found.
7204Error during reconcile operation.
7300Error with the server certificate.
7301Error with PEM encoding.
7401Failed to unprotect the DVS-H content key.
7402Using FairPlay licence is not allowed for these credentials versions.
8001Parameter missing.
8003Wrong value for one of the parameter.
8004Incoherent secretId senderId.
8011Unmanaged DCM range.
8012Unmanaged DMM range.
8013Unmanaged certificate range.
8020FairPlay parsing error.
8021FairPlay error in CKC building.
8022FairPlay - Server is not supporting the protocol used.
8023FairPlay SKR1 integrity check failed.
8024FairPlay configuration internal error.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.