Fatal Execution Engine Error after COM+ call: Possible CLR bug


hi,

 

we have just faced odd problem our .net 2.0 windows service application , haven't find solution far. unknown reason .net 2.0 framework crashes after com+ client-side call and our windows service fails start everytime because of that. the event log contains following error messages (two):

 

source: .net runtime

description: .net runtime version 2.0.50727.832 - fatal execution engine error (7a0592a2) (80131506)

 

source: .net runtime 2.0 error

description: faulting application serveritsekkeri.exe, version 1.0.0.0, stamp 479df12e, faulting module mscorwks.dll, version 2.0.50727.832, stamp 461f2e2a, debug? 0, fault address 0x000c63bf

 

the crashing has been detected on our customer server (windows server 2003 standard edition sp2 32 bit running on the xeon 5130 processor (multi-core)). odd reason our application works without problems on our test server (windows server 2003 standard edition sp2 32 bit running on celeron processor (single-core) or development machine (windows xp professional sp2 32 bit, pentium 4 2,4 ghz (single-core)).

 

after googling on problem found lot of people getting same "fatal execution engine error" .net 2.0 application. found a hot fix (kb913384) relating problem from microsoft ( http://support.microsoft.com/kb/913384 ) didn't help. had solved problem by deleting current user account profile (possible corrupted one) , creating new one (according kb913384 problem caused by a user account without profile). i removed security updates in case of buggy update no luck.

 

finally found interesting bug report relating samekind of problem:

 

fatal execution engine error using method returning matrix if component in com+ application on x64 machine

https://connect.microsoft.com/visualstudio/feedback/viewfeedback.aspx?feedbackid=291290&wa=wsignin1.0 

according report bug detected on computer running on xeon multi-core processor , clr bug. bug has been closed (fixed) possible have found again in own situation? possible there clr bug shows on xeon multi core processors when executing com+ calls?

 

our application acts com+ client-side , works timer application timed checks com+ server-side. server-side has been developed delphi 7 , using .delphi 8 .net wrapper classes in our .net 2.0 application for com+ client-side calls. combination has worked great many of our .net 2.0 applications until found odd behaviour between the .net 2.0 framework/clr , xeon processor??? smile

 

so guys, me 1 avoid crashing , make com+ calls working on xeon server? don't think there wrong code since works charm on other computers.

 

i grateful help.

 

thanks

 

juha 

 

 

 

 



.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