Fatal Execution Engine Error


visual studio 2008 closes automatically without error when create new silverlight application project. problem not occur when visual studio 2008 sp1 uninstalled , reinstalled on system. in case there no xaml intellisense , silverlight toolbar in application. on installing silverlight 3 sdk , tools, xaml intellisense cannot create new silverlight application. in cases visual studio closes when open xaml page in existing silverlight project if open source code editor. vs not crash when xaml page opened xml editor. have tried commands devenv /setup, devenv /resetskippkgs, mentioned in many posts not help. have tried uninstalling visual studio , silverlight , reinstalling them couple of times not help. os windows server 2008. not able obtain crash dump in process mentioned. in event viewer see error in .net runtime follows: 

.net runtime version 2.0.50727.3615 - fatal execution engine error (623e60b0) (80131506).

it real relief annoying problem if me out of this. thanks.

hi

have read  the thread and  inner thread provided?

he had explaned why error occured in first thread. and i find some useful information fixed solution in thread below.

http://social.msdn.microsoft.com/forums/en-us/clr/thread/40e8e7e7-d051-49b7-ba2c-509b210a9736

the 'fatal execution engine error' (80131506) pretty general , can caused many things. not sure what the exact solution is. need try more.

good luck you.

 

cookie luo[msft]
msdn community support | feedback us
get or request code sample microsoft
please remember mark replies answers if , unmark them if provide no help.



.NET Framework  >  Common Language Runtime Internals and Architecture



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more