Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 972107 - Last Review: September 28, 2009 - Revision: 3.0
Error event ID 5 is logged in the System log on a computer that uses the iSCSI Software Initiator to connect to an iSCSI target device
On a computer that uses the iSCSI Software Initiator to connect to an iSCSI target device, the following Error event may be logged in the System log periodically or when the computer starts:
Log Name: System
Source: iScsiPrt
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Log Name: System
Source: iScsiPrt
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
Description:
Failed to setup initiator portal. Error status is given in the dump data.
Log Name: System
Source: iScsiPrt
Event ID: 70
Task Category: None
Level: Error
Keywords: Classic
Description:
Error occurred when processing iSCSI logon request. The request was not retried. Error status is given in the dump data.
Log Name: System
Source: MSiSCSI
Event ID: 113
Task Category: None
Level: Warning
Keywords: Classic
Description:
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *xxx.xxx.xxxx.xxxx 0003260 Root\ISCSIPRT\0000_0 .
This issue may occur in all versions of Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2.
This issue occurs for one or more of the following reasons.
Cause 1
An iSCSI target device that is listed on the
Favorite Targets tab of the iSCSI Initiator is no longer accessible. This may occur if the iSCSI target device name is changed, if the IP address is changed, or if the iSCSI target device is removed from the network.
Cause 2
The iSCSI target device has reached its limit for the number of incoming connections.
Cause 3
A transient network issue temporarily prevented connectivity to the iSCSI target device.
Cause 4
The network stack is not fully prepared when the initiator was trying to connect to persistent targets. The initiator will retry to connect. When the network stack is fully prepared, connection should be successfully established.
If you receive this error when the iSCSI target device that is listed on the
Favorite Targets tab no longer exists, you can resolve this issue by removing the iSCSI target device from the list of favorite targets.
If you receive this error, and you cannot access an iSCSI target device that is still configured on the network, make sure that the client computer has network connectivity to the iSCSI target and make sure that name resolution is working correctly.
If you have successfully connected to your iSCSI target device despite this error, it indicates that the connectivity issue was temporary. Therefore, you can safely ignore this Error event.
APPLIES TO
- Windows Vista Home Basic
- Windows Vista Home Premium
- Windows Vista Business
- Windows Vista Enterprise
- Windows Vista Ultimate
- Windows Vista Home Basic 64-bit Edition
- Windows Vista Home Premium 64-bit Edition
- Windows Vista Enterprise 64-bit Edition
- Windows Vista Ultimate 64-bit Edition
- Windows Vista Business 64-bit Edition
- Windows Server 2008 Standard
- Windows Server 2008 Enterprise
- Windows Server 2008 Datacenter
- Windows 7 Enterprise
- Windows 7 Home Basic
- Windows 7 Home Premium
- Windows 7 Professional
- Windows 7 Starter
- Windows 7 Ultimate
- Windows Server 2008 R2 Standard
- Windows Server 2008 R2 Enterprise
| kbexpertiseinter kbtshoot kbsurveynew kbprb KB972107 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please