AccessViolationException in PISDK application

Discussion created by MaxStrueverWipro on Jan 11, 2012
Latest reply on Jan 18, 2012 by MaxStrueverWipro

I had an AFSDK/PISDK application crash mysteriously. The entry in the Windows Application log said that the “faulting module” was PISDK.dll and the problem was logged as


Application: EBS.exe


Framework Version: v4.0.30319


Description: The process was terminated due to an unhandled exception.


Exception Info: System.AccessViolationException




   at PISDK.IEventPipe2.RemoveSignUp(System.Object, System.Object)


   at MyApp.MonitoredAttribute.delete()


   at ...”


the part of my code that calls RemoveSignUp is wrapped in a try-catch. Upon investigation, I see that exceptions such as this are deemed "corrupted state exceptions" and cannot be caught with the usual try catch.


What could the root source of the AccessViolationException be? Is this simply an issue of trying to removesignup on a PIPoint which isn't in the event pipe anymore? Or is this related to the STA threading issues of PISDK?