Atapi Event 9 Error
Contents |
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an atapi error in event viewer entire company using just one server, these days that's no longer the case. New computers
Atapi Error Event 11
are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers
Atapi Incompatible Error
is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of
Atapi Error 11 Device Ide Ideport0
the servers. read more... Event ID: 9 Source: atapi Source: atapi Type: Error Description:The device, \Ide\IdePort0, did not respond within the timeout period. English: This information is only available to subscribers. An example of English, please! Comments: Anonymous In my case, this problem was solved after uninstalling KASPERSKI AV/IS. x 11 Anonymous In my case, error indicated \Device\Ide\IdePort1. Upon going to registry, went to regedit and navigated to hkey_local_machine\hardware\devicemap\scsi\scsi port 1 - noticed it was labeled as "cdrom atapi error windows 7 peripheral" - replaced cdrom drive, no more errors. x 4 John Panton Message: IDE-port 0 not responding within the timeout period. It could be HDD 0 or IDE/ATAPI controller, but first: - Check the cables from the MB to the HDD. - Check the operation of any other devices connected to the same cable as HDD 0- even disconnect any CD/DVD drives on that cable. x 9 Alexander Solano In my case, this problem was solved after uninstalling Roxio's Easy CD Creator 5.0. There are known compatibility issues between Windows XP and versions of Easy CD Creator earlier than version 5.1. See ME310628 for details. x 51 Peter Hayden In one case, a computer was running Windows 2000 Professional SP4 that was configured to boot from a SCSI drive. An IDE drive was temporarily added in order to perform some work on it. When the computer was started this event was repeated four times and then followed by EventID 11 from source atapi. Windows showed the disk as normal but Partition Magic 8.0 showed it as "BAD". Remove or replace the faulty hard drive. x 54 Anonymous Getting this error could mean that your hard disk controller is not working well. Check to see if you have difficulty accessing the hard disk (slow), or if the hard disk is having trouble powering up. Even though the controller is not working well you can still
One games Xbox 360 games PC event id 9 iastor games Windows games Windows phone games Entertainment All event id 11 disk Entertainment Movies & TV Music Business & Education Business Students & event id 9 volsnap educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security http://www.eventid.net/display-eventid-9-source-atapi-eventno-2060-phase-1.htm Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft https://support.microsoft.com/en-us/kb/314093 Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript https://community.spiceworks.com/windows_event/show/546-atapi-9 CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 9 (Error) Source: atapi How important https://www.virtualbox.org/ticket/8478 is this event? (4 votes) 1 2 3 4 5 not important very important Description The device, \Ide\IdePort , did not respond within the timeout period. The device, \Ide\IdePort , did not respond within the timeout period. Add link Text to display: Where should atapi error this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages The device, \Device\Ide\IdePort3, did not respond within the timeout period.
Jun 23, event id 9 2009 The device, \Device\Ide\IdePort0, did not respond within the timeout period. Aug 10, 2009 The device, \Device\Ide\IdePort1, did not respond within the timeout period. Aug 10, 2009 Das Gerät \Device\Ide\IdePort0 hat innerhalb der Fehlerwartezeit nicht geantwortet. Jun 06, 2011 message string data: \Device\Ide\IdePort0 Mar 20, 2012 message string data: \Device\Ide\IdePort2 Nov 13, 2012 Comments Thai Pepper May 27, 2011 Steve M. Other, 101-250 Employees How to troubleshoot error messages about Event ID 9 and Event ID 11 http://support.microsoft.com/kb/314093 In almost all cases, these messages are posted because of hardware problems. The source may be the controller or (more probably) a device that is attached to the controller. The hardware problem can be poor cabling, incorrect termination or transfer rate settings, slow device relinquishment of the SCSI bus, a faulty device, or in rare cases, a poorly written device driver. Pure Capsaicin Jun 30, 2011 peter Non Profit, 101-250 Employees thanks for info Pimiento Aug 31, 2011 James51G Manufacturing, 1-50 Employees Some old PentiumOpened 6 years ago Last modified 5 years ago Event ID 9: did not respond within the timeout period Reported by: ToddAndMargo Owned by: Priority: critical Component: other Version: VirtualBox 3.0.12 Keywords: Cc: Guest type: Windows Host type: Linux Description host: centos 5.5 x64, 32 GB memory guest: windows server 2003, sp2, r2 32 bit, 4 GB memory VM: VB 3.2.12 Hi All, Sorry for coming directly to you guys with this, but since I can not purchase support from you guys, I have no other choice. And, this is a real emergency. I have got to get this fixed or my goose is cooked (as in fired). I am in trouble here. I just got a Fox Pro database corruption. The SATA controller was giving me Event: 9 iaStor error out the nose, so I switched our controller from an "IATA89ENU v8.9.0.1023" (SATA) controller to a "Intel 82371AB/EB 5.2.3790.3959" (IDE/ATAPI) controller. It stopped the iaStor errors. But now I get the same Event:9 ATAPI errors. I HAVE TO STOP THESE ERRORS! Log files will follow shortly. Many thanks, -T Event Type: Error Event Source: atapi Event Category: None Event ID: 9 Date: 3/2/2011 Time: 10:21:14 AM User: N/A Computer: VB-PPRO2 Description: The device, \Device\Ide\IdePort0, did not respond within the timeout period. Attachments event9.zip (58.4 KB) - added by ToddAndMargo 6 years ago. logs for event 9 WindowsXPE.7z (19.5 KB) - added by birdie 5 years ago. The entire virtual machine, excluding a bootable Windows XP SP2 BartPE CD-Rom Change History Changed 6 years ago by ToddAndMargo attachment event9.zip added logs for event 9 comment:1 Changed 6 years ago by ToddAndMargo I am finding this error all over my other Windows guests. Not a *flood* like the guest running M$SQL Server 2008, but here and there: Event Type: Error Event Source: iaStor Event Category: None Event ID: 9 Date: 1/3/2011 Time: 1:54:23 PM User: N/A Computer: VB-WINXP Description: The device, \Device\Ide\iaStor0, did not respond within the timeout period. Also: a work around to help you guys troubleshoot thi