| Previous | Next |
| FSRM_E_CACHE_MODULE_ALREADY_EXISTS | FSRM_E_FILE_MANAGEMENT_JOB_ALREADY_EXISTS |
FSRM_E_FILE_MANAGEMENT_EXPIRATION_DIR_IN_SCOPE
FSRM_E_FILE_MANAGEMENT_EXPIRATION_DIR_IN_SCOPE prevents a file-management job from moving expired files into a directory that the same job scans. Such a layout can cause moved files to be evaluated and expired repeatedly.
Separate source and expiration namespaces
- Compare the normalized expiration path with every namespace root, including mount points and inherited subdirectories.
- Choose a destination outside all job scopes and outside any overlapping retention job that would immediately process it.
- Verify write permissions for the server computer account after changing the path.
A different textual path can still resolve inside the same scope through a mount point or reparse point. Do not work around validation with an alias. Design the expiration repository as a separate managed namespace with its own retention and access policy, then test the move and report output using one file.
File management job · Retention scenario · FSRM overview
Looking for a different code? Search another status or error code.