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 ( 389 ) in Source ( ibmchgr ) 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\Changer0
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a DLL?
What is causing the “The description for Event ID ( … ) in Source ( …. ) cannot be found… “?
As per IBM: "The messages arises as a result of some logging the device driver performs when a command is issued to the device and there is less data returned than expected. In this case an Inquiry command is issued for more data than is available. The adapter card reports a data under-run and the Ultrium Device Driver logs it but continues the operation successfully. Inquiries are issued frequently and contribute to these messages. Aside from filling the event log there is no impact to the customer". See the link to "IBM Support Solution #1144183" to solve this problem.
|Private comment: Subscribers only. See example of private comment|
|Links: IBM Support Solution #1144183|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated