| Previous | Next |
| FSRM_E_RMS_NO_PROTECTORS_INSTALLED | FSRM_E_PROPERTY_MUST_APPLY_TO_FOLDERS |
FSRM_E_RMS_NO_PROTECTOR_INSTALLED_FOR_FILE
FSRM_E_RMS_NO_PROTECTOR_INSTALLED_FOR_FILE is more specific than having no protectors at all: protection components are installed, but none claims the current file format. Other document types in the same job may still be processed successfully.
Handle the failed extension explicitly
- Confirm the actual format rather than trusting only the filename extension.
- Check the installed protector supported-file list and version.
- Exclude unsupported formats or deploy a protector designed for that document type.
Renaming the extension can send incompatible bytes to a protector and risks data loss. Build the job scope from formats that have been tested with the selected RMS template. When a batch contains mixed types, preserve per-file results and do not treat successful protection of Office documents as evidence that every selected format is supported.
Classification-based encryption · Deploy encryption · File management tasks
Looking for a different code? Search another status or error code.