Skip to main content
Skip table of contents

NAGRA CONNECT PRM licence server error codes

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

The following error code details are per the SSP 20.49 documentation version.
Error codeDescription
1001Invalid request format.
1002Invalid interface version in the request URL
1003Empty header.
1004Invalid authorisations format.
1005Correlation id format error.
1006Tenant id format error.
2001Invalid challenge format.
2002Challenge active key generation does not match key package generation.
2102PSSH missing in the licence request.
2103No ContentId found in the licence request.
2104Invalid deviceId found in the licence request.
3001Content Authorization token version is not supported.
3002Content Key token version is not supported.
3003One or more header parameter is missing.
3004The token encryption key is not valid
3005The token type is unknown.
3006The token format is not supported.
3007The content rights format is not supported.
3008The entitlements format is not supported.
3009The account format is not supported.
3011The account profile format is not supported.
4000Ungranted request.
4001The Content Authorization token is missing in the request.
4002The Content Key token referenced is missing in the request.
4003Several Content Authorization tokens in the request.
4004Duplicate content keys.
4005Invalid expiration date.
4006Token already played.
4007Device ID mismatch between the token and the challenge.
4008The device security level is insufficient.
4009Tenant ID mismatch between request and tokens.
4010Credential privilege mismatch
4011No valid key found for the key id.
4012Invalid API in header request
4013An invalid caller in the header request.
4014Problem related to kid in the request.
4015The credential not found.
4016Missing mandatory field.
4017The device is disabled.
4018The device specified in the token does not exist.
4019The device is not associated with the provided account.
4020The account is not in the ACTIVE state.
4021The product specified does not have any entitlement.
4022Specified tenant does not exist in the Rights Management system.
4024Tenant not found.
4025The tenant is not Active.
4027Device binding error.
4028No compliant track was found.
4029Airplay output not supported.
4030Token HDCP and playbackDigitalAVAdapter Usage Rules not supported
4031Usage rule profile does not exist.
4032Unexpected Content Key token received in the request.
4033Session token missing in the request.
4034Multiple session token not allowed.
4035AccountId mismatch between the authentication token and session token.
4036Missing accountId field in ContentAuthZ.
4037Missing maxSessions field in ContentAuthZ.
4038Unexpected token type.
4039The device referenced in the challenge does not exist.
4040ContentAuthZ or DevAuthN token signature missing in Session token.
4041Signature from Session token does not match signature from ContentAuthZ or DevAuthN token.
4042Multiple keys without startDate have been found.
4043Content startDate too far into the future.
4044Device HDCP protection failure.
4046HWPRMLS does not support SDP token.
4047Content rights end date in the past.
4103Content not approved for playback over airplay.
4104Content not approved for playback over digital AV adapter.
4106Content not allowed for DRM.
4107Content not distributed by the operator.
4109Token not reusable on the device
4111Content Authorization, Device Authentication or SDP token is missing in the request.
4112No content rights found matching the licence request.
4113The number of allowed requests exceeded.
5001Licence generation error reported by DRM SDK.
5002Key package initialisation error.
6001Internal error.
6002Connection or communication protocol error.
6003Server configuration error.
JavaScript errors detected

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

If this problem persists, please contact our support.