See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The following table shows FDRM error codes and their descriptions.
| Error code | Description |
|---|---|
|
E_INSUFFICIENT_BUFFER |
Error. The buffer size is too small. |
|
E_FILE_NOT_FOUND |
Error. The file was not found. |
|
S_FDRM_NOTDRMOBJECT |
Success. API call succeeded but the passed-in object is not FDRM-protected. |
|
S_FDRM_NOPROVIDER |
Success. API call succeeded but no FDRM provider is installed. |
|
E_FDRM_FILEDELETED |
Object did not have rights and could not be reactivated. User chose to delete the object. |
|
E_FDRM_LICENSEPENDING |
Object cannot be used now but there is an outstanding request for some type of rights renewal. |
|
E_FDRM_CANCELLED |
User chose not to use object with prompt based rights. |
|
E_FDRM_NOTDRMOBJECT |
API call failed because the passed-in object was not FDRM-protected. |
|
E_FDRM_NOTALLOWED |
Requested operation is not allowed for this object or object does not have sufficient rights to be used. |
|
E_FDRM_NOFORWARDRIGHTS |
Object does not have rights to be forwarded. |
|
E_FDRM_NONOTIFY |
The object was never registered for notifications. |
|
E_FDRM_NOPROVIDER |
API call failed because no FDRM provider was installed. |
|
E_FDRM_UNKNOWNMETRIC |
Unknown metric type requested from FDRM_GetMetric. |
|
E_FDRM_ERRORNOTHANDLED |
Error could not be handled by FDRM_HandleError. |
 Note: |
|---|
| For information about handling FDRM errors in DSHOW filters see DSHOW FDRM Error Handling. |