We have a client that runs BE 9.1 (rev 4691 updated with be4691RSP4a_280008.exe) on Windows server 2003 SP-1 (actually SBS-2003) and all the jobs run fine for about two weeks then it goes bad. For example if I put a new tape in then run an inventory job it hangs at 99% completed in the current job monitor for a couple of minutes, then I get a "Inventory Drive 0001 -- The job failed with the following error: The device is not ready" error notification then two errors in the application event log:
The first is event ID 34113
Backup Exec Alert: Job Failed
(Server: "*******") (Job: "Inventory Drive 0015") Inventory Drive 0001 -- The job failed with the following error: The device is not ready.
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
The second is event ID 33152
Adamm Mover Error: Unload Status Failure!
Error = ERROR_NOT_READY
Drive = "HP 1"
{495E3E30-E658-4968-AD29-0389CC54CDA4}
Media = ""
{00000000-0000-0000-0000-000000000000}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)
Any jobs submitted after that will result in the same error: the device is not ready. The only way I can fix it is to uninstall BE, reboot, then re-install it all again. It works for a couple of weeks then comes up with the same errors. The tape drive is a brand new HP DAT72 drive with the latest firmware. Any fixes will be gratefully received as it is becoming very irritating. Thanks in advance, John Harris
