Error: Response was of unexpected text/html ContentType. Incoming portion of HTML stream: (none)

	English	
Deutsch - Machine Translation Español - Machine Translation Français (France) - Machine Translation Italiano - Machine Translation 日本語 - Machine Translation 한국어 - Machine Translation Português (Brasil) - Machine Translation Русский - Machine Translation 简体中文 - Machine Translation

Support Note KB0401630

Symptom

Transactions sent to ERP fail on the Managed Gateway for Spend&Network side with error:

Response was of unexpected text/html ContentType. Incoming portion of HTML stream: (none)

Cause

The concerned webservice does not exist on ERP side.

For transactions that send SOAP messages to ERP, the webservice alias must be published on ERP side and also must match with the endpoint address posted by Managed Gateway for Spend&Network.

Resolution

Publish the interface via the Set Up the Interface in the SPRO configuration of the concerned integration scenario
If the interface is already published, make sure the end-point URL used by Managed Gateway for Spend&Network is the same published on SOAMANAGER

See Also

For example, for BusinessPartnerSUITEBulkReplicateRequest transaction, the endpoint pointed on Managed Gateway for Spend&Network is http://domain/sap/bc/srt/xip/arba/businesspartnersuitereplicaterequest/client where domain is the virtual host configured on your Managed Gateway for Spend&Network connection and client is the ERP client.

When checking the same on SOAMANAGER, the Alternative Access URL should be exactly the same used by Managed Gateway for Spend&Network.

Applies To

SAP Integration Suite Managed Gateway > Managed Gateway for Procurement
SAP Integration Suite Managed Gateway > Managed Gateway for Sourcing Integration