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.
Target did not respond in time for a SCSI request. The CDB is given in the dump data.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is iSCSI?
What is a CDB?
According to Microsoft, this event is logged when the target did not complete a SCSI command within the timeout period specified by SCSI layer. The dump data will contain the SCSI Opcode corresponding to the SCSI command. User can refer to SCSI specification for getting more information about the SCSI command.
See iSCSI Users Guide (EV100227).
From a Microsoft support engineer post:
Event ID 9 is logged when the target did not complete a SCSI command within the timeout period specified by SCSI layer. The dump data will contain the SCSI Opcode corresponding to the SCSI command.
Please try the following resolution to solve this issue:
1. On the Windows system, click Start, click Run, type regedit and press Enter.
2. In HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk, edit or add the TimeOutValue entry to set it to 60 seconds in decimal format (0000003c in hexadecimal).
- To edit the value for the TimeOutValue entry if it already exists, double-click the entry, enter the new value, and click OK.
- To add the TimeOutValue entry if it does not yet exist, right-click anywhere in the list of values, and then click New > DWORD value. Name the new value TimeOutValue, and then double-click it to edit the setting.
If you are not running iSCSI Initiator v1.05a, you can also check the following:
Go to the registry value MaxRequestHoldTime at the following registry key:
Increase the value to 90. If that does not work, try 120.
Meanwhile, please also contact to your iSCSI device manufacturer to confirm whether this issue is caused by the iSCSI device.
|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