What does Event ID 5/7/9/11/15 mean while troubleshooting tape device related issues with Backup Exec

  • Article ID:100028072
  • Modified Date:
  • Product(s):


While troubleshooting a tape device related issue with Backup Exec, event id 5 / 7 / 9 / 11, and/or 15 is observed in the Windows System Event log.



  • Event ID 5. This error indicates SCSI parity errors.  
  • Event ID 7. This error indicates that bad blocks exist.  
  • Event ID 9. This issue indicates SCSI bus timeouts.  
  • Event ID 11. The driver detected a controller error on <DEVICE_NAME> 
  • Event ID 15. The device, <DEVICE_PATH>, is not ready for access yet.

Veritas QuickAssist (VQA) can assist in discovering hardware related issues.  Click here to learn more and download the utility.



NOTE: Please have a technical support representative from the device manufacturer available while being assisted by a Veritas Technical Support representative involving devices exhibiting these event ID errors. Veritas Technical Support can assist in provide product level support only. 

Below are some additional details that may assist you and the device manufacturer's technical support representative in troubleshooting the storage device. 

  • Event ID 5: This error can be caused by a faulty SCSI card or a faulty SCSI termination. If this error occurs contact the hardware's manufacturer.
  • Event ID 7: This error can be caused by an outdated tape device driver, faulty media, or dirty read/write heads on the tape drive. To correct this error, update to the most recent Backup Exec tape device drivers, run a cleaning job, and replace the media with new media, if possible. If the error continues, contact the hardware vendor.
  • Event ID 9:  This error usually occurs when the SCSI bus resets itself, or when the SCSI hardware does not respond quickly. Sometimes this error is caused when another device shares the same cable. In certain high-end servers, you may need to move the SCSI card to a different Peripheral Component Interconnect (PCI) slot that does not share the same bus as a RAID controller. To correct this error, slow down the SCSI bus and install the most recent SCSI drivers and firmware.
  • Event ID 11: This error could be a result of a bad or corrupted device driver, a hardware problem, a malfunctioning device, poor cabling, or termination issues. This is an error occurring within the driver or hardware itself. To correct this error, slow down the SCSI bus and install the most recent SCSI drivers and firmware.
  • Event ID 15: This error indicates that the device is not ready to be accessed. This error usually occurs when the device is malfunctioning or is configured incorrectly. This error may also occur if the incorrect drivers are loaded or the drivers are not up to date. Check with the manufacturer for updated firmware, drivers, or known issues. This could also indicate a malfunctioning device.
    Ensure correct and up to date drivers are loaded for the device. Also make sure the device is ready to be accessed. Contact the hardware vendor if the device is observed to be malfunctioning.


Related Articles

What is a Tape Alert and why do they appear in Backup Exec job logs?

Was this content helpful?

Get Support