Error when you run the Best Practices Analyzer tool on a computer that is set to the Japanese system locale in Windows Server 2012

Symptoms

Consider the following scenario:

  • You have a computer that is running Windows Server 2012.

  • The system locale setting of the computer is set to Japanese.

  • You install the Network Policy and Access Services (NPAS) server role with default settings on the computer.

  • You try to run the Best Practices Analyzer tool to scan Network Access Protection (NAP) components.

In this scenario, the scan fails. Additionally, you receive an error message that resembles the following:

Cannot convert value "System.Object[]" to type "System.Xml.XmlDocument". Error: "'<', hexadecimal value 0x3C, is an invalid attribute character. Line 21, position 8."


Notes

  • This issue also occurs when the system locale is set to a language that uses Unicode characters.

  • When you install the NPAS server role by using default settings in Windows Server 2012, only the Network Policy Server role service is installed.

Cause

This issue occurs because UTF-8 encoding is not specified during the reading process of the XML files that are related to the Best Practices Analyzer scan.

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 Server 2012. Additionally, you must have the NPAS server role installed.

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 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 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 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 x64-based versions of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Manifest.psd1

Not applicable

648

02-Jun-2012

14:34

Not applicable

Npas.ps1

Not applicable

98,864

04-Dec-2012

23:17

Not applicable

Npas.sch

Not applicable

12,420

02-Jun-2012

14:34

Not applicable

Npas.xsd

Not applicable

2,373

02-Jun-2012

14:34

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, 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

Additional file information for Windows Server 2012

File name

Amd64_db048b8c21dce421ec306a67d7d00db7_31bf3856ad364e35_6.2.9200.20576_none_2cfe480e7700a926.manifest

File version

Not applicable

File size

700

Date (UTC)

05-Dec-2012

Time (UTC)

14:36

Platform

Not applicable

File name

Amd64_microsoft-windows-npas-bpa_31bf3856ad364e35_6.2.9200.20576_none_1ad1087dc905a33d.manifest

File version

Not applicable

File size

5,652

Date (UTC)

05-Dec-2012

Time (UTC)

08:05

Platform

Not applicable


Need more help?

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

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×