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 code

Description

1001

Invalid request format.

1002

Invalid interface version in the request URL

1003

Empty header.

1004

Invalid authorisations format.

1005

Correlation id format error.

1006

Tenant id format error.

2001

Invalid challenge format.

2002

Challenge active key generation does not match key package generation.

2102

PSSH missing in the licence request.

2103

No ContentId found in the licence request.

2104

Invalid deviceId found in the licence request.

3001

Content Authorization token version is not supported.

3002

Content Key token version is not supported.

3003

One or more header parameter is missing.

3004

The token encryption key is not valid

3005

The token type is unknown.

3006

The token format is not supported.

3007

The content rights format is not supported.

3008

The entitlements format is not supported.

3009

The account format is not supported.

3011

The account profile format is not supported.

4000

Ungranted request.

4001

The Content Authorization token is missing in the request.

4002

The Content Key token referenced is missing in the request.

4003

Several Content Authorization tokens in the request.

4004

Duplicate content keys.

4005

Invalid expiration date.

4006

Token already played.

4007

Device ID mismatch between the token and the challenge.

4008

The device security level is insufficient.

4009

Tenant ID mismatch between request and tokens.

4010

Credential privilege mismatch

4011

No valid key found for the key id.

4012

Invalid API in header request

4013

An invalid caller in the header request.

4014

Problem related to kid in the request.

4015

The credential not found.

4016

Missing mandatory field.

4017

The device is disabled.

4018

The device specified in the token does not exist.

4019

The device is not associated with the provided account.

4020

The account is not in the ACTIVE state.

4021

The product specified does not have any entitlement.

4022

Specified tenant does not exist in the Rights Management system.

4024

Tenant not found.

4025

The tenant is not Active.

4027

Device binding error.

4028

No compliant track was found.

4029

Airplay output not supported.

4030

Token HDCP and playbackDigitalAVAdapter Usage Rules not supported

4031

Usage rule profile does not exist.

4032

Unexpected Content Key token received in the request.

4033

Session token missing in the request.

4034

Multiple session token not allowed.

4035

AccountId mismatch between the authentication token and session token.

4036

Missing accountId field in ContentAuthZ.

4037

Missing maxSessions field in ContentAuthZ.

4038

Unexpected token type.

4039

The device referenced in the challenge does not exist.

4040

ContentAuthZ or DevAuthN token signature missing in Session token.

4041

Signature from Session token does not match signature from ContentAuthZ or DevAuthN token.

4042

Multiple keys without startDate have been found.

4043

Content startDate too far into the future.

4044

Device HDCP protection failure.

4046

HWPRMLS does not support SDP token.

4047

Content rights end date in the past.

4103

Content not approved for playback over airplay.

4104

Content not approved for playback over digital AV adapter.

4106

Content not allowed for DRM.

4107

Content not distributed by the operator.

4109

Token not reusable on the device

4111

Content Authorization, Device Authentication or SDP token is missing in the request.

4112

No content rights found matching the licence request.

4113

The number of allowed requests exceeded.

5001

Licence generation error reported by DRM SDK.

5002

Key package initialisation error.

6001

Internal error.

6002

Connection or communication protocol error.

6003

Server configuration error.

JavaScript errors detected

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

If this problem persists, please contact our support.