SharePoint Integration

Re: Microsoft InfoPath has stopped working

Doreen — Wed, 13 May 2015 19:03:19 GMT

I had the same issue today and although an older thread I thought I’d share my 2¢ experience. The only difference is my environment is not the same combination as the others. I am using Win 7, IE9, InfoPath 2007 (client form) and SharePoint 2007. And this happened just after Tuesday Windows updates…go figure!

Problem: When a user attempts to tick 1 of 2 a radio buttons on one particular InfoPath 2007 form that is using qRules and DBXL, the following Microsoft Office InfoPath dialog appears and they are not allowed to tick the radio button. They are able to tick this same radio button on other forms in the library – it’s just (so far) one form identified with a problem. This form is no different than others in the library.

Error dialog:

“Microsoft Office InfoPath has stopped working. Windows can check online for a solution to the problem.

Options: Check online for a solution and close the program or Close the program

View more problem details:

signature:

Problem Event Name: APPCRASH

Application Name: INFOPATH.EXE

Application Version: 12.0.6662.5004

Application Timestamp: 50105e7f

Fault Module Name: IPEDITOR.DLL

Fault Module Version: 12.0.6662.5004

Fault Module Timestamp: 50105f02

Exception Code: c0000005

Exception Offset: 002b106e

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 1033

Additional information about the problem:

LCID: 1033

Brand: Office12Crash

skulcid: 1033

Solution:

I found a work around thanks to the suggestions in the forum but I did not find a solution to keep it from happening again.

The solution was to open the form in a different environment. Fortunately I have a remote machine with Windows XP Pro and IE8 (& InfoPath 2007 & SharePoint 2007) and I was able to tick this troublesome radio button and submit the form back to SharePoint!

Re: Microsoft InfoPath has stopped working

Ganthet2814 — Fri, 11 Jul 2014 14:15:23 GMT

I had the same problem with a form I had been working on... same exact scenario where I would go to open the form (in Preview or otherwise) and I would get the same "problem/close" message yet I could open it in on an XP machine.

Now, I don't know if you have a Query for data when the form opens, but I turned off the "query on open" in one of the receive Data Connection I was using. I then created a Query button in the form to pull the information in after the form has loaded.

Worked like a charm!

The only side-affect is that I had to redefine the dropdowns I was using to call to that Data Connection, but that might have been caused by some other trouble-shooting.

Hope this helps!

Re: Microsoft InfoPath has stopped working

Hilary Stoupa — Tue, 21 Jan 2014 17:02:25 GMT

Thanks so much for the info & update, Mark!

Re: Microsoft InfoPath has stopped working

marktolley — Tue, 21 Jan 2014 16:23:50 GMT

There's a Microsoft Hotfix available on (free) request, http://support.microsoft.com/kb/2817598, that appears to resolve the issue on our PCs.

It refers to the following knowledge base article: -

2817603
(http://support.microsoft.com/kb/2817603/ )
Query parameters are lost when you open a new form in InfoPath 2010

Regards,

Mark

Re: Microsoft InfoPath has stopped working

Patrick Halstead — Sun, 11 Aug 2013 20:29:00 GMT

Please call Microsoft support and complain. I will escalate again.

Re: Microsoft InfoPath has stopped working

Bismark E. — Tue, 06 Aug 2013 17:56:23 GMT

Hello Patrick Halstead, l would like to know if microsoft resolved this mistake , l have a lot of problems whit this and changing ipeditor.dll is not enough, please let me know.

Re: Microsoft InfoPath has stopped working

marktolley — Tue, 30 Jul 2013 07:43:35 GMT

This problem appears to still exist in the new Service Pack 2 for Office 2010 - and there's no way to remove the IPEDITOR patch...

Re: Microsoft InfoPath has stopped working

Patrick Halstead — Fri, 12 Jul 2013 15:27:18 GMT

I was in contact with Microsoft several weeks regarding this. I will ask them what the status of this is.

Re: Microsoft InfoPath has stopped working

TxSteve — Fri, 12 Jul 2013 13:25:08 GMT

Update: So now we WANT to install the patch. Has anyone else encountered this issue and was able to successfully identify what was causing the conflict and was able to resolve? Just short of completely rebuilding the form from scratch in v.2010 is what I think we are down too, but it would sure be nice to know what the root cause is.

Re: Microsoft InfoPath has stopped working

TxSteve — Tue, 23 Apr 2013 17:07:52 GMT

We found the issue with our forms. Turns out it was/is KB2760406.

http://answers.microsoft.com/en-us/office/forum/office_2010-infopath/kb2760406-infopath-error-after-update/58631190-8bc1-401a-921c-b6351474350b

We uninstalled the patch and restored functionality.

Re: Microsoft InfoPath has stopped working

marktolley — Tue, 23 Apr 2013 14:36:01 GMT

I'm also seeing the same problem, but it only affects 1 form out of about 50 we have on our SharePoint server.

WinDbg reveals the crash to be caused by a good old 'null pointer' exception within IPEDITOR.DLL

As a test, I made a copy of the form library, changed the form ID and removed all custom code and data connections but the problem persists.

I've noted that a number of people have reported this problem over the past few days. It appears to be caused by one of the two InfoPath 2010 updates from the April 2013 WIndows Update.

Although not a recommended solution, removing either of these 'patches' appears to resolve the problem.

Microsoft InfoPath has stopped working

TxSteve — Mon, 22 Apr 2013 13:13:42 GMT

"A problem caused the program to stop working correctly. Please close the program. "

We are using a form and SharePoint 2010.

So I am getting this error with users running Win7 Office 2010, but users with WinXP and Office 2007 can open the form, populate and submit to SharePoint with no errors. The form has been working for weeks with no previous errors.

Is there a way for me to get more detailed information other than; There was an error... and then it closes.

PS.. Not running 64bit, occuring with multiple users.