Event ID/Source search
Keyword search
Example: Windows cannot unload your registry file
EvLog 3.0 – 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 entire company using just one server, these days that's no longer the case.New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers 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 the servers.
read more...
Event ID: 9 Source: symc8xx
| Source: symc8xx |
| Type: Error |
| Description: The device, \Device\Scsi\symc8xx1, did not respond within the timeout period. |
| English: Request a translation of the event description in plain English. |
| Comments: EventID.Net This event is common to many controllers. See the link to "EventID 9 from source adpu160m". 
EventID.Net 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.
|
| Private comment: Subscribers only. See example of private comment |
| Links: ME154690, EventID 9 from source adpu160m |
| Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... |
| Feedback:
Send comments or solutions
- Notify me when updated
|
| Printer friendly |
Subscribe to EventID.Net now!