InfoPath Dev

We have an InfoPath form that runs fine on Windows 7, with either Office 2010 or 2013.  It also runs fine on Windows 8.n, with either Office 2010 or 2013, 64-bit.

This form fails when running on a Windows 8.n system with Office 2010 or 2013, 32-bit.  The error is: 

InfoPath cannot open the selected form because of an error in the form's code.

Exception has been thrown by the target of an invocation. 

Our development environment is Windows 7, Office 2013 64-bit.  Publishing this form from Windows 8.1, Office 2013 64-bit results in no change on what systems it works or fails.

Someone must have InfoPath 2013 running on a Windows 8 system with 32-bit Office.  Right?  Any help would be appreciated.

Paul  

This problem is really starting to bite us now, as more of our users are installing Windows 8.1 and Office 2013 32-bit.

We can create a small form and it runs just fine under Windows 8.1 and Office 2013 32-bit.  But when we try to run InfoPath Filler or InfoPath Designer on our full production form, it fails.

InfoPath Designer fails with "Not enough storage is available to process this command".

Could it be the size of our form that is causing this?   Our manifest.xsf is 5 MB.

This form runs fine if Office 64-bit is installed, but this is not the standard installation at our company, and it causes conflicts with other software.  We have spent a lot of time working on this problem, with no success.  Yet.

Paul

Oh wow - that sounds awful. So, if you create a new form, your Windows 8.1 / Office 2013 (32 bit) users can open it in filler. But this other form - you can't even open it in designer on a machine with Windows 8.1 / Office 2013 (32 bit)? The form is a 2013 Filler form?

Hilary,

You are correct on all counts.

Most of our users are still running Office 2010 on Windows 7, so our form is published with that in mind--InfoPath 2010 form at .NET 2.0.  All Windows 7 users are happy.  Windows 8.1 users with Office 32-bit are not. 

We have the same problem no matter how the form is published:

• InfoPath 2010 form, .NET 2
• InfoPath 2013 form, .NET 2
• InfoPath 2013 form, .NET 4

Using InfoPath (Filler or Designer) under Windows 8.1 and 32-bit Office 2013 fail with all three combinations.

Filler fails with "InfoPath cannot open the selected form because of an error in the form's code.  Exception has been thrown by the target of an invocation."

Designer fails with "Not enough storage is available to process this command".

Ideas?

Paul 

Where is the form published? SharePoint? Is the 32 bit Office install from Office Online by any chance? I am kind of grasping at straws here - but I do remember the early Office Online installs of InfoPath having some issues... and was also wondering if the Windows installs are upgrades if the template might be cached some place. One of my colleagues is using Windows 8.1 with 32 bit Office, and she has not had trouble opening InfoPath forms that the rest of us use, so I am bugging her for more details on her environment right now....

The form is published on a Windows network share and run from there. The local cache is not the problem, as new forms made to diagnose the problem have different names, so they would be copied fresh to the user's InfoPath cache.

This is not Office Online; rather it's Office Professional Plus.

Our guess is that there's some resource we're short on due to the size of the form we publish, since a form with one view works just fine on 32-bit Office.   We have 103 views, some simple, most not.  It's also interesting to note that we can open up any of our forms up to the version published about a year ago.  Everything before that opens in Filler and Designer, everything after that fails.

Paul 

I believe I have found a solution to this problem.  So far, it seems to work.

By default, 32-bit applications are not "large address aware" and cannot address space greater than 2 GB.  INFOPATH.EXE is no exception.

To see if an application is "aware", do a  DUMPBIN /HEADERS  command on the image.  If the output contains the line "Application can handle large (>2GB) addresses" then it's "aware".

If not, do an  EDITBIN /LARGEADDRESSAWARE  command on the image.

We have done this with INFOPATH.EXE and now it both opens with InfoPath Filler and designs with InfoPath Designer, on a 32-bit Office system running Windows 8.1.

Paul