Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 9 Source: adpu160m

Source
Level
Description
The device, \Scsi\adpu160m, did not respond within the timeout period.
Comments
 
According to Microsoft "in almost all cases, these messages are being posted due to hardware problems with either the controller or, more likely, a device that is attached to the controller in question. The hardware problems can be associated with poor cabling, incorrect termination or transfer rate settings, lazy or slow device responses to relinquish the SCSI bus, a faulty device, or, in very rare cases, a poorly written device driver." See ME154690 link below.
On my virtual servers (2) running on a HP D530C host with 2GB RAM this occurs regularly, even though device manager in the VM shows no problem (Microsoft Virtual Machine PCI SCSI Controller). I am running Windows 2003 Server as the host with 2 Windowsr 2003 VM Terminal servers (512 MB Ram each) as guest test OSs running from Virtual Server 2005 R2 on the host. Other than the repetition of the each VM of this error in the System Log, each has been extremely stable for over 65 days. This may be just a time out issue and benign.
In n order to solve this problem I downloaded the free "HP StorageWorks Library and Tape Tools". I just installed it on the server in question and ran through a load of the tests. It turned out it was the tape drive's firmware that was out of date. So, using the program, I downloaded the latest version and did what it said. The tape device disappeared, then, after waiting 5 minutes, the drive reappeared (much to my relief!) with the firmware updated. Result: the drive is up and running again and no more error messages.
See ME259237, ME305547, ME314093, and ME885464 for information on this problem.

From a newsgroup post: "Are you using Roxio GoBack (or Symantec GoBack) software? If so, then you should know that one poster in the XP hardware newsgroup stated that he was told by his PC seller that Roxio GoBack (version 3, latest updates) was generating the error you describe below. He said he had disabled GoBack and still received the error, proceeding to an entire uninstall to completely get rid of the problem.
Otherwise, this error is usually due to poor cabling, loose cables, a failing controller, or failing hardware, such as the Primary IDE controller for your hard drive".

If the event description points to old hardware, read ME315539 for information on how to remove the old hardware from Device Manager.

See the link to "EventID 9 from source atapi" and "Compaq User Guide ProLiant CL380" for additional information.
In one case, a computer was running Windows 2003 that had an Adaptec Ultra 160 (19160) SCSI Adapter that was being used to control separate C: and D: drives. After a while the D: drive failed. This resulted in the SCSI BIOS taking a long time to run and eventually timed out. When Windows loaded and this Event ID appeared, Windows took a long time to start up (even when the swap file was moved to the C: drive). The D: drive was not accessible. This event ID was accompanied by EventID 11 from source Disk, EventID 117 from source adpu160m and EventID 10026 from source DCOM.
Resolution: Remove or replace the faulty hard drive.


After adding Dell Open Manage Array Manager to a PowerEdge Server we received 6 of these in the event log when OS started the SCSI drivers. The tape backup driver worked but was much slower. Upgrading the SCSI controller driver fixed the problem.
Compaq DL380 G3, "Compaq 64-Bit/66MHz Dual Channel Wide Ultra3 SCSI Adapter"(adpu160m driver) and Compaq "COMPAQ 20/40GB DAT 8 AL" Tape Drive with AutoLoader. I was getting this event and nothing that I tried to fix this problem worked. In the end, I upgraded to the Compaq DL380 Support Pack version 6.4 and that fixed both the stop errors in event viewer and the problems I was having with the Tape Drive itself (not recognizing the tapes, errors stating it was offline etc.).
I called HP support on this one, as we were seeing blue screens when ever a bad tape was discovered in our tape library. They said this is a symptom of a known driver problem for the HP ProLiant 64-Bit66-Mhz Dual Channel Wide Ultra3 SCIS Controller. Download the latest driver from HP. A fix was implemented in the 1 Jul 03 release V6.1.640.100 of this driver. There are special instructions for installing that need to be followed. Suggest calling HP for those as they don't appear to be included with the updated driver package.
When the AHA-29160 is inserted in to Windows 2000 Professional it automatically installs the incorrect driver for the card, it installs the Adaptec AIC-7892 ultra 160/m PCI SCSI card. This driver is for the chipset on the AHA-29160, not the card, and as a result this error message is logged in the system log. Solution: Update the AHA-7892 driver with the driver for the AHA-29160 that is digitally assigned. To do this, click Start > Setting > Control Panel > System > Hardware tab > Device Manager button > double left click SCSI and RAID controllers > right click Adaptec SCSI Card AIC-7892 Ultra 160 SCSI > left click Properties > click Drivers tab > click Update Driver button > locate driver and update the driver to Adaptec AHA-29160. The driver can be found on the Adaptec website.
This event occured at exactly the same time as event ID: 57665 (source Backup Exec - error reported "The request could not be performed because of an I/O device error"). For solutions see Veritas article "How to resolve SCSI bus timeouts" at Veritas TechNote ID: 191158 link below.
I find that if I get a cyclic redundancy check (which 90% of the time turns out to be a bad SDLT tape), this error occurs. This happens on my other DLT drives as well when bad media is encountered. I usually use a different tape and it works ok.
Try cleaning the tape drive (had to clean it twice before the error stopped). Retentioning the tape(s) may also help.
It is generated when the device cannot initialize within the normal time period, or when it stops responding during normal operation. The event source is the device driver name. This occurs on one of the following three circumstances:
- a drive or device controller cannot initialize due to hardware failure or IRQ conflict. If you have installed new hardware, remove it and read the installation manual again.
- a device reports to the PnP service but does not respond to the OS. try rebooting.
- a removable media on the mass controller that generated the error (like backup tape, DLT, or CDROM) is badly written and the drive resets so frequently that it doesn't report to the OS.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...