What does HRESULT 0x80045329 (FSRM_E_INVALID_REPORT_DESC) mean?

 
Previous Next
FSRM_E_INVALID_REPORT_FORMAT FSRM_E_INVALID_FILENAME

FSRM_E_INVALID_REPORT_DESC

FSRM_E_INVALID_REPORT_DESC (0x80045329) The description configured for a storage report is invalid. The problem is limited to report metadata rather than the file data being analyzed.

What to check for FSRM_E_INVALID_REPORT_DESC

  • Check the report description for unsupported characters, malformed text, or policy-restricted content.
  • Use a short plain-text description to verify the report job, then restore the intended text.
  • If the report was imported, validate the source XML encoding and escaping.

Microsoft: FSRM overview

Microsoft: FileServerResourceManager PowerShell module

Microsoft: FSRM troubleshooting guidance

Diagnostic interpretation of FSRM_E_INVALID_REPORT_DESC

FSRM_E_INVALID_REPORT_DESC has the HRESULT value 0x80045329. AllStat records the condition as “The specified report description is invalid.”. For FSRM_E_INVALID_REPORT_DESC, 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_INVALID_REPORT_DESC

  • Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80045329 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_INVALID_REPORT_DESC or the fsrm / report / desc operation.
  • For FSRM_E_INVALID_REPORT_DESC, check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.

Retry and recovery for FSRM_E_INVALID_REPORT_DESC

Retry FSRM_E_INVALID_REPORT_DESC only when the owning API documents a transient state or after the condition described as “The specified report description is invalid.” has changed. For FSRM_E_INVALID_REPORT_DESC, 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.