Access Denied Message on Form open - InfoPath Dev
in

InfoPath Dev

Access Denied Message on Form open

Last post 07-13-2009 06:20 AM by JerryK. 0 replies.
Page 1 of 1 (1 items)
Sort Posts: Previous Next
  • 07-13-2009 06:20 AM

    • JerryK
    • Not Ranked
    • Joined on 01-29-2008
    • Posts 5

    Access Denied Message on Form open

    Good morning,

    I've done some Google-research on this and looked some of the books we have in the office. This is the issue.

    InfoPath 2003 (11.8165.8221) SP3

    XML form (ex: Form.xml) - distributed via email to users
    XSN template (ex: template.xsn) stored in folder on an https webserver.
        - Template uses managed code written in Visual Studio 2003
        - Template has embedded data: 3MB XML file, used to populate various form controls
        - Template is published with a certificate and needs "Full Trust"

    The template has been in use for about 15 months and has gone through 3-4 updates.

    Process:
        Users open Form.xml, which reaches out to template.xsn and pulls down template        
        embedded data and properties. Users fill out form and submit form data to a web service via a data connection.
        These users are usually not on our domain, they access the template from their own home internet connection.   

    Exception:
        When a user opens Form.xml, the progress bar appears showing that it's        
        connecting to template.xsn  the properties appear to be downloading
        but an error is thrown stating:

            InfoPath cannot open the following file: Form.xml.
            Access Denied.

    This is a very non-intuitive message. The template information is not pulled and the form is not opened. Looking in the <user>\Local Settings\Application Data\MicroSoft\InfoPath\FormCache\ folder, the Guid-based folder which is supposed to contain the template information has not been created.

    This does not appear to happen to all users, only some. Also, this seems to be a recent development. Our last template update was in February.

    I'm not 100% but I don't think that this is neccessarily an InfoPath issue but I am no expert - there have been no changes in how we deploy new templates.

    For those who are experts, have you received this error before?
    If so, what can cause this error?
        * server-side setting change?
        * client-side setting change?
        * InfoPath deployment or template problem?

    Any thoughts or ideas are much appreciated.

    Thanks,

    Jerry K

Page 1 of 1 (1 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.