Moving published form to new domain - InfoPath Dev
in

InfoPath Dev

Moving published form to new domain

Last post 04-24-2013 06:34 AM by yoni_R. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 04-24-2013 01:05 AM

    • yoni_R
    • Not Ranked
    • Joined on 02-20-2009
    • Posts 7

    Moving published form to new domain

    Hi everyone,

    I have a question about moving a form with dataconnections to a new domain.

    I created the dataconnections and stored them in central admin. I published my form to a sharepoint server and to my local dev environment.

    After uploading the form to central admin, I can activate the feature on the site collections where I need it.

    Now the problem is that the test and production environment are in different domain and I have no way of connecting with InfoPath to these servers. Therefore, republishing is not possible.
    I have updated my dataconnection files to point to the lists on the new environment by changing the site and the listID.

    But after uploading the form in test, I get 5566 errors.

    How can I put a xsn-file from one central admin to another and still have it find the dataconnections in the new central admin?

  • 04-24-2013 05:30 AM In reply to

    Re: Moving published form to new domain

    I don't believe there is a way to upload a form succesfully  to SharePoint other than publishing it (via InfoPath's File > Publish).

    It's quite a unique issue not having access to the domain where the form needs to be published to!

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 04-24-2013 06:34 AM In reply to

    • yoni_R
    • Not Ranked
    • Joined on 02-20-2009
    • Posts 7

    Re: Moving published form to new domain

    The problem is that we keep getting an Invalid Url exception when we try to connect to the environment.

    After researching the issue we found that there was supposedly no site collection at root level, but this is the case with us. Our site collection is in the root but the error still pops up.

    That's why we were hoping to upload the document to central admin without having to publish it again.

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