Secondary data connection fails with colon character in URL

phildetwei — Mon, 22 Jun 2015 19:05:32 GMT

My site collection was upgraded from 2010 to 2013. When upgraded, there was an issue that caused the SP to create a new web app for my site collection (not my idea, but done and will not be reversed at this point).

My URL now has a “:81” in it, going from

http://servername/sites/collectionname to

http://servername:81/sites/collectionname (“:81” after the server name).

Several InfoPath forms that utilize secondary connections for retrieval of data still work properly since the upgrade however if I attempt to add a new connection of this sort, to any list on the site collection, InfoPath returns the error, “The operation could not be completed” from the InfoPath data connection wizard. This error is also returned on the working forms if one attempts to modify and existing connection (that still works and has the “:81” in the box, just can’t re-save it now). Connections migrated over work fine – new connections cannot be added. Existing connections cannot be modified.

Is there another way to reference the “:81” in the URL that will allow this to work? SOAP connection to any list using the normal method also similarly fails. Both of these methods work fine by the way, on the same form, when referencing a URL on the old collection (which is still up) or any of the other 2013 collections that don’t have the “:81” in the URL. There is not much InfoPath support from the SP admins so changes that require their involvement or support are less desirable.

Thanks so much for any direction on this.

Data Connections

Secondary data connection fails with colon character in URL