Microsoft Knowledge Base Email Alertz

FIX: The CLR fails with a fatal execution engine error, and a crash occurs when you run an application by using the .NET Framework 2.0 Service Pack 2

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: 963676 - Last Review: August 4, 2010 - Revision: 4.0

FIX: The CLR fails with a fatal execution engine error, and a crash occurs when you run an application by using the .NET Framework 2.0 Service Pack 2

On This Page

SYMPTOMS

The common language runtime (CLR) fails with a fatal execution engine error, and a crash occurs when you run an application by using the Microsoft .NET Framework 2.0 Service Pack 2 (SP2). For example, this problem occurs when you start World Wide Web Publishing Service (W3SVC) on a server that is running Microsoft Exchange Server 14, and then submit requests to Exchange Web Services. When this problem occurs, you may experience the following symptoms:
  • In the Windows Event Viewer, you see a ".NET Runtime" event in the Application log that includes one or more of the following:
    • Incorrectly committed to using native image for <assembly>
    • COR_E_EXECUTIONENGINE
    • 0x80131506
  • When Fusion logging is turned on, the last Fusion log that is generated in the default category contains the following information at the end of the log:
    LOG: Found assembly by looking in the GAC.
    LOG: Binding succeeds. Returns assembly from <path of assembly>.
    LOG: Assembly is loaded in <LoadFrom or default> load context.
  • When you run the application under the Windows Debugger before the crash, you find that the CLR writes the following message to the debugger:
    Rejecting native image because dependency is not native.

CAUSE

If an assembly that has a native image in the global assembly cache (GAC) is loaded as a dependent bind of an assembly through the LoadFrom method for the first time, Fusion logging will correctly find the assembly. The native image is never returned to the caller, although it is recorded in the load context.

RESOLUTION

Hotfix Replacement Information

The hotfix that corresponds to KB963676 has been superseded with the hotfix KB981574, which contains all fixes that were previously included in KB963676. You should use the hotfix KB981574 to fix the issues described in KB963676. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981574  (http://kbalertz.com/Feedback.aspx?kbNumber=981574/ ) The splash screen stays open longer than usual when you try to start Excel on a computer that has the .NET Framework 3.5 SP1 installed

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

How to view Event Viewer in Windows Vista

  1. Click Start, and then click Control Panel.
  2. Double-click Administrative Tools, and then double-click Event Viewer.

    Note To open Event Viewer, you can also click Start, type eventvwr.exe in the search box, and then double-click Event Viewer under Programs.
  3. In the console tree, expand Windows Logs, and then select Application.
  4. In the details pane, double-click the event that you want to view.

How to turn on Fusion logging

  1. Start a Microsoft Visual Studio 2008 command prompt in Administrator mode.
  2. Type fuslogvw.exe, and then press ENTER.
  3. Click on Settings, and then click the Log all binds to disk option button.
 

APPLIES TO
  • Microsoft .NET Framework 2.0 Service Pack 2
  • Microsoft .NET Framework 3.5 Service Pack 1
  • Microsoft Visual Studio 2008 Service Pack 1
Keywords: 
kbhotfixserver kbexpertiseadvanced kbqfe kbsurveynew KB963676
       

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