We have a MOSS 2007 site running that has InfoPath forms (created in InfoPath 2007 and/or InfoPath 2010) with workflows created in SharePoint Designer 2010. We’re are preparing for an upgrade to SharePoint 2013. In preparation for that, we’ve been installing Office 2013 on users’s desktops.
We’ve begun to see intermittent issues with people not being able to submit forms from InfoPath 2013. Not all users experience the issues.
Those who do experience it get the same messages:
InfoPath cannot submit the form.
Some rules were not applied. InfoPath cannot submit the form. An error occurred while the form was being submitted. The form cannot be submitted to the following location: https://URL (Full URL is listed correctly) The site may be offline, read-only, or otherwise unavailable. The parameter is incorrect.
For those who have this error appear, they are running Windows 7, IE 8 or 9, and have the SharePoint URL set as the local intranet site in their browser.
Of the forms, we have 5 of the 7 are browser-enabled forms and submit without issue if the user accesses SharePoint from Mozilla Firefox or Google Chrome instead of Internet Explorer. While we’ll be redesigning all of the forms as part of the upgrade process, we need for people to be able to continue processing purchase reqs, time sheets etc, over the next 3-4 months.
Has anyone seen this issue or have any suggestions of how I track down the problem and provide a temporary solution?
It took a couple of days of testing and verifying but here’s what we found:
Of the users who could not submit forms, there were two issues. One was the Compatibility settings in IE. To “fix” the issue two options were available: turn compatibility settings off or uncheck the setting to have local intranet site display in compatibility view. Either one seems to work.
The bigger issue, that I’m still not sure how/why it was happening, is that those users who were experiencing issues were getting login prompts when they submitted. The problem with these login prompts was that they were not pointing to the correct domain, even though the user was logged into the computer with the correct domain. Once we had the users login (going to Login in as another user entering the correct domain login\password combo and clicking to remember credentials) the problem went away.
Anybody have ideas of why that would suddenly begin to happen? I can send more details if needed.