Help! Attempt to modify a read-only node - InfoPath Dev
in

InfoPath Dev

Help! Attempt to modify a read-only node

Last post 01-09-2007 12:45 PM by touque. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 01-09-2007 10:15 AM

    • touque
    • Not Ranked
    • Joined on 11-06-2006
    • Canada
    • Posts 2

    Help! Attempt to modify a read-only node

    InfoPath 2003 SP2
    Managed code written in vb.net (VS .NET 2003)
    Windows Sharepoint Server 2.0
    The form is given full trust and digitally signed before being published.
    I have published it to the server to replace previous version (which had no managed code)

    Now only I can open existing forms or fill out this form

    Other users cannot, and instead get:
    Form template (https://..../template.xsn)
    "InfoPath cannot create a new, blank form
    (or InfoPath cannot open the selected form if opening existing)
    because of an error in the form's code.
    Attempt to modify a read-only node.

    Form works for me but not other users. The sharepoint server is in Trusted Sites in IE on both my machine and on client machines.

    I'm stuck. Help please!
  • 01-09-2007 12:41 PM In reply to

    Re: Help! Attempt to modify a read-only node

    Hi Chris and welcome to our forum,
    Sounds like a bug in the form. Who developed the form? Do you have access to the original code? If you'd like us to look at it. please purchase a support block and send us the XSN along with the VB.NET code. Thanks!
    Patrick Halstead
    Project Manager at Qdabra
  • 01-09-2007 12:45 PM In reply to

    • touque
    • Not Ranked
    • Joined on 11-06-2006
    • Canada
    • Posts 2

    Re: Help! Attempt to modify a read-only node

    Thanks Patrick, but I think I have it licked.

    On my environment I have an infopath.exe.config file in the same folder as infopath.exe which contains:

    <startup>
    <requiredRuntime imageVersion="v1.1.4322" version="v1.1.4322" />
    <supportedRuntime version="v1.1.4322" />
    </startup>

    I copied the .config file to the client machines and that made the problem go away. Now my managed code is happily churning away.

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