InfoPath Dev

Hello,
I have developed an InfoPath form and published it to the SharePoint form library. There is one user (out of many) unable to open the form. The error message is not informative. It basically says " Could not open "https://...../Forms/template.xsn". Is there anyone have any idea what's wrong.
The user has MS Office 2003 installed. He is using IE 6.0, Windows XP Pro (Prob SP1a).
Thanks for your help in advance.
Kin

Is your site a Secure site(https), is every one accessing template.xsn with "https://...../Forms/template.xsn" or do they use "http://.../Forms/template.xsn"?
Normally you will get this error if the template is not located at that specific location.
Can you try one thing from that user
Click on "Modify Settings and Columns" - > "Edit Template" and check out if you can edit the form template and save it back?

I have a similar problem. We have SharePoint intranet site with a form at "http://.../Forms/template.xsn". The same SharePoint site (and form) is accessible at "https://...../Forms/template.xsn" to employees not signed into VPN.

Using save functionality, I am able to add a form to the library from either http or https. But when I visit the external site (https://...) and open a form created from the internal site http://), I get "Could not openhttp://...../Forms/template.xsn". Visa Versa. The form saves ok though.

The test form is using jscript, but would like to get it to work using managed code.

Is there a way to suppress the error?
Is it possible to make the open/submit functionality work in this situation?

The problem in this situation is that the XSN being used in each case really looks different to InfoPath. One is on http and one is on https. Given your environment, the only way to get around this would be to write server code to do the PI fixup translation on the fly when the user requests the XML file.

The primary workaround is for all users to access via https (even when on VPN).

Thank you for pointing me in the right direction, shirazcupala. That's going to save me hours!

Glad to have helped. :)

Hi Shiraz, We are facing below issue. Please go through the below steps. Currently we have configured the url with HTTP protocol to access the XSN file. We have 2 types of users mentioned below. 1. Internal User:- When internal user try to access XSN file HTTP protocol it will work as expected because we have configured the url with HTTP protocol. 2. Third Party User:- When third party user try to access XSN file with HTTPS protocol we are facing issues because we have configured the url with HTTP protocol. Now we want solution when thirdparty user try to login with HTTPS protocol, we want overwrite that protocol with HTTP at RUN TIME. Ultimately we want to convert protocol HTTPS to HTTP or vice varsa dynamically. Please help out on this issue. Thanks & Regards Harisha S