SAP Knowledge Base Article - Preview

3670614 - EDMX Fetch failed with HTTP Response Code:503 in Cloud Integration

Symptom

OData calls to an upgraded SAP Business One system fail.

HTTP status: 405 Method Not Allowed.

Log shows: “com.sap.gateway.core.ip.component.exceptions.OData4Exception: Vocab validation failed for URI … cause: com.sap.gateway.core.ip.component.exception.ODataProcessingException …”

OData V4 adapter response: “HTTPS proxying is not supported. Use HTTP instead. HTTPS is not needed because communication is already secured by the tunnel.”

Metadata is retrieved but not processed in SAP Business One.


Read more...

Environment

SAP Cloud Integration (CPI) OData V4 adapter connecting to SAP Business One Service Layer via SAP Cloud Connector.

Keywords

405 method not allowed, OData V4 adapter, SAP Business One, metadata fetch error, HTTPS proxying not supported, Cloud Connector configuration, SAP-Connectivity-SCC-Location_ID, invalid EDMX file content, HTTP protocol, secure tunnel, CPI integration flow. , KBA , LOD-HCI-PI-CON-OD , OData Adapters , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.