| Previous | Next |
| FSRM_E_CLASSIFICATION_SCAN_FAIL | FSRM_E_FILE_MANAGEMENT_JOB_MAX_FILE_CONDITIONS |
FSRM_E_FILE_MANAGEMENT_JOB_NOT_LEGACY_ACCESSIBLE
FSRM_E_FILE_MANAGEMENT_JOB_NOT_LEGACY_ACCESSIBLE means a file-management job contains conditions or settings created through the newer WMI/PowerShell model that the legacy COM or MMC editing path cannot represent safely.
Use the management surface that owns the configuration
- Read and update the job with the FileServerResourceManager PowerShell module or FSRM WMI classes.
- Export the complete job before editing so newer conditions are not silently discarded.
- Avoid recreating the task in the legacy console merely to make it visible there.
The HRESULT protects configuration fidelity. A legacy editor may understand the job name and schedule but not all condition or action fields. Rebuilding the job through that editor can change selection semantics. Use one authoritative automation path, compare the desired configuration with the current object, and test the resulting job against a report-only or limited scope.
File management tasks · FileServerResourceManager module · File management job
Looking for a different code? Search another status or error code.