SharePoint Document Issues

Fix SharePoint Server 2019 SOAP Responses Empty or List Not Found Error

Tauseeq Magsi Sep 30, 2026 869 views

Question details

User needs to resolve an issue where SOAP requests to a SharePoint Server 2019 site return empty results or state that the list is not found.

Fix SharePoint Server 2019 SOAP Responses Are Empty or Return List Not Found

Product: SharePoint Server 2019
Device & OS: not provided
Scenario: Executing SOAP API methods like GetListsCollection on a SharePoint Server 2019 test site.
Observed behavior: The server returns an HTTP 200 success code and no errors appear in ULS logs, but the SOAP response body is empty or returns a 'List is not found' error despite the lists actually existing.

Before you start

Ensure the calling account has proper read permissions for the target site collection and that you have basic familiarity with XML namespaces used in SharePoint SOAP requests.

Solution 1Recommended

Verify SOAP Endpoint, Namespaces, and Permissions

Check your SOAP request parameters to ensure the endpoint URL, authentication, and XML schemas perfectly match SharePoint Server 2019 requirements.

Empty responses with an HTTP 200 OK status usually indicate that the server successfully parsed the request structurally, but the specific XML namespaces, site path, or authentication context did not map to the expected data.

Check the Site Collection Path

Verify that your SOAP endpoint URL points exactly to the specific site or subsite where the list resides (e.g., http://<site_name>/<subsite>/_vti_bin/lists.asmx), rather than the root directory.

Validate the XML Request Namespace

Inspect your SOAP envelope and ensure the request namespace exactly matches SharePoint's expected schema, which is typically http://schemas.microsoft.com/sharepoint/soap/.

Confirm Authentication and Permissions

Ensure the authentication method (NTLM, Kerberos, or Claims) passed by your calling application matches the SharePoint Server 2019 web application settings, and that the executing account has adequate list access.

Test Against a Simple List

Compare your request syntax with a known working SharePoint Server SOAP example and execute a test request against a brand new, basic custom list to rule out list-specific corruption.

Consult Dedicated Support: Because this issue specifically concerns SharePoint Server (on-premises) rather than SharePoint Online, it is highly recommended to post the raw request and response payloads in the dedicated SharePoint Server Microsoft Q&A channel for further technical investigation.

Free Microsoft Office alternative

Manage and Edit Documents Seamlessly with WPS Office

While troubleshooting SharePoint Server backend API issues, you still need a reliable suite to manage, edit, and collaborate on your everyday documents. WPS Office provides a lightweight, highly compatible, and free alternative to Microsoft Office.

1. Download WPS Office: Visit the official WPS website to download and install the free WPS Office suite on your device.
2. Open Your Documents: Launch WPS Office and click 'Open' to load your existing Microsoft Word, Excel, or PowerPoint files without losing any formatting.
3. Edit and Save: Edit your documents seamlessly and save them in standard Office formats to maintain perfect compatibility with your colleagues.

Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx)Lightweight installation that won't slow down your systemFamiliar user interface ensuring a zero learning curveBuilt-in PDF editing, conversion, and document management tools

microsoft office alternative - wps office

Frequently Asked Questions

Why does the SharePoint SOAP API return HTTP 200 but an empty response?

This commonly happens when the XML namespace in your SOAP request is incorrect, missing, or malformed. SharePoint processes the HTTP request successfully (hence the 200 code) but fails to locate the expected data fields defined by the schema, resulting in an empty response.

How do I find the correct SOAP endpoint URL for my SharePoint list?

The standard endpoint for list operations in SharePoint Server is typically located at /_vti_bin/lists.asmx appended directly to your specific site or subsite URL where the list is hosted.

Why does GetListsCollection report 'List not found' when I know the list exists?

This usually occurs if your endpoint URL points to the root site collection instead of the specific subsite containing the list, or if the account executing the API call lacks the necessary permissions to view that specific list.

Document & File Issues