| Previous | Next |
| FSRM_E_FILE_MANAGEMENT_JOB_ALREADY_RUNNING | FSRM_E_FILE_MANAGEMENT_JOB_CUSTOM |
FSRM_E_FILE_MANAGEMENT_JOB_EXPIRATION
FSRM_E_FILE_MANAGEMENT_JOB_EXPIRATION is specific to the expiration action of an FSRM file-management job. A file met the job conditions, but FSRM could not move it into the configured expiration directory.
Check the move destination and file state
- Verify that the expiration directory exists, is writable by the server, and is outside the scanned scope.
- Check path length, name collisions, open handles, encryption, and cross-volume behavior for the failing file.
- Use the job report and
LastErrorto identify the exact source and destination.
Expiration is not deletion: FSRM moves qualifying files under an expiration root while preserving a managed retention workflow. Do not substitute a custom delete command as a quick fix, because it changes recovery and auditing semantics. Correct the destination or file-access problem, then test with one representative file before rerunning the full job.
File management job · Retention scenario · FSRM overview
Looking for a different code? Search another status or error code.