Fatal Execution Engine Error (7A0979AE) (80131506)

[Erakna]

I have created one of the .Net applications and was testing that with the help of the Quick Test Profession. While testing that, I found that it get crashed without giving me any of the error message but when I saw the event viewer then it was showing that the problem is with the Net. The exact message that I got is as below. Please see that and tell me the possible solutions for this.

Event ID: 1023
.NET Runtime version 2.0.50727.3615 - Fatal Execution Engine Error (7A0979AE) (80131506)

[Shreevats]

I have also seen the cases like this when the problem happens subsequent to updating some patch for the .NET Framework. My suggestion to you is to verify that if your server has updated some of the patch. If you find it true then you will have to delete that patch and then restart your computer. There are more chances this time issue will be resolved. If you found that the problem is not resolved then please post back with your experience and we will guide you with some other solution.

[Villiers]

I have found on other KB article which is a patch accessible for this precise error code. I cannot say it for sure that this is definitely going to solve this problem because I have never faced the same but it looks like, you can try this and see if it can solve the problem for you. Please reply back that if it was helpful to you or not. Thank you.

http://support.microsoft.com/kb/930771/en-us

[Ronchi]

When the ordinary language runtime (CLR) begins then the CLR confirms that the user profile exists. If user profile does not subsist then an unacceptable reference (null ref) is place within the user policy cache. If user profile is made throughout policy resolution then the CLR attempts to take out the reference toward the unacceptable reference within the user policy cache and that results to crash .NET Framework. I hope that this will clear your mind for this.

[Dwarner]

I think that problem is with the Quick Test Profession software that you are trying to use to test your .Net applications and just because of that, you are getting this problem. My suggestion to you is to uninstall that from your computer and after that install it over again to see if that can solve the problem. Reinstalling will create all the new files for that and there are more possibility that the problem will be resolved after this and there is no harm to try this once and see that helps you.