How to track down source of crash + Event log error?

8 Oct 2008 5:34 PM

Grant Schenck

Hello,

I built a client application using C# .NET 2.0. It runs fine at a number
of customer sites. One customer is reporting several users getting
problems. At start up it crashes with a dialog "myapp has encountered a
problem and needs to close..."

Checking in the event log we see and event with the following information:

Source: .NET Runtime 2.0 Error
Event ID: 5000
Type: Error
Description:
EventType clr20r3 P1 myapp.exe, P2 1.0.0.0, P3 48ea486b, P4 system.security,
P5 2.0.0.0, P6 4333ae39, P7 c2, P8 e2, P9 udta330idobh2roz2ayvlcelag5agtls,
P10 NUL.

Now, my application use an unmanaged COM object and it also access the
Windows Registry (HKLU) and also uses a web services interface.

Based on some searches I'm thinking this might be some kind of security
issue but I'm not sure where or what to check. Any input would be helpful.
I'm not that familiar with Windows Security so if you have any ideas it
would be helpful if you could describe the procedures I could follow to try
to address this or at least better determine what is causing the problem.
It is not really an option to run under a debugger at the customer site.

Thanks!

--
Grant Schenck

19 Nov 2008 8:25 AM

Robin

Run the program under a Debugger. Remote Debugger from VS or IDA are great
for this.

Then you might see what the error is.

Kind Regards,
Robin

Show quoteHide quote

"Grant Schenck" wrote:

> Hello,
>
> I built a client application using C# .NET 2.0. It runs fine at a number
> of customer sites. One customer is reporting several users getting
> problems. At start up it crashes with a dialog "myapp has encountered a
> problem and needs to close..."
>
> Checking in the event log we see and event with the following information:
>
> Source: .NET Runtime 2.0 Error
> Event ID: 5000
> Type: Error
> Description:
> EventType clr20r3 P1 myapp.exe, P2 1.0.0.0, P3 48ea486b, P4 system.security,
> P5 2.0.0.0, P6 4333ae39, P7 c2, P8 e2, P9 udta330idobh2roz2ayvlcelag5agtls,
> P10 NUL.
>
> Now, my application use an unmanaged COM object and it also access the
> Windows Registry (HKLU) and also uses a web services interface.
>
> Based on some searches I'm thinking this might be some kind of security
> issue but I'm not sure where or what to check. Any input would be helpful.
> I'm not that familiar with Windows Security so if you have any ideas it
> would be helpful if you could describe the procedures I could follow to try
> to address this or at least better determine what is causing the problem.
> It is not really an option to run under a debugger at the customer site.
>
> Thanks!
> --
> Grant Schenck
>
>
>