system.dll error

  • Thread starter Thread starter John
  • Start date Start date
J

John

Hi

I am getting this error when running a project;

An unhandled exception of type 'System.ExecutionEngineException' occurred in
system.dll

What can I do to fix this problem? Using vs.net 2003, framework 1.1 sp2.

Thanks

Regards
 
Hi John,
Can you send a piece of code?
Maybe someone can help you then.
I think this is searching in the dark.
Cor
 
Where are you running the assembly from? Your hard-drive, or a network
share?

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

" System.Reflection Master "

==== Converting to 2002 ====
Remove inline declarations
 
Well the tricky bit is that the same code runs fine on one partition. Now
because I need to target my code to ol2000 and above I used another
partition to install vs.net 2003 and ol2000 (i have ol2002 on my main
partition) so I can generate the necessary ol2000 interop assemblies. It is
this second partition that I am getting the error on. Both partitions seem
to have the same setup for vs; vs.net 2003, framework 1.1 sp2. The only
difference appears to be ol2002 on main partition (where it runs correctly)
and ol2000 where it does not run correctly.

Thanks

Regards
 
* "John said:
I am getting this error when running a project;

An unhandled exception of type 'System.ExecutionEngineException' occurred in
system.dll

What can I do to fix this problem? Using vs.net 2003, framework 1.1 sp2.
Click to expand...

<msdn>
Execution engine errors are fatal errors that should never occur. Such errors occur mainly when the execution engine has been corrupted or data is missing. The system can throw this exception at any time. When possible, the system throws an exception that provides more information than the ExecutionEngineException exception.
</msdn>
 
Hi John,

You went the two partitions route. :-)

WIth such little information it's hard to know what the error might be. As
Herfried reports, that is a general "I just can't cope!" error. It arose not
long ago in the context of ActiveX controls, for instance.

The culprit could be VB, OL or the combination.

Some lines to investigate:
Do normal VB projects run?
Can you access the other apps in Office 2000?
Can you access OL using the similar code but from a script (for
instance, TestOL.vbs)?
Can you do anything at all with OL from VB?

Finally, at what point, exactly, does the error occur?

I can't say I'll be able to give you an answer, but this may narrow it
down.

Regards,
Fergus
 
Should I reinstall vs.net 2003?

Regards

Herfried K. Wagner said:
<msdn>
Execution engine errors are fatal errors that should never occur. Such
Click to expand...
errors occur mainly when the execution engine has been corrupted or data is
missing. The system can throw this exception at any time. When possible, the
system throws an exception that provides more information than the
ExecutionEngineException exception.
 
Back
Top