Symptoms

On a computer that is running Windows 8 or Windows Server 2012, non-English site names are not displayed in the "s-sitename" field in an Internet Information Services (IIS) log file.

For example, consider the following scenario:

  • You create a site by using multibyte, non-English characters.

  • In the Applicationhost.config file, you set the site "logSiteId" setting to "false." For example, the configuration in the Applicationhost.config file resembles the following:

    <site name="site name" id="2"> 
    <application path="/" applicationPool="site name">
    <virtualDirectory path="/" physicalPath="C:\inetpub\wwwroot" />
    </application>
    <bindings>
    <binding protocol="http" bindingInformation="*:8080:" />
    </bindings>
    <logFile logSiteId="false" />
    </site>
  • You send an HTTP request to the site.

  • You open an IIS log file to view the "s-sitename" field.

In this scenario, the site name is an unrecognizable string.

Cause

This issue occurs because the Http.sys file cannot handle non-English site names. The Http.sys file is given a Char string instead of a WCHAR string.

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 this specific problem.

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, submit a request to 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 8 or Windows Server 2012.

Registry information

To use the hotfix in this package, 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 8 and Windows Server 2012 file information notesImportant Windows 8 hotfixes 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

    6.2.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

Loghttp.dll

8.0.9200.20777

15,872

18-Jul-2013

04:13

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

File name

File version

File size

Date

Time

Loghttp.dll

8.0.9200.20777

19,456

18-Jul-2013

10:35




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:

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

Additional file information for Windows 8 and Windows Server 2012

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

File name

File version

File size

Date

Time

X86_49aeceb66df8d0cf9d4cf047bc722ddd_31bf3856ad364e35_6.2.9200.20777_none_611b1f64ec6c9cbc.manifest

Not applicable

711

18-Jul-2013

18:16

X86_microsoft-windows-i..httploggingbinaries_31bf3856ad364e35_6.2.9200.20777_none_795c11fb1ef7ec40.manifest

Not applicable

3,037

18-Jul-2013

05:02

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

File name

File version

File size

Date

Time

Amd64_700329bda86a3ff4d0d439e07ed16ac1_31bf3856ad364e35_6.2.9200.20777_none_1545cbe12ece604c.manifest

Not applicable

1,072

18-Jul-2013

18:17

Amd64_microsoft-windows-i..httploggingbinaries_31bf3856ad364e35_6.2.9200.20777_none_d57aad7ed7555d76.manifest

Not applicable

3,043

18-Jul-2013

11:31


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!

×