Some information about the environment:
- MOSS 2007
- InfoPath 2003 form templates (not browser enabled forms)
- The InfoPath form is published as a site content type to a forms library called "Request Forms" (simply stores all of our request forms). This forms library is where users launch the form.
We have a request form that when submitted, saves the form to a SP Document Library. A workflow then copies the new form to another more 'locked down' document library. I've noticed a few forms, when viewed from the Properties page of the form result in the following error when the document link is clicked (note: you would have to go toView Properties of the list item and then click the name link to duplicate the error). Error message:
"The following file is not a valid InfoPath form template:
http://sharepoint.companydomain.com/sites/subsitename/Request%20Forms/Request%20Form%20Template.xsn?Source=http://sharepoint.companydomain.com/sites/subsitename/Request%20Forms/Forms/Allitems.aspx&OpenIn=PreferClient&NoRedirect=true&XsnLocation=/sites/subsitename/Request%20Forms/Request%20Form%20Template.xsn"
If I view the XML headers for the InfoPath forms that result in this error, the HREF value for the template is the URL above. In theory, the HREF value should just be a link directly to the template: http://sharepoint.companydomain.com/sites/subsitename/Request%20Forms/Request%20Form%20Template.xsn. However, as you can see, additional parameters in bold are being added for some reason. I thought having the form launched from multiple locations on the sharepoint site may be the cause, but this doesn't seem to always duplicate the error.
Those forms that do not result in an error have HREF values equal to the URL in the paragraph above. Thus, they open without any problem. I should also note that if you click the Name link directly from the Document Library view (i.e. All items view), the form also opens without any issue. It's just when you go to View Properties of a list item and then click the Name link that presents the issue.
Any thoughts on what could be causing some InfoPath forms based on a site content type to have different template location values in the XML headers?
Regards,
Nishant