| Previous | Next |
| ERROR_UNABLE_TO_CLEAN | ERROR_DATABASE_FAILURE |
ERROR_OBJECT_NOT_FOUND
The generic RSM object identifier no longer resolves
This code is used when the requested object class is not known in the current RSM database. Unlike type-specific errors such as invalid media or invalid drive, the caller may not yet know which kind of RSM object the GUID was intended to represent. Common causes are stale cached identifiers, deletion during device reconfiguration, or using an identifier obtained from a different RSM server.
Re-enumerate objects in the correct server session and track both GUID and object type in application state. If the failure follows a database import or restore, rebuild cached relations instead of assuming GUID continuity. Also handle change notifications so deletion or reclassification invalidates references held by long-running management processes.
What to inspect
- Log the expected NtmsObjectsTypes value with the GUID.
- Enumerate from the parent container rather than scanning unrelated types.
- Invalidate cached identifiers after deletion, restore or device-change events.
References
- Microsoft: RSM object types, GUIDs and operational state
- Microsoft: Removable Storage Manager API
- Microsoft: Removable Storage Manager objects and administration
Looking for a different code? Search another status or error code.