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. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The description for Event ID ( 11 ) in Source ( ADIC1000 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: \Device\MediumChanger0.
|English: This information is only available to subscribers. An example of English, please!|
|Concepts to understand:|
What is a DLL?
What is causing the “The description for Event ID ( … ) in Source ( …. ) cannot be found… “?
In my case, a PowerVault 132T from Dell displayed "Picker Error" "Reset System". After resetting, I received this event every 5 seconds. I rebooted the server and the error was gone.
If the programmer of the device driver would have created the event log message dll file properly, this event should read:
The driver detected a controller error on \Device\MediumChanger0.
As is the case with event id 11 from other devices, this may indicate problems with the hardware or connectivity (SCSI cables, improper SCSI termination, etc...). The device itself may not necessarely exhibit a particular problem.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated