FIX: The Failed Request Tracing log file is missing entries in IIS 8.0

Applies To
Internet Information Services 8.0

Symptoms

When you use the Failed Request Tracing module on a server that is running Internet Information Services (IIS) 8.0 in Windows 8 or Windows Server 2012, you find that some entries are missing in the Compact View section of the Failed Request Tracing log file. For example, the first event that is logged in the Failed Request Tracing log file should be the GENERAL_REQUEST_START event. However, in this case, you find that the log file starts with NOTIFY_MODULE_END, as shown in the following example:

NOTIFY_MODULE_END ModuleName="FailedRequestsTracingModule", Notification="BEGIN_REQUEST", fIsPostNotificationEvent="false", NotificationStatus="NOTIFICATION_CONTINUE" 17:13:11.269
NOTIFY_MODULE_START ModuleName="IsapiFilterModule", Notification="AUTHENTICATE_REQUEST", fIsPostNotification="false" 17:13:11.269
NOTIFY_MODULE_END ModuleName="IsapiFilterModule", Notification="AUTHENTICATE_REQUEST", fIsPostNotificationEvent="false", NotificationStatus="NOTIFICATION_CONTINUE" 17:13:11.269
You would expect that the Failed Request Tracing log file would start with the GENERAL_REQUEST_START event, as shown in the following example:

GENERAL_REQUEST_START SiteId="1", AppPoolId="DefaultAppPool", ConnId="1610612743", RawConnId="0", RequestURL="http:⁠//localhost/iisstart.Htm", RequestVerb="GET

Resolution

This hotfix is also available at Microsoft Update Catalog

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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, go to the following Microsoft website:

http:⁠//support.microsoft.com/contactus/?ws=support Note 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

You must have IIS 8.0 installed on a computer that is running Windows 8 or Windows Server 2012.

Restart information

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

Replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows 8 and Windows Server 2012 file information notesImportant Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" 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, 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
    8.0.920 0.20 xxx Windows 8 and Windows Server 2012 RTM 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 8 and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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.

For all supported x86-based versions of Windows 8

File name File version File size Date Time Platform
Iisfreb.dll 8.0.9200.20685 154,624 11-Apr-2013 04:39 x86
W3core.mof Not Applicable 143,858 25-Jul-2012 20:18 Not Applicable
W3isapi.mof Not Applicable 2,560 25-Jul-2012 20:16 Not Applicable

For all supported x64-based versions of Windows 8 and Windows Server 2012

File name File version File size Date Time Platform
Iisfreb.dll 8.0.9200.20685 163,840 10-Apr-2013 22:33 x64
W3core.mof Not Applicable 143,858 25-Jul-2012 20:16 Not applicable
W3isapi.mof Not Applicable 2,560 25-Jul-2012 20:14 Not applicable
Iisfreb.dll 8.0.9200.20685 154,624 11-Apr-2013 04:39 x86
W3core.mof Not Applicable 143,858 25-Jul-2012 20:18 Not applicable
W3isapi.mof Not Applicable 2,560 25-Jul-2012 20:16 Not applicable

      

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, see Description of the standard terminology that is used to describe Microsoft software updates .

Additional file information

Additional file information for Windows 8 and for Windows Server 2012

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

File name X86_f612ceff1f1d7bc825ddb98eefd6bc7b_31bf3856ad364e35_6.2.9200.20685_none_b68ee3d062dc7ffe.manifest
File version Not applicable
File size 711
Date (UTC) 11-Apr-2013
Time (UTC) 16:07
Platform Not applicable
File name X86_microsoft-windows-i..httptracingbinaries_31bf3856ad364e35_6.2.9200.20685_none_2cbc954b057532e7.manifest
File version Not applicable
File size 6,242
Date (UTC) 11-Apr-2013
Time (UTC) 16:07
Platform Not applicable

Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012

File name Amd64_9077bb6791e6099b72362914b08db78c_31bf3856ad364e35_6.2.9200.20685_none_9dbaa608ce6ccd76.manifest
File version Not applicable
File size 1,072
Date (UTC) 11-Apr-2013
Time (UTC) 15:44
Platform Not applicable
File name Amd64_microsoft-windows-i..httptracingbinaries_31bf3856ad364e35_6.2.9200.20685_none_88db30cebdd2a41d.manifest
File version Not applicable
File size 6,248
Date (UTC) 11-Apr-2013
Time (UTC) 15:44
Platform Not applicable
File name Wow64_microsoft-windows-i..httptracingbinaries_31bf3856ad364e35_6.2.9200.20685_none_932fdb20f2336618.manifest
File version Not applicable
File size 6,051
Date (UTC) 11-Apr-2013
Time (UTC) 15:44
Platform Not applicable