Debug Application Error

[Irene]

I have two developers using Visual Basic.Net Standard Version 2003 to write
managed code behind InfoPath forms on WinXP SP2. They are able to
successfully build their code and the forms run fine after submitting them to
Sharepoint, but when they try to step through their code in debug, they get
an InfoPath Application Error which shuts everything down. (This is not the
same as the warning about "full trust security" - in this case the infopath
application crashes.)

I can debug the same forms and code without a problem using Windows 2003 and
VS.NET. Is this a known issue and is there a work-around?

 

[Brian Teutsch [MSFT]]

When InfoPath shuts down, does it give you a chance to submit an error
report? If so, we can get some information to help us investigate. Here's
what to do if you get the error reporting dialog:
1 - Open your Control Panels, go to Administrative Tools and choose Event
Viewer
2 - Click on the Application category.
3 - Look for an Error event, with it's big red circle
4 - Look immediate after (above) it for an Information event
5 - Double click to open that Information event
6 - Record the number next to Bucket, (ie Bucket 137738808) and post it up
here

I can't say for sure that we'll have any information, but that will help us
investigate.

Thanks,
Brian

 

[Irene]

Here is the error description:

Bucket 133323527, bucket table 1, faulting application infopath.exe, version
11.0.6357.0, stamp 40b65d54, faulting module mscorwks.dll, version
1.1.4322.2032, stamp 40f6320e, debug? 0, fault address 0x0007214e.

 

[Brian Teutsch [MSFT]]

This issue may be related to exceptions that are being thrown but not being
populated back to the CLR properly by InfoPath. I'm sorry I don't have any
good suggestions, other than to try and determine if there are security
exceptions in your code that can be changed, possibly durin form startup.

Thank,
Brian