Monday, October 17, 2022

A hotfix that logs an event for the errors that are resulted from dropped frames or dropped requests in Windows 7 or Windows Server 2008 R2 is available [MS]

Introduction

This article describes a hotfix that logs an event for the errors that originate from dropped frames or dropped requests on a Fibre Channel (FC) network. After you install the hotfix, an event is logged to record the retry that was performed. The following event is logged in the event log when the dropped frames or the dropped requests are retried: Note When there is a congestion or connection issue in the FC, the following two hardware errors are generated in the event log:

INITIATOR RESPONSE TIMEOUT

TIMEOUT ON LOGICAL UNIT

If the system receives one of these I/O errors, the system silently retries. Because there is no indication of the retry activity, when an application becomes unresponsive during this time, users may misinterpret that as a system freeze. Additionally, in the Microsoft Multipath I/O (MPIO) configuration, the failover operation does not start.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain 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 do not 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 do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 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 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (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.1.760
    1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Classpnp.sys

6.1.7601.22269

141,656

27-Feb-2013

04:29

x86

Iologmsg.dll

6.1.7601.22269

2,048

27-Feb-2013

04:22

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Classpnp.sys

6.1.7601.22269

180,584

27-Feb-2013

05:25

x64

Iologmsg.dll

6.1.7601.22269

2,048

27-Feb-2013

05:18

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Classpnp.sys

6.1.7601.22269

378,216

27-Feb-2013

04:33

IA-64

Iologmsg.dll

6.1.7601.22269

2,048

27-Feb-2013

04:26

IA-64


Status

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

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

X86_microsoft-windows-classpnp_31bf3856ad364e35_6.1.7601.22269_none_17e308c82395bd84.manifest

File version

Not applicable

File size

12,448

Date (UTC)

27-Feb-2013

Time (UTC)

04:56

Platform

Not applicable

File name

X86_microsoft-windows-iologgingdll_31bf3856ad364e35_6.1.7601.22269_none_b93de05973ead173.manifest

File version

Not applicable

File size

2,648

Date (UTC)

27-Feb-2013

Time (UTC)

04:55

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_microsoft-windows-classpnp_31bf3856ad364e35_6.1.7601.22269_none_7401a44bdbf32eba.manifest

File version

Not applicable

File size

12,450

Date (UTC)

27-Feb-2013

Time (UTC)

06:20

Platform

Not applicable

File name

Amd64_microsoft-windows-iologgingdll_31bf3856ad364e35_6.1.7601.22269_none_155c7bdd2c4842a9.manifest

File version

Not applicable

File size

2,652

Date (UTC)

27-Feb-2013

Time (UTC)

06:18

Platform

Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_microsoft-windows-classpnp_31bf3856ad364e35_6.1.7601.22269_none_17e4acbe2393c680.manifest

File version

Not applicable

File size

12,449

Date (UTC)

27-Feb-2013

Time (UTC)

04:57

Platform

Not applicable

File name

Ia64_microsoft-windows-iologgingdll_31bf3856ad364e35_6.1.7601.22269_none_b93f844f73e8da6f.manifest

File version

Not applicable

File size

2,650

Date (UTC)

27-Feb-2013

Time (UTC)

04:56

Platform

Not applicable


No comments:

Post a Comment

Search This Blog

Authentication loop between msft.sts.microsoft.com/adfs and OWA in Exchange Server 2019 and 2016 - Microsoft Support [MS]

Authentication loop between msft.sts.microsoft.com/adfs and OWA in Exchange Server 2019 and ...