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

  • Thread starter Thread starter Grant Schenck
  • Start date Start date
G

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!
 
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!
Click to expand...

I think this is a security issue perticularly accessing registry in
Vista.

Make sure the user who is executing the code has enough previlages to
access it.

Also I suggest, place some logging code in the method where tou
suspect the crash / access the regisrry (my suspect) , and get the log
file from the client, see where exactly its crashing.

If you can nail it down to the exact line of code / issue, NG members
can help you out.

-Cnu
 
When you say: "Make sure the user who is executing the code has enough
privileges to
access it"

Where exactly would I go to view and change these privileges?

--
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!
Click to expand...

I think this is a security issue perticularly accessing registry in
Vista.

Make sure the user who is executing the code has enough previlages to
access it.

Also I suggest, place some logging code in the method where tou
suspect the crash / access the regisrry (my suspect) , and get the log
file from the client, see where exactly its crashing.

If you can nail it down to the exact line of code / issue, NG members
can help you out.

-Cnu
 
Back
Top