Mini Kabibi Habibi

Current Path : C:/Windows/System32/DriverStore/FileRepository/iscsi.inf_amd64_260e9b4b7d61bc83/
Upload File :
Current File : C:/Windows/System32/DriverStore/FileRepository/iscsi.inf_amd64_260e9b4b7d61bc83/iscsilog.dll

MZ����@���	�!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEd���E�" @�


`�'`A 8=T.rdata�@@.rsrc8= >@@��E
TTT��E$����E��T.rdataT|.rdata$zzzdbg �.rsrc$01� H<.rsrc$02 >�m����Jc��>L_ڎ�Z����S@�s��E��(�@�X�p�����	�	�	�p\��$�7� �MUI�4VS_VERSION_INFO��
4aJ
4aJ?StringFileInfo�040904B0LCompanyNameMicrosoft CorporationPFileDescriptioniSCSI Event Log DLLn'FileVersion10.0.19041.3636 (WinBuild.160101.0800)HInternalNameiSCSI Event Log DLL�.LegalCopyright� Microsoft Corporation. All rights reserved.POriginalFilenameiSCSI Event Log DLLj%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.19041.3636DVarFileInfo$Translation	� @ @�"@"@L@@@@TC@C@�G@G@���x!�!�(#�?��A�B�83D�F�L4H�H�$7�Initiator received an asynchronous logout message. The Target name is given in the dump data.

A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.

xAttempt to bootstrap Windows using iSCSI NIC Boot (iBF)

�If Digest support selected for iSCSI Session, Will use Processor support for Digest computation.

�Initiator did not start a session recovery upon receiving the request. Dump data contains the error status.

�Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.

�The initiator could not allocate resources for an iSCSI session.

�Maximum command sequence number is not serially greater than expected command sequence number in login response.

Dump data contains Expected Command Sequence number followed by Maximum Command Sequence number.

MaxBurstLength is not serially greater than FirstBurstLength.

Dump data contains FirstBurstLength followed by MaxBurstLength.

�Failed to setup initiator portal. Error status is given in the dump data.

�The initiator could not allocate resources for an iSCSI connection

�The initiator could not send an iSCSI PDU. Error status is given in the dump data.

�Target or discovery service did not respond in time for an iSCSI request sent by the initiator. 

iSCSI Function code is given in the dump data. For details about iSCSI Function code please refer 

to iSCSI User's Guide.

�Target did not respond in time for a SCSI request. The CDB is given in the dump data.

�Login request failed. The login response packet is given in the dump data.

�Target returned an invalid login response packet. The login response packet is given in the dump data.

�Target provided invalid data for login redirect. Dump data contains the data returned by the target.

�Target offered an unknown AuthMethod. Dump data contains the data returned by the target.

�Target offered an unknown digest algorithm for CHAP. Dump data contains the data returned by the target.

�CHAP challenge given by the target contains invalid characters. Dump data contains the challenge given.

�An invalid key was received during CHAP negotiation. The key=value pair is given in the dump data.

�CHAP Response given by the target did not match the expected one. Dump data contains the CHAP response.

�Header Digest is required by the initiator, but target did not offer it.

�Data Digest is required by the initiator, but target did not offer it.

�Connection to the target was lost. The initiator will attempt to retry the connection.

�Data Segment Length given in the header exceeds MaxRecvDataSegmentLength declared by the target.

�Header digest error was detected for the given PDU. Dump data contains the header and digest.

�Target sent an invalid iSCSI PDU. Dump data contains the entire iSCSI header.

�Target sent an iSCSI PDU with an invalid opcode. Dump data contains the entire iSCSI header.

�Data digest error was detected. Dump data contains the calculated checksum followed by the given checksum.

�Target trying to send more data than requested by the initiator.

Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iSCSI header.

�Initiator received an invalid R2T packet. Dump data contains the entire iSCSI header.

�Target rejected an iSCSI PDU sent by the initiator. Dump data contains the rejected PDU.

�Initiator could not allocate a workitem for processing a request.

�Initiator could not allocate resource for processing a request.

�Challenge size given by the target exceeds the maximum specified in iSCSI specification.

�Target CHAP secret is smaller than the minimum size (12 bytes) required by the spec. 

Initiator CHAP secret is smaller than the minimum size (12 bytes) required by the spec. Dump data contains the given CHAP secret.

�FIPS service could not be initialized. Persistent logons will not be processed.

�Initiator requires CHAP for logon authentication, but target did not offer CHAP.

�Initiator sent a task management command to reset the target. The target name is given in the dump data.

�Target requires logon authentication via CHAP, but Initiator is not configured to perform CHAP.

�Target did not send AuthMethod key during security negotiation phase.

PTarget sent an invalid status sequence number for a connection. Dump data contains 

Expected Status Sequence number followed by the given status sequence number.

tTarget failed to respond in time for a login request.

xTarget failed to respond in time for a logout request.

�Target failed to respond in time for a login request. This login request was for adding a new connection to a session.

�Target failed to respond in time for a SendTargets command.

�Target failed to respond in time for a SCSI command sent through a WMI request.

pTarget failed to respond in time to a NOP request.

�Target failed to respond in time to a Task Management request.

�Target failed to respond in time to a Text Command sent to renegotiate iSCSI parameters.

�Target failed to respond in time to a logout request sent in response to an asynchronous message from the target.

�Initiator Service failed to respond in time to a request to configure IPSec resources for an iSCSI connection.

�Initiator Service failed to respond in time to a request to release IPSec resources allocated for an iSCSI connection.

�Initiator Service failed to respond in time to a request to encrypt or decrypt data.

�Initiator failed to allocate resources to send data to target.

�Initiator could not map an user virtual address to kernel virtual address resulting in I/O failure. 

�Initiator could not allocate required resources for processing a request resulting in I/O failure. 

�Initiator could not allocate a tag for processing a request resulting in I/O failure. 

�Target dropped the connection before the initiator could transition to Full Feature Phase.

�Target sent data in SCSI Response PDU instead of Data_IN PDU. Only Sense Data can be sent in SCSI Response.

�Target set DataPduInOrder to NO when initiator requested YES. Login will be failed.

�Target set DataSequenceInOrder to NO when initiator requested YES. Login will be failed.

�Can not Reset the Target or LUN. Will attempt session recovery.

�Booting from iSCSI, but Could not set any NIC in Paging Path.

�Attempt to disable the Nagle Algorithm for iSCSI connection failed.

After receiving an async logout from the target, attempt to relogin the session failed.  Error status is given in the dump data.

�Attempt to recover an unexpected terminated session failed. Error status is given in the dump data.

�Error occurred when processing iSCSI logon request. The request was not retried. Error status is given in the dump data.

�Unexpected target portal IP types. Dump data contains the expected IP type.

����=��C��A�-o�/ڋ���m�5�j������MUIMUIen-US