| Previous | Next |
| FSRM_E_DIFFERENT_CLUSTER_GROUP | FSRM_E_REPORT_JOB_ALREADY_RUNNING |
FSRM_E_REPORT_TYPE_ALREADY_EXISTS
FSRM_E_REPORT_TYPE_ALREADY_EXISTS (0x80045332) The same storage-report type was added more than once to a single FSRM report job. The job must contain each report type only once.
What to check for FSRM_E_REPORT_TYPE_ALREADY_EXISTS
- Review the report-job definition and remove the duplicate report type.
- Check import and automation logic that may append instead of replace report types.
- Rerun the job after the definition contains one instance of each intended report.
Microsoft: FileServerResourceManager PowerShell module
Microsoft: FSRM troubleshooting guidance
Diagnostic interpretation of FSRM_E_REPORT_TYPE_ALREADY_EXISTS
FSRM_E_REPORT_TYPE_ALREADY_EXISTS has the HRESULT value 0x80045332. AllStat records the condition as “A report of the specified type already exists in the report job.”. For FSRM_E_REPORT_TYPE_ALREADY_EXISTS, in practice, interpret that wording at the boundary owned by File Server Resource Manager configuration, rather than treating the value as a generic Windows message.
Evidence to capture for FSRM_E_REPORT_TYPE_ALREADY_EXISTS
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80045332 value before a wrapper converts it to an exception or Boolean result.
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions FSRM_E_REPORT_TYPE_ALREADY_EXISTS or the fsrm / report / type / already / exists operation.
- Reproduce FSRM_E_REPORT_TYPE_ALREADY_EXISTS with the smallest valid input and note whether the result changes with identity, architecture, service state, or target object.
Retry and recovery for FSRM_E_REPORT_TYPE_ALREADY_EXISTS
Retry FSRM_E_REPORT_TYPE_ALREADY_EXISTS only when the owning API documents a transient state or after the condition described as “A report of the specified type already exists in the report job.” has changed. For FSRM_E_REPORT_TYPE_ALREADY_EXISTS, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.
Looking for a different code? Search another status or error code.