Error running .NET applications

  • Thread starter Thread starter Luke Wright
  • Start date Start date
L

Luke Wright

Hi,

We are experiencing a problem where any .NET (2.0) application run on a
particular machine causes a crash. We see the following two messages in the
Application event log:

'.NET Runtime version 2.0.50727.832 - Fatal Execution Engine Error
(7A0592A2) (80131506)'

'Faulting application dfsvc.exe, version 2.0.50727.1433, stamp 471ebf7e,
faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ef729, debug?
0, fault address 0x000dff9d.'

Our main application is a clickonce application. When the user clicks on a
link to launch it, they get the message 'dfsvc.exe has encountered a problem
and needs to close...'. I tried launching 3 very simple ClickOnce
applications, one unsigned, one signed, and one signed and configured to
install. All three failed. Then I tried running two very simple .NET
applications directly on the machine (not clickonce), one console
application, one WinForms application. Both failed with similar error
messages.

The user has tried completely uninstalling all versions of the Framework and
reinstalling 2.0, but that did not correct the problem. So, apparently,
something seems to have corrupted the .NET environment such that even
removing and installing the framework doesn't fix it.

Any ideas?

Thanks,

Luke Wright
Projector PSA, Inc.
 
Luke said:
We are experiencing a problem where any .NET (2.0) application run on a
particular machine causes a crash. We see the following two messages in the
Application event log:

'.NET Runtime version 2.0.50727.832 - Fatal Execution Engine Error
(7A0592A2) (80131506)'

'Faulting application dfsvc.exe, version 2.0.50727.1433, stamp 471ebf7e,
faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ef729, debug?
0, fault address 0x000dff9d.'
Click to expand...
Both failed with similar error messages.
Click to expand...

Similar how? In particular, is the crash location (mscorkws.dll, 0x000dff9d)
consistent or does it vary?

Does the System event log include any "interesting" error messages that
might, for example, indicate hardware problems? Is the machine running
particularly aggressive anti-virus software or other software that installs
deep hooks?

One small test you could do is run PEVerify (from the .NET or Windows SDKs)
on the executables, both from the development and from the crashing machine.
The crash you're reporting is occurring in
mscorwks!PEImage::GetEntryPointToken (specifically,
mscorwks!PEDecoder::GetCorHeader is returning a bad pointer), which suggests
some sort of problem reading the executables. However, if the crash location
varies, this doesn't mean a lot and it could just as well be a HW problem.

When all's said and done, the error you're seeing is an internal CLR error,
which means Microsoft Support is best qualified to solve your problem.
 
Back
Top