InfoPath Main Submit pointing to old server after upgrade to SharePoint 2010

Question

Hello

I've just completed an upgrade from MOSS 2007 to SharePoint 2010. I noticed several Data Connections for the Main Submit button in a number of InfoPath forms are pointing to the old MOSS 2007 address.

How is this possible when I ran the following commands:

    Update-SPInfoPathUserFileUrl
    Update-SPInfoPathAdminFileUrl

The above commands are meant to replace any .UDCX and .XSN pointing to the old address with the new address.

I also noticed when I open the form in Design mode using InfoPath 2010, I am unable to modify the Data Connection address manually. The textbox is greyed out or disabled.

Is there anything else I need to do?

Thank you.

Yoshi

Answer 1

Hi Yoshi ,

I understand that you have upgraded to SharePoint 2010,but some submit data connection doesn’t update after running the commands. How do you perform the upgrade? Using Database attach upgrade or In-place upgrade?

In order to upgrade InfoPath service during database attaché upgrade, you need to: Existing administrator-approved form templates and data connections must be migrated to the new deployment and upgraded to work with InfoPath Forms Services in Microsoft SharePoint Server 2010. 

After running Update-SPInfoPathUserFileUrl and Update-SPInfoPathAdminFileUrl command, you need to click ‘Relink All’ in a form library.

For more information about the detailed steps, you can refer to this site:Plan to upgrade form templates during an upgrade to SharePoint Server 2010: http://technet.microsoft.com/en-us/library/ee704551.aspx#updateLinks

Thanks,

Entan Ming

---

Entan Ming

TechNet Community Support

Answer 2

Hi, 

You are upgraded to SharePoint 2010. You need to modify connections in your info path form. 

Click on Data Connections from ribbon. Select data connection and click on modify. change the Url of your current address and form will run fine. Also check for is there any custom code running on form load. 

If the connections are disabled then you need to create those connections again. 

Thanks 

---

amol

Answer 3

Hi Guys

Thanks for your replies. I managed to work out what the issue was.

When I ran the Update-SPInfoPathUserFileUrl command against a web application, it managed to update two of the three Content Databases. It wasn't updating the main Content database and I was able to tell this by checking the status of the running jobs in Central Admin.

The Update-SPInfoPathUserFileUrl command can be run against a Web Application, a Content Database or a Site. I decided to run the command against a Site and it worked. I then tried to run it against the main Content DB and it finally worked and all UDCX and XSN files were updated. However, I did have to download some of the InfoPath templates and republish them to the new server even though the UDCX and XSN xml files showed it was pointing to the new server. Wierd?

Regards,

Yoshi