InfoPath Dev

I have an IP 2010 browser form that I have been publishing to the same SP form library in Office 365 for quite some time and everything was working fine opening and publishing the browser form.  I made a change to a couple of the data connections today (changed the option to not automatically retrieve data when the form is opened) becuase the form was taking too long to open.  I am using the submit to sharepoint command in the form using qrules. 

When publishing the form I get the error "Could not verify the form template on the specified server" error when publishing.  When I click that error the only message I can retrieve is "Could not verify the form template on the target server..https://server/_vti_bin/FormsServices.asmx . Make sure you are connected to the network.  The forms service is running fine on the server. The form publishes, but cannot be viewed in a browser??  The error refers to something being incompatible for browsers but nothing has been added to the form that would make it incompatible. 

I changed the data connections back to retreive the data when the form is opened but I still cannot publish the form and open it in a browser.  The other thing I noticed is that in the form options, if I enter the server that is running the forms service in the Compatibility category, it never stays.  Each time I try and publish and open the form options the server is missing. 

I have seen other posts with this same error, but nothing that would pertain to my issue.  Forms Service is turned on, I have full access to site. This is quite a large form and I am not sure if this is a problem with O365 or my form.  Any help would be greatly appreciated.  I attached the template to the email.

One issue I have seen is that I have to open Internet Explorer and make sure I am signed in before I try to publish from InfoPath.

Another thought is that Microsoft pushes updates to Office 365 and sometimes these can cause unexpected issues. To verify whether it's an issue with qRules or with the specific form, can you try the following?:

1. Create a blank, new browser form

2. Inject it with qRules

3. Set up a very simple command (or two), perhaps GenerateGuid.

4. Publish the form to a new Office 365 form library.

5. Open the form in the browser and tries the command(s) you set up.

If this all works, then at least we know it's an issue specific to the form. 

If this all fails, then we know it's related to qRules on Office 365.

Let us know how it goes. Thank you!

Thanks for the response!  I have created a new form and it works fine when published.  I found that on the savings view,  there are two fields under project complexity scale that are simple drop down boxes that had choices of 0,1,2,3,4,5.  I did not receive any errors on these two fields but when I opened them the drop down choices had disappeard and the manually entered choices were blank.  When I clicked "add" to add the choices back in, there was a blank line at the top that needed deleted.  After adding the manual choices to the drop down lists, I was able to publish the form although some of the other data connections were not working???

 I recreated almost all of the data connections and now have the form publishing correclty again.  I hope this helps someone else that has the same problem in the future.

 Is there any way that I would have been able to tell that there was a problem with those two fields without stumbling onto it randomly?  Using O365 I do not have any access to logfiles on the server.  Is there something I can add to the form that would send any type of detailed error messages locally?

 

Thanks again!

If the error is happening from a qRules command, we can look at the Error node in QdabraRules, but if the error is at the SharePoint level, I believe those logs are not available unless we contact Microsoft support.

I sometimes try to admin approve a template that won't sandbox - and then get a better error message about why it isn't browser compatible.

Next time - send me your template. I'll try to admin approve it on one of our ShP servers and we'll see if we can get a better error message. :-)