Streamkeeper Multi-DRM Status Codes

Multi-DRM status codes

The below table provides the status codes and their descriptions, expected UI behavior (if applicable), and comments to include if you report the error to Verimatrix Customer Care.

Error code	Description	Use case	UI Error Message displayed	Type of UI Message
MDRM-0	Success	General		Success bar
MDRM-1	An unexpected error occurred while processing the request		No	N/A
MDRM-50	Failed to parse input JSON into valid representation		Yes
MDRM-51	Server could not find a resource matching the request URI		Yes
MDRM-52	The server does not support the functionality required to fulfill the request	N/A	Yes	Error bar
MDRM-99	Failed to communicate with the backend service	N/A	Yes	Error bar
MDRM-100	An error occured while creating a DRM in the database		No	N/A
MDRM-101	Failed to retrieve DRM from the database		No	N/A
MDRM-102	An error occured while retrieving a DRM from the database		No	N/A
MDRM-103	Failed to retrieve signing key from the database		No	N/A
MDRM-104	An error occured while retrieving a signing keys from the database		No	N/A
MDRM-105	An error occured while creating a signing key in the database		No	N/A
MDRM-106	An error occurred while retrieving a signing key from the database		No	N/A
MDRM-107	An error occurred while decrypting a DRM record		No	N/A
MDRM-108	An error occurred while encrypting a DRM record		No	N/A
MDRM-109	Unable to retrieve encryption key for database record		No	N/A
MDRM-110	Failed to serialize into a valid JSON representation		No	N/A
MDRM-111	Failed to deserialize JSON into a valid object representation		No	N/A
MDRM-175	Failed to map a database result set into the specified type		No	N/A
MDRM-176	Database record was not modified to prevent conflicting modifications		No	N/A
MDRM-177	User role does not have permissions to perform the requested operation		No	N/A
MDRM-178	Failed to communicate with the database		No	N/A
MDRM-300	Public key must be present in request Provisioning: Add Service Access Key with a blank Public Key field		No	N/A
MDRM-301	Public key could not be Base64 decoded	Provisioning: Add Service Access Key	Yes
MDRM-302	Public key does not match algorithm length requirement	Provisioning: Add Service Access Key	Yes
MDRM-303	Count is outside of the acceptable range of values	Provisioning: Add Service Access Key	No	N/A
MDRM-304	Count could not be converted to an integer	Provisioning: Add Service Access Key	No	N/A
MDRM-305	Database record encryption unsupported in region	Provisioning: Add Service Access Key	No	N/A
MDRM-306	Database failed to process request	Provisioning: Add Service Access Key	No	N/A
MDRM-307	Failed to communicate with database	Provisioning: Add Service Access Key	No	N/A
MDRM-308	User is not authorized to perform the requested database operation	Provisioning: Add Service Access Key	No	N/A
MDRM-309	Failed to retrieve organization from the database	Provisioning: Add Service Access Key	No	N/A
MDRM-311	User is not authorized to perform the request, organization is inactive		No	N/A
MDRM-312	User role does not have permission to access requested resource		Yes
MDRM-325	Request contains unsupported audience value		No	N/A
MDRM-327	Issuer must be present in request	Add Service Access Key	Yes	Error
MDRM-328	Signing key ID must be present in request	Add Service Access Key	Yes
MDRM-329	Key ID could not be converted to a UUID	Add Service Access Key	Yes
MDRM-330	Unable to obtain row lock for database record	Add Service Access Key	No	N/A
MDRM-350	Initialization vector must be present in DRM request		Yes
MDRM-351	Provider must be present in DRM request	Registration of DRM configuration and blank provider field	Yes	Error bar / on screen
MDRM-352	Request URL must be present for DRM	Registration of DRM configuration and blank URL field	Yes	Error bar / on screen
MDRM-353	Request contains unsupported DRM type		No	N/A
MDRM-354	Secret key must be present in DRM request		Yes
MDRM-355	Secret key does not match algorithm length requirement	Registration of DRM configuration	Yes	On screen
MDRM-356	Secret key could not be Base64 decoded	Registration of DRM configuration	Yes	On screen
MDRM-358	Private key must be present in DRM request		Yes
MDRM-359	Private key does not match algorithm length requirement		Yes
MDRM-360	Private key could not be Base64 decoded		Yes
MDRM-361	Certificate must be present in DRM request		Yes
MDRM-362	Initialization vector could not be Base64 decoded		Yes

Updated over 1 year ago