| Previous | Next |
| FSRM_E_MESSAGE_LIMIT_EXCEEDED | FSRM_E_CANNOT_RENAME_PROPERTY |
FSRM_E_OBJECT_IN_USE
FSRM_E_OBJECT_IN_USE blocks deletion or replacement of an FSRM object that is currently running or referenced by another committed object. Typical dependencies include rules referencing modules or properties and jobs using property conditions.
Find the dependency before deleting
- Enumerate rules, file-management jobs, and report definitions that refer to the object name or identifier.
- Stop or wait for active classification and file-management work before changing shared definitions.
- Remove the dependent references, commit those changes, and only then delete the object.
Forcing service restarts does not remove persistent references and can leave automation expecting an object that no longer exists. Property definitions in particular cannot be deleted while file-management conditions reference them. Treat this HRESULT as a configuration graph problem: map the references, update consumers, and preserve stable names where external scripts depend on them.
Property definition · File management job · Classification manager
Looking for a different code? Search another status or error code.