I'm trying to modify my list InfoPath form to connect to a data of a SharePoint Web Service Lists.GetListItems

On the part where I'll specify the parameters, I get the following error:

Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown. Root element is missing.

I think my parameters are correct since I got the IDs from SharePoint Manager. What could be causing this error? Thanks

  • Care to post the code? – RJ Cuthbertson Aug 1 '12 at 13:34
  • I dont have a code, Im simply using the InfoPath 2010 wizard on connecting to the web service. Data > Data Connections > Add... > Receive Data > SOAP > etc... – harousame Aug 1 '12 at 13:40
  • The root element is in the returned data. The beginning of the return string ought to be <?xml version="1.0" encoding="utf-8" ?>. Can you see what the return string is? – RJ Cuthbertson Aug 1 '12 at 13:52
  • Can you upload a screenshot of the Data Connection wizard and the configuration you are using? I'm assuming you are using this to access a list from another site collection? – LeviS Aug 1 '12 at 16:23

The quotes from the article InfoPath: Use SharePoint Web Services :

  • "Why won't InfoPath work with SharePoint Web Services? It comes down to the fact that InfoPath doesn't recognize that some web services, such as Lists.asmx's GetListItems requires strings (which InfoPath handles just fine) and XmlNodes (which InfoPath can't seem to figure out)"
  • "The solution? Create a Proxy Web Service that takes in strings representing the Xml code and create XmlNodes from them"

    Read more there...

Don't kill the messenger...

The answer of Office365 support in discussion Has anyone succeeded using webservice in InfoPath on office 365? is:

  • The root cause of this problem is that "Business Data Connectivity Service" feature is required when trying to get data using web service in InfoPath. However, currently, for security purpose, the Business Data Connectivity Service is not part of the Office 365 SharePoint Online offering. You can find the available features in SharePoint Service Description, which can be found at following link:

    Office 365 for Enterprise Service Descriptions

    For a workaround, you may refer to Sky’s suggestion to build an external webservice. If you have any concern about this future, I suggest you submitting a feedback at

  • Thanks for the answer, i am actually trying to create a proxy web service now. However I'm stuck with the disco command. Its giving me an error of "The request failed with http status 401: unauthorize". I tried googling but i found no help. Im rather new to creating a web service, I'm following this walkthrough msdn.microsoft.com/en-us/library/ms464040.aspx – harousame Aug 4 '12 at 9:50
  • 1
    Please open a new question on this. This board is not for discussions but for questions having answers – Gennady Vanin Геннадий Ванин Aug 4 '12 at 13:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.