| Previous | Next |
| ERROR_OBJECT_NOT_FOUND | ERROR_DATABASE_FULL |
ERROR_DATABASE_FAILURE
Removable Storage Manager could not use its object database
RSM keeps library, drive, slot, media, media-pool, library-request and operator-request state in a central database. The service updates that database as devices move cartridges and applications allocate, mount or eject media. This status is therefore broader than an invalid object GUID: the database operation itself failed, so otherwise valid objects can become unavailable to the current request.
Preserve the database and service logs before attempting repair. Determine whether the failure is limited to one update or affects enumeration and object information generally. Check storage health, permissions and service connectivity, then use the supported RSM export, import or recovery procedure rather than deleting individual database files. After recovery, inventory attached libraries so physical slot and drive contents are reconciled with restored records.
What to inspect
- Test object enumeration and GetNtmsObjectInformation in a fresh RSM session.
- Check the volume hosting the RSM database for I/O, space and file-system errors.
- Inventory every online library after database recovery or restore.
References
- Microsoft: information stored in the RSM database
- Microsoft: Removable Storage Manager API
- Microsoft: reconciling library contents through inventory
Looking for a different code? Search another status or error code.