none
SharePoint 2013 SOAP Connection

    Question

  • 

    I'm attempting to establish a SOAP connection from a SharePoint 2013 list so I can share the data across site collections. I've done this successfully in SharePoint 2010 but cannot get it to work correctly in SP2013. Here is what I've done while using SharePoint 2013 Designer: - Create the SOAP connection by filling in -- Service Description Location: http://portal.XXXXX.local/_vti_bin/Lists.asmx?WSDL - Click on the 'Connect' button which activates the rest of the dialog box -- Port: ListsSoap -- Operation: GetListItems - Parameters: -- listName: my list's GUID -- viewName: my list's "All Items" view GUID I then save the connection calling it "TestSOAP" and all looks good to this point so I create a new Web Part page.aspx. Open the page in advanced mode and insert an Empty Data View web part. After saving the file I then put my cursor between the <Data Source> </Data Source> tags and insert the TestSOAP data connection. The following code appears: <SharePoint:SoapDataSource runat="server" id="SoapDataSource1" AuthType="None" WsdlPath="http://portal.XXXXX..local/_vti_bin/Lists.asmx?WSDL" SelectUrl="http://portal.XXXXX..local/_vti_bin/Lists.asmx" SelectAction="http://schemas.microsoft.com/sharepoint/soap/GetListItems" SelectPort="ListsSoap" SelectServiceName="Lists"><SelectCommand><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><GetListItems xmlns="http://schemas.microsoft.com/sharepoint/soap/"><listName>371b9b0f_x002d_26ab_x002d_4208_x002d_9582_x002d_99dfea5ba811</listName> <viewName>bd73ba5a_x002d_5a55_x002d_4d43_x002d_9fc1_x002d_40685b0f16cb</viewName></GetListItems> </soap:Body></soap:Envelope></SelectCommand> </SharePoint:SoapDataSource> The Data Source Details view appears with the following message: The server returned a non-specific error when trying to get data from the data source. Check the format and content of your query and try again. If the problem persists, contact the server administrator. Searching on-line shows many different suggestions to correct this problem but none seem to work in both our development and production environment. This all worked perfectly in SharePoint 2010 but we've now upgraded to SharePoint 2013 so need to get this figured out. Thanks for any help you can provide. George

    Sunday, January 1, 2017 10:33 PM

All replies