Hi G, Shruti,
Thanks for reaching out to Microsoft Q&A.
Connection is failing due to an unsupported content type in the response from the SAP Datasphere endpoint. Specifically, the error is related to the server returning a MIME type of text/html
instead of the expected application/xml
or similar content types required for OData communication. The easiest way is to check the logs or contact SAP support to ensure the OData service is properly configured and available. Before that you can consider some basic checks by yourself to see if you can narrow down the issue.
- Ensure that the OData endpoint URL you are using is correct and accessible. if the URL is incorrect or missing parameters, the server might return an HTML error page, which leads to the
text/html
MIME type in the response. - Verify that you are authenticating correctly against the SAP Datasphere OData service. OData services often require proper auth (OAuth, Basic Auth, etc.), and failing to authenticate could result in an HTML response indicating a login or permission issue.
- The error mentions
serviceurl+"/$metadata"
. Try opening this URL in a browser or another REST client (Postman) to ensure that it returns the expected metadata in XML format. If it returns an HTML page, there might be an issue with the OData service setup on the SAP side - SAP Datasphere may expose different API versions or endpoints (ex., v1, v2). Make sure that you're using the correct api endpoint that supports OData.
- Ensure that your network does not have any firewall or proxy settings that might interfere with the communication between adf and sap Datasphere.
Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.