By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,573 Members | 1,752 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,573 IT Pros & Developers. It's quick & easy.

system.dll error

P: n/a
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

Nov 20 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Cor
Hi John,
Can you send a piece of code?
Maybe someone can help you then.
I think this is searching in the dark.
Cor
Nov 20 '05 #2

P: n/a
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
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:#Z**************@TK2MSFTNGP09.phx.gbl...
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

Nov 20 '05 #3

P: n/a
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
"Tom Spink" <th**********@ntlworld.com> wrote in message
news:u%****************@TK2MSFTNGP10.phx.gbl...
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
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:#Z**************@TK2MSFTNGP09.phx.gbl...
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


Nov 20 '05 #4

P: n/a
* "John" <jo**@nospam.infovis.co.uk> scripsit:
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.


<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>

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>
Nov 20 '05 #5

P: n/a
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
Nov 20 '05 #6

P: n/a
Should I reinstall vs.net 2003?

Regards

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:bm************@ID-208219.news.uni-berlin.de...
* "John" <jo**@nospam.infovis.co.uk> scripsit:
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.
<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>

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>

Nov 20 '05 #7

P: n/a
* "John" <jo**@nospam.infovis.co.uk> scripsit:
Should I reinstall vs.net 2003?


I think this won't help, but I am not sure...

:->

--
Herfried K. Wagner
MVP · VB Classic, VB.NET
<http://www.mvps.org/dotnet>
Nov 20 '05 #8

P: n/a
Thanks Fergus. Helpful as always.

I will try these.

Regards

"Fergus Cooney" <fi******@tesco.net> wrote in message
news:ey**************@tk2msftngp13.phx.gbl...
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

Nov 20 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.