PlayReady licence server error codes
The following error codes are not generated by the player but are generated by the PlayReady licence server and are passed to the player as extras. For more information, see PlayReady extra codes.
The following error code details are per the SSP 20.49 documentation version.
| Error Code | Description |
|---|---|
| 1001 | Invalid request format. |
| 1004 | Invalid authorisations format. |
| 1005 | Correlation id format error. |
| 1006 | Tenant id format error. |
| 2001 | Invalid challenge format. |
| 2103 | No ContentId found in the licence request. |
| 2104 | Invalid deviceUniqueId found in the licence request. |
| 3001 | The content authorisation token version is not supported. |
| 3002 | Unsupported content key token version. |
| 3003 | Invalid signature. |
| 3004 | Decryption error. |
| 3005 | Unknown token. |
| 3006 | Invalid schema error. |
| 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 authorisation token is missing in the request. |
| 4003 | Several authentication tokens found in ATM response, but only one is allowed. |
| 4004 | Duplicate content keys. |
| 4005 | Invalid expiration date. |
| 4006 | Token already played. |
| 4008 | The device does not reach the token security level. |
| 4009 | Tenant ID mismatch between request and token. |
| 4010 | Credential privilege mismatch. |
| 4011 | No keys found for the requested content. |
| 4012 | Invalid API in header request. |
| 4013 | Invalid caller in the header request. |
| 4014 | Problem related to the kid in the request. |
| 4015 | 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 specified product does not have any entitlement. |
| 4022 | The specified tenant does not exist in RMG. |
| 4024 | Tenant not found. |
| 4025 | The tenant is not Active. |
| 4027 | Device ID mismatch between token, device or challenge. |
| 4028 | No compliant track was found. |
| 4029 | Token airplay output is not supported. |
| 4030 | Token HDCP and playbackDigitalAVAdapter usage rules are not supported. |
| 4031 | Unable to find a usage rule profile. |
| 4033 | The session token is missing in the request. |
| 4034 | Multiple session tokens not allowed. |
| 4035 | AccountId mismatch between the authentication token and the session token. |
| 4036 | Missing accountId in contentAuthZ token. |
| 4037 | MaxSession is invalid or missing. |
| 4038 | Unexpected token type. |
| 4039 | The device referenced in the challenge does not exist. |
| 4040 | ContentAuthZ or DevAuthZ token signature is missing in the session token. |
| 4041 | Signature from Session token does not match signature from ContentAuthZ or DevAuthN. |
| 4042 | Multiple keys without startDate have been found. |
| 4043 | The content startDate is too far in the future. |
| 4047 | The content rights end date is in the past. |
| 4103 | The content is not approved for playback over airplay. |
| 4104 | The content is not approved for playback over a digital AV adapter. |
| 4111 | The content authorisation or device authentication token is missing in the request. |
| 4112 | No content rights found which match the licence request. |
| 6001 | Internal error. |
| 6002 | Connection or communication protocol error. |
| 6003 | Server configuration error. |