This article describes an issue that occurs if you install the iSCSI Target Server role on a Windows Server 2012 R2-based computer. A hotfix is available to fix this issue. The hotfix has a prerequisite.

Symptoms

An iSCSI target returns a SCSISTAT_GOOD response instead of a SCSISTAT_BUSY response for a read or write command even though the target receives a BUSY signal from the storage appliance in Windows Server 2012 R2.

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, you must have the April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed on Windows Server 2012 R2.



Registry information

To apply this hotfix, you don't have to make any changes to the registry.



Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology that Microsoft uses to describe software updates.

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies to" section in articles to determine the actual operating system that each hotfix applies to.  

Notes

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.18xxx

    Windows Server 2012 R2

    RTM

    GDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

x64 Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Iscsitgt.dll

6.3.9600.18156

1,191,936

05-Dec-2015

14:59

x64


x64 Windows Server 2012 R2

File property

Value

File name

Amd64_c0373f7903a5802e66f515579be264d1_31bf3856ad364e35_6.3.9600.18156_none_89e7062483a0052a.manifest

File version

Not applicable

File size

719

Date (UTC)

06-Dec-2015

Time (UTC)

21:55

Platform

Not applicable

File name

Amd64_microsoft-windows-i..get-service-service_31bf3856ad364e35_6.3.9600.18156_none_3c3c076f8e0488a5.manifest

File version

Not applicable

File size

103,756

Date (UTC)

05-Dec-2015

Time (UTC)

15:45

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,598

Date (UTC)

06-Dec-2015

Time (UTC)

21:55

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×