468,103 Members | 1,211 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,103 developers. It's quick & easy.

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

If I run my program on another machine I get the following error

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

This happens with I try to open an OleDb.OleDbConnection

What is causing this?

Also the normal Try Catch block doesn't catch this error, I had to use the
CLR debugger to get the error.

Thanks.
Mar 5 '07 #1
3 11285
In article <O$**************@TK2MSFTNGP03.phx.gbl>,
ss*****@nospam.nospam says...
If I run my program on another machine I get the following error

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

This happens with I try to open an OleDb.OleDbConnection

What is causing this?
Wow. That's a nasty one. I would re-install the .NET runtime and make
sure both machines are running the same version (including service
packs).
Also the normal Try Catch block doesn't catch this error, I had to use the
CLR debugger to get the error.
I think there are (at least in 1.x) four exceptions that are so "bad",
they can't be caught. The runtime is so corrupt, it can't do proper
stack unwinding to process the exception.
System.ExecutionEngineException is one of them.

--
Patrick Steele
http://weblogs.asp.net/psteele
Mar 6 '07 #2
Thanks for the reply. How do I go about reinstalling the .Net runtime?
"Patrick Steele" <pa*****@mvps.orgwrote in message
news:MP************************@msnews.microsoft.c om...
In article <O$**************@TK2MSFTNGP03.phx.gbl>,
ss*****@nospam.nospam says...
>If I run my program on another machine I get the following error

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

This happens with I try to open an OleDb.OleDbConnection

What is causing this?

Wow. That's a nasty one. I would re-install the .NET runtime and make
sure both machines are running the same version (including service
packs).
>Also the normal Try Catch block doesn't catch this error, I had to use
the
CLR debugger to get the error.

I think there are (at least in 1.x) four exceptions that are so "bad",
they can't be caught. The runtime is so corrupt, it can't do proper
stack unwinding to process the exception.
System.ExecutionEngineException is one of them.

--
Patrick Steele
http://weblogs.asp.net/psteele

Mar 6 '07 #3
Figured it out thanks to Patrick's advice

From KB 908077, I did the following and it works now.

Repair the .NET Framework 2.0
The following are three ways to repair the .NET Framework.
Use the Repair command on the Windows Installer cache file
To repair the .NET Framework 2.0 by using the Windows Installer cache file,
follow these steps:1. Click Start, click Run, type installer in the Open
box, and then click OK.
2. On the View menu in Windows Installer, click Details, right-click
the Name column header, and then click Comment.
3. Right-click the cached Windows Installer file that has the
Microsoft .NET Framework 2.0 RTL x86 enu comment, and then click Repair.
4. After the repair process has completed, quit Windows Installer.

"Patrick Steele" <pa*****@mvps.orgwrote in message
news:MP************************@msnews.microsoft.c om...
In article <O$**************@TK2MSFTNGP03.phx.gbl>,
ss*****@nospam.nospam says...
>If I run my program on another machine I get the following error

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

This happens with I try to open an OleDb.OleDbConnection

What is causing this?

Wow. That's a nasty one. I would re-install the .NET runtime and make
sure both machines are running the same version (including service
packs).
>Also the normal Try Catch block doesn't catch this error, I had to use
the
CLR debugger to get the error.

I think there are (at least in 1.x) four exceptions that are so "bad",
they can't be caught. The runtime is so corrupt, it can't do proper
stack unwinding to process the exception.
System.ExecutionEngineException is one of them.

--
Patrick Steele
http://weblogs.asp.net/psteele

Mar 6 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Professor Frink | last post: by
reply views Thread by NicK chlam via DotNetMonster.com | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.