BUG: The NET Framework Configuration tool does not localize strings (303715)



The information in this article applies to:

  • Microsoft .NET Framework 1.1
  • Microsoft .NET Framework 1.0
  • Microsoft Visual Studio .NET (2003), Enterprise Architect Edition
  • Microsoft Visual Studio .NET (2003), Enterprise Developer Edition
  • Microsoft Visual Studio .NET (2003), Academic Edition
  • Microsoft Visual Studio .NET (2002), Professional Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
  • Microsoft Visual Studio .NET (2002), Academic Edition
  • Microsoft Common Language Runtime (included with the .NET Framework 1.1)
  • Microsoft Common Language Runtime (included with the .NET Framework) 1.0
  • Microsoft .NET Framework Class Libraries 1.1
  • Microsoft .NET Framework Class Libraries 1.0

This article was previously published under Q303715

SYMPTOMS

When you run a non-English language version of the Microsoft .NET Framework Configuration tool (Mscorcfg.msc), many of the strings are not localized. The resource lookup fails, and a string that is similar to following may appear:
[Resource lookup failed - infinite recursion detected. Resource name: Policy_AllCode_Name]

CAUSE

This problem occurs because of security loading problems. As a result, the security system cannot obtain managed resources in some cases, and you receive an error message in English.

The .NET Framework Configuration tool and the Code Access Security Policy tool (Caspol.exe) use security manager application programming interfaces (APIs) internally. Because of a bug in the product, these APIs fail when a Security.config file does not exist on the system (which is the default for non-English operating systems).

If .NET Framework is installed as part of Visual Studio .NET, this problem does not occur because the Security.config file exists.

RESOLUTION

Before you run the tool, run the following command from a command prompt:

caspol -all -reset

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Start the Microsoft .NET Framework Configuration tool.
  2. Click to expand the My Computer, the Runtime Security Policy, the Machine, and the Code Group nodes.

Modification Type:MinorLast Reviewed:9/15/2005
Keywords:kbvs2002sp1sweep kbbug kbpending KB303715