Microsoft Knowledge Base Email Alertz

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:

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 303715 - Last Review: February 23, 2007 - Revision: 4.7

BUG: The NET Framework Configuration tool does not localize strings

This article was previously published under Q303715

On This Page

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.

APPLIES TO
  • Microsoft .NET Framework 1.1
  • Microsoft .NET Framework 1.0
  • Microsoft Visual Studio .NET 2003 Enterprise Architect
  • Microsoft Visual Studio .NET 2003 Enterprise Developer
  • Microsoft Visual Studio .NET 2003 Academic Edition
  • Microsoft Visual Studio .NET 2002 Professional Edition
  • Microsoft Visual Studio .NET 2002 Enterprise Architect
  • Microsoft Visual Studio .NET 2002 Enterprise Developer
  • 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
Keywords: 
kbvs2002sp1sweep kbbug kbpending KB303715
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate