| Previous | Next |
| FSRM_E_CLASSIFICATION_NOT_RUNNING | FSRM_E_FILE_MANAGEMENT_JOB_EXPIRATION |
FSRM_E_FILE_MANAGEMENT_JOB_ALREADY_RUNNING
What the FSRM state means
FSRM_E_FILE_MANAGEMENT_JOB_ALREADY_RUNNING (0x8004533F) means the File Server Resource Manager task is already running or queued. FSRM permits at most one running task for a given file-management job, so a second manual or scheduled start must be correlated with the existing instance rather than treated as a generic service failure.
Evidence to capture
- File-management job name/ID and its current status: not running, queued or running.
- The trigger that created the existing run: schedule, manual request, automation or retry.
- Queue/start time, current phase, scanned scope and last progress/error event.
- Whether a second caller is issuing
Runwhile the first job is still queued.
Focused test
Query the job status before issuing another run. If it is queued or running, let that instance complete or use the documented cancellation/management path; then start one new instance and verify that its identity and timestamps are new. Do not restart the FSRM service merely to clear the visible state.
Prevent recurrence
Automation should make job starts idempotent: check state, record the existing run, and avoid scheduling/manual overlap. If the job appears permanently running, investigate the running task and its current action instead of submitting additional copies.
Verification
Confirm that one trigger produces one running job, a concurrent duplicate trigger is rejected or coalesced as expected, and the status returns to not running when the job completes.
Technical references
Looking for a different code? Search another status or error code.