| Previous | Next |
| FSRM_E_ADR_MAX_EMAILS_SENT | FSRM_E_RMS_TEMPLATE_NOT_FOUND |
FSRM_E_PATH_NOT_IN_NAMESPACE
FSRM_E_PATH_NOT_IN_NAMESPACE means an API request or classification operation supplied a file path that is not contained in the effective scope of the selected rule. FSRM scopes are explicit local namespace roots; matching content does not override scope membership.
Compare the resolved path with the rule scope
- Resolve drive letters, mount points, and junctions to the local path seen by the FSRM server.
- Inspect the exact folder list or dynamic namespace assigned to the rule.
- Add the correct root only when the policy is intended to cover that storage location.
Do not assume that a UNC alias, DFS path, or symbolic route is equivalent to the local namespace recorded by FSRM. Adding a broad parent directory can unexpectedly classify unrelated data. Prefer the narrowest local scope that contains the target files, then run a report-only test to verify which paths are included before applying property or file-management actions.
Automatic file classification · Classification management · Classification manager
Looking for a different code? Search another status or error code.