.NET Runtime 2.0 Error

[James Lamanna]

Hi,
A couple of users have been getting this same .NET Runtime 2.0 error
from an app that I have written, and I haven't been able to diagnose
or debug the problem:

Faulting application.....faulting module kernel32.dll version
5.1.2600.3119 stamp 46239bd5 debug? 0, fault address 0x00012a5b.

Any help would be greatly appreciated.

Thanks.

-- James

 

[Kerem Gümrükcü]

Hi James,

without a callstack, some code and knowing what
is going on there before this instruction at this address
has been executed, it is impossible to tell what this
error exactly means. You need to attach a debugger
at this point and go down the callstack to see what
instruction/operation made this "fault" exception appear,...

Do you Pinvoke, read/write to raw app memory? Do
you have any native code pinvoking from .NET? Do
you use hooking methods? We need more Information
about your application,...


Regards

Kerem

--

 

[Michael Nemtsev [MVP]]

Hello James,

just to add to previous post make sure that u have all latest .NET SP installed

coz very rare it can be .NET FW bug

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo


JL> Hi,
JL> A couple of users have been getting this same .NET Runtime 2.0 error
JL> from an app that I have written, and I haven't been able to diagnose
JL> or debug the problem:
JL> Faulting application.....faulting module kernel32.dll version
JL> 5.1.2600.3119 stamp 46239bd5 debug? 0, fault address 0x00012a5b.
JL>
JL> Any help would be greatly appreciated.
JL>
JL> Thanks.
JL>

 

[James Lamanna]

Hi,
Unfortunately I haven't been able to reproduce this error on any of my
systems, this only occurs on a couple of client machines.
I do use P/Invoke in some places.
I guess I'll keep trying to duplicate the error here so I can get a
debugger on it.

Thanks.

-- James

 

[michal]

Hi,

I have got very similar problem.

I have a program that uses third party assembly that access unmanaged dll.
It worked very well at my client machine since recently. Now it behaves
really odd. When I try to debug it on my desktop with Visual Studio it runs
fine. No error, warnings whatsoever. When I run it manually at client machine
it just runs. But if I run it as a SQL Agent job (invoking it by xp_cmdshell)
it crashes and logs error to application log.

Faulting application xlqguar2.exe, version 2.0.0.0, stamp 47c2676a, faulting
module kernel32.dll, version 5.0.2195.7135, stamp 46236fd1, debug? 0, fault
address 0x0002bcb1.

What may it be caused by?

Some details:

System: Windows 2000 SP4
SQL Server 2000

I will appreciate any help.

Regards
michal

Hi,
Unfortunately I haven't been able to reproduce this error on any of my
systems, this only occurs on a couple of client machines.
I do use P/Invoke in some places.
I guess I'll keep trying to duplicate the error here so I can get a
debugger on it.

Thanks.

-- James

Hello James,

just to add to previous post make sure that u have all latest .NET SP installed

coz very rare it can be .NET FW bug

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

JL> Hi,
JL> A couple of users have been getting this same .NET Runtime 2.0 error
JL> from an app that I have written, and I haven't been able to diagnose
JL> or debug the problem:
JL> Faulting application.....faulting module kernel32.dll version
JL> 5.1.2600.3119 stamp 46239bd5 debug? 0, fault address 0x00012a5b.
JL>
JL> Any help would be greatly appreciated.
JL>
JL> Thanks.
JL>

 

[Kevin Brown]

I'm getting this problem also. Mine arises after an exception is caught
in my compiled executable. If the application is being run through the
debugger everything is fun, however, when I try to run the compiled .exe
and an exception is caught I get

Faulting application wbpattersondental.exe, version 1.0.0.0, stamp
481b5633, faulting module kernel32.dll, version 5.1.2600.3119, stamp
46239bd5, debug? 0, fault address 0x00012a5b.

in a Windows popup that only let's me close the application, which my
app wouldn't normally let me do, which is why I'm catching exceptions.
Any help would be greatly appreciated.

Thank you.