| Previous | Next |
| FSRM_E_FILE_MANAGEMENT_EXPIRATION_DIR_IN_SCOPE | FSRM_E_PROPERTY_DELETED |
FSRM_E_FILE_MANAGEMENT_JOB_ALREADY_EXISTS
FSRM_E_FILE_MANAGEMENT_JOB_ALREADY_EXISTS means the job manager already contains a persistent job using the requested name. Job names identify configuration objects and can also be referenced by automation and scheduled tasks.
Update or version the existing job deliberately
- Enumerate existing jobs and compare scope, conditions, operation type, schedule, and actions.
- Modify the intended object instead of creating another job with the same display name.
- If replacement is required, disable scheduling, preserve reports, remove the old job, and then create the new version.
Appending random suffixes avoids the immediate HRESULT but creates duplicate policies that can process the same files twice. Treat the name collision as evidence that deployment is not idempotent. Use a stable desired-state workflow that gets the job by name, validates its configuration, and changes only the necessary properties.
File management job · MS-FSRM overview · FSRM overview
Looking for a different code? Search another status or error code.