What does HRESULT 0x80045395 (FSRM_E_LEGACY_SCHEDULE) mean?

 
Previous Next
FSRM_E_FILE_MANAGEMENT_JOB_INVALID_CONTINUOUS_CONFIG FSRM_E_CSC_PATH_NOT_SUPPORTED

FSRM_E_LEGACY_SCHEDULE

FSRM_E_LEGACY_SCHEDULE is the failure HRESULT 0x80045395 (signed decimal -2147200107, unsigned decimal 2147767189). Its severity bit is 1, facility is 4 (FACILITY_ITF), and the facility-specific code field is 0x5395.

The stored FSRM schedule must be upgraded on this server

This HRESULT indicates that an FSRM object contains a schedule created by an earlier File Server Resource Manager version and that representation is incompatible with the current Windows Server. Microsoft’s message directs the administrator to edit the schedule on the current computer so it can be rewritten in the supported format.

AllStat records the official condition as: “The object contains a schedule that was created by using an earlier version of File Server Resource Manager and that is incompatible with the current version of Windows Server. Edit the schedule on this computer to update it.” The wording should be interpreted at this FSRM stage, not as a generic file-system or COM failure.

Where the failure boundary lies

The schedule serialization is the rejected component. The quota, report, classification, or file-management policy that owns it may otherwise be valid. This differs from a deprecated job, where the object is flagged because its broader feature set is obsolete, and from a syntactically invalid new schedule supplied by a caller.

Likely causes to separate

  • FSRM configuration was imported or migrated from an older Windows Server release.
  • An in-place upgrade retained a scheduled object whose legacy representation was never opened and saved.
  • Automation copies serialized schedule data instead of creating a new schedule through the current API.
  • A restored FSRM database contains objects last committed by an older service version.

Evidence worth preserving

  • Identify the owning FSRM object, its schedule, last-modified time, source server version, and migration method.
  • Export the object before editing so recurrence, start time, and policy configuration can be compared afterward.
  • Record whether the HRESULT appears during enumeration, save, import, or scheduled execution.
  • Check other imported objects from the same source for the same legacy schedule format.

Diagnostic sequence

  • Open the affected object on the current server and inspect every recurrence and start-time setting.
  • Edit and save the schedule through the current FSRM console, PowerShell module, WMI class, or documented API.
  • Retrieve the object again and verify the next-run calculation rather than assuming a successful save preserved semantics.
  • Test one manual run and one scheduled trigger in a non-destructive scope.
  • Update migration automation to recreate schedules with current objects instead of copying opaque serialized data.

Retry and recovery

Recommit the schedule on the current server. A retry of the original operation without rewriting the schedule is deterministic and should not be looped. When the old recurrence cannot be represented exactly, create a new supported schedule and document the intentional behavioral change before enabling the job.

What this HRESULT does not establish

The code does not prove that the whole FSRM database is from an unsupported version, and it does not say that the job action or namespace is invalid. Editing unrelated policy fields is unnecessary unless separate validation errors identify them.

Difference from nearby FSRM results

FSRM_E_FILE_MANAGEMENT_JOB_DEPRECATED flags the job itself as deprecated. FSRM_E_LEGACY_SCHEDULE can be repaired by upgrading the schedule representation while retaining the object.

Practical scenario

A file-management job is imported from an older server and appears in the console, but enabling it returns this HRESULT. The administrator exports the definition, recreates and saves its monthly schedule on the new server, verifies the next run, and then enables the job.

Guidance for software and telemetry

Treat schedules as versioned API objects, not portable binary blobs. Migration tools should log source and target server versions and verify calculated run times after conversion.

Official Microsoft references

Looking for a different code? Search another status or error code.