InfoPath Dev

When she opens a new form by using the actual form library new button it opens as read only and tells her she's working offline.  That's really strange!!

It looks like this topic was started about 3 years ago...  Has anyone ever been able to fix or work around this problem?

We successfully work around it by not hotlinking to the form,.

We make the users open the form lbrary and click NEW to create the form.

When we do this, we never get the error.

Yes, instead of getting the error when she does it that way it opens the form offline in read-only mode for some reason...

I manage and develop a lot of InfoPath forms and my users get this error All.The.Time!  And I'm still insisting on them opening the majority of our forms via a link, so I do have a fix that works every time.  It's bizarre, but it works. 

Go to "security and trust" in the form options.  You want "domain" of course.  You'll find that either the "automatically determine..." checkbox will be selected or the "domain" option button will be selected (without "automatically" checkbox selected)  Whatever is set, do the opposite (even though, in theory, they both do the same thing). 

 For example, if the "automatically determine..." checkbox is set to true, then UNselect that and just make sure the "domain" option button is selected.  Re-publish the form.  If the "automatically determine" checkbox is not selected, then select it and re-publish the form. 

I realize this makes no sense since both of those options do the same thing.  But this fixes the problem for me every time.

I am in the habit now of testing a form when I publish it to make sure it opens properly. 

 I have found the resolution to our problem is when I publish the form to a network share that I use the FQDN\share name.  Originally we were just using the server name\share and had the above error.  Don't know if this will help others but it worked in my situation

 Why not just make a shortcut to where the "New" function goes? I've done that before.

The URL will look something like this: http://yourSPurl/FormServerTemplates/templateName.xsn

that is exactly what causes the error in the first place - we are going in circles here!

another suggestion I have found is here - not yet tested

I'm just throwing this out there in case anyone else has this problem.  But in my instance the .xsn file was out on a network share.  I tried changing the security in the form and it didn't seem to matter.  I would receive that same message everytime I opened the form regardless of whether it was a link or a direct file.

 The fix for me was to go to c:\users\"username"\appdata\local\microsoft\infopath\ and delete all of the files and folders from that directory.  The next time I opened the form I was prompted to upload the form template and it worked fine.

 Of course now I need to replicate this to 15 other users machines.

I've had success by clearing the Infopath cache.  I've found this is particularly frequent when user upgrades from InfoPath 2007 to 2010.  I've created separate Clear Cache shortcuts so our user can run the appropriate one, based on which version of InfoPath they're using - 2007 or 2010.

To run the clear cache go to Start > Run and enter:  Infopath /cache clearall

This fixes it for my users every time.

This issue had a deceptive error message for me. Though it was complaining about permission levels, the real problem was that the form wasn't where it thought it was.

My problem was (recreatably) caused by saving the form template to one location, and then moving that .xsn file to a different location (a SharePoint directory, for instance) from which customers would access it. When I, or any one else for that matter, tried to open a form based on that template, I would get the aforementioned error.

The solution was simply to open the form template in design mode, and then to save it to the final location from which other users would access it. Once the .xsn file exists, it needs to stay where it is to ensure it functions properly. If you need the form template in a different location, open it in design mode and save it there.

I don't know if this is the solution that everybody needs, but it was certainly the solution to my problem.