Application terminates due to access violation?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Does anyone knows the meaning with KB823140 and KB903886? These articles
treat the issue of "Access Voilation" in .NET framework.

I have an application developed in C# that sometimes simply dies. No
messages, no error codes, no exceptions. A few days ago I got a tip that this
might be caused by an "Access Violation" when calling methods in COM
components.

Daniel
 
I think I might be the person that gave you that answer. the first article is
the one I was refering to. It says that it affects 1.0 and 1.1 so will be
fixed in 2.
What do you want to know about the meaning. It describes an issue
Marshalling calls to COM so an AV is thrown and the framework is murdered for
it.

Ciaran O'Donnell
 
Hello!

I want to know wether this issue is solved in the .Net framework 2.0 or not!
I converted my application to use 2.0 insted of 1.1 + service pack 1 without
any improvements.

//Daniel
 
It should be. If you are still experiencing it, try to track it down to a
particular operation or type of operation you are doing and try replicating
it on another machine or a VM. check the eventlog to see if it logs anything
there or add tracing to your app to see where it dies, then use it to narrow
it down to the line it dies on.
Its going to need to be tracked down in order to find out what it is.

Good Luck

Ciaran O'Donnell
 
Back
Top