InfoPath Dev

I have a situation where Infopath no longer opens my form without crashing. My Infopath document does have VB Code and integrates with Sharepoint. Everything worked fine yesterday but today (I haven't intentionally made any changes) when I launch the form via Debug or Form Preview, some activity starts but before the form is ever displayed, I get the crash dialog that sends information on to Microsoft.

Any Ideas?

Hi Andy,
Well, could be anything. Please make sure you have the latest hotfixes for InfoPath. You can search the forum (upper right) for Knowledge Base Hotfix and find the link to the Trident issue. That's the most frequent. Install the patch, then try again. If it still happens, go to EventVwr and look up the Bucket ID for the crash and we can investigate further.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Thanks for the info. I'm not sure I found the right patch as I didn't find trident link you mentioned, just a registry fix to IE.

Here is the Event View info:
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.

For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

Hi Andy,
There should be one more event with the bucket number in it. We can't verify the bug unless we know the bucket number. Can you look for this?

Patrick Halstead [InfoPath MVP]
InfoPathDev

Sorry. Here ya go.
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.

Great. I'll look this up and see if it corresponds to anything meaningful.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Hi Andy,
Microsoft investigated this and said the bug would be fixed in SP2 (Service Pack 2). I'm not sure when this is due out, but my guess is soon.

Patrick Halstead [InfoPath MVP]
InfoPathDev

found that error seemed to be something corrupt in the manifest file. I could get around the problem by recreating the VB project:
-Create new Infopath VB project using the Infopath template
from the damaged project
-Select all the code in the VB.Form from the damaged project
past it into the new project
-Add the web references to the new project

Now the new project works.

Hi patrick,

quote:

---

Microsoft investigated this and said the bug would be fixed in SP2 (Service Pack 2). I'm not sure when this is due out, but my guess is soon.

---

It's a very good news! Microsoft is waking up? ;-)

Have you any information about that? a link? or anything else?

Thanks

Thierry


Every moment hesitated is a moment gone for life!!! Think about it

Hi Thierry,
Microsoft is very much awake and I have some very responsive contacts ... :) Anyway, my guess is that there may be something searchable in the Knowledge Base. The crash reporting page may even have some text.

Patrick Halstead [InfoPath MVP]
InfoPathDev