Fatal Execution Engine Error 0x7924d8e6
Contents |
360 games PC games
Fatal Execution Engine Error 80131506
Windows games Windows phone games Entertainment All Entertainment .net runtime fatal execution engine error Movies & TV Music Business & Education Business Students & educators
.net Runtime Fatal Execution Engine Error 80131506
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet .net runtime version 2.0.50727.5485 - fatal execution engine error Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All kb981574 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 17:22:27 GMT by s_wx1131 (squid/3.5.20)
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about http://stackoverflow.com/questions/1205111/how-do-i-debug-a-net-fatal-execution-engine-error hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How do I debug a .net Fatal Execution Engine Error? up vote 5 down vote favorite 2 As a developer, I'm trying to setup a development environment on our brand new fatal execution VMWare ESX server. Things are not working out: somewhere during the SharePoint Product & Technologies Configuration Wizard, the application just disappears, and in the event log I find the following error: .NET Runtime version 2.0.50727.3082 - Fatal Execution Engine Error (7A0979C6) (80131506) Now I know all this sounds suspiciously like a ServerFault.com style problem (and a very generic error message, lots of similar hits on google), and of course we are addressing the issue in such a way fatal execution engine (installing/uninstalling service packs/hotfixes, different os versions, testing individual elements of the install, different settings for the vm, etc), but out of personal interest I'd like to gain a bit more understanding about the issue then "install hotfix XXYY and hope it goes away". I was wondering: How do I approach this error from a coders perspective? Can I somehow make a debugger stop when this issue occurs, or manually point it to the reported address (in what module)? Should I try and install use Visual Studio for this, or use lowlevel tools like windbg? What are these error codes exactly? The latter looks like a com error. Is the other one an address? Can I somehow turn on more detailed error reporting? A faulting .dll would be nice. You can tell I am not at all experienced in debugging at this level in a .net environment, but I am very much willing to learn. Any pointers are most welcome! p.s. When I try to run the command-line configuration tool psconfig to do a non-UI configuration, most if not all commands trigger a StackOverflowException. Again, where do I go from there? sharepoint debugging com share|improve this question asked Jul 30 '09 at 8:06 Paul-Jan 11.3k3165 I believe 80131506 is the internal error code for FEEE –Brian Rasmussen Jul 30 '09 at 8:11 You should get good details about the fault i