| Previous | Next |
| FSRM_E_INCOMPATIBLE_FORMAT | FSRM_E_PERSIST_PROPERTIES_FAILED |
FSRM_E_FILE_ENCRYPTED
FSRM_E_FILE_ENCRYPTED occurs when classification or property processing requires file content that FSRM cannot decrypt in its service or module-hosting context. Encryption can therefore block content rules even though the path is visible and ordinary metadata can still be enumerated.
Identify the encryption boundary
- Determine whether the file uses EFS, RMS protection, or another format-specific protection mechanism.
- Check whether the selected module needs file content or can operate only on existing metadata.
- Run the rule under the documented service/module account rather than assuming the interactive user credentials are used.
Do not solve this by granting broad share permissions: authorization to open the path and possession of the decryption capability are different requirements. If protected files must remain unreadable to the server, exclude them from content classification or use properties written before protection. Classification-based RMS documentation also notes that search and content-based classification are unavailable after a document is protected.
Classification-based encryption · Property bag · FSRM overview
Looking for a different code? Search another status or error code.