| Previous | Next |
| ERROR_INVALID_CLEANER | ERROR_OBJECT_NOT_FOUND |
ERROR_UNABLE_TO_CLEAN
The drive could not be cleaned with the available configuration
CleanNtmsDrive queues a library request; successful queuing does not guarantee that the robotic movement and cleaning cycle will finish. Failure can reflect a drive that does not support automated cleaning, no usable cleaner cartridge, incompatible media, changer trouble or a device-service condition. For a stand-alone drive, RSM records the cleaning time rather than controlling a robotic cycle, so the hardware topology matters.
Inspect the library request and operator-request queues, then examine drive and changer operational state. Check whether a cleaner is online, reserved and not spent. Hardware logs may show a load, transport or drive-cleaning failure that is more precise than the final Win32 code.
What to inspect
- Read the failed library request and device-service operator request.
- Verify cleaner availability, reservation and remaining uses.
- Check drive and changer hardware logs for the same operation.
References
- Microsoft: queuing an RSM drive-cleaning request
- Microsoft: RSM operator-request types and states
- Microsoft: RSM object types, GUIDs and operational state
Looking for a different code? Search another status or error code.