ADS Error CSoapExceptionTransport: HTTP send returned with status code (100.101)
While working with ADS, we might face many issues and most of them are with respect to the connectivity between the SAP ABAP system and the ADS Service Provider. The ADS Service provider can be the SAP JAVA or SAP Portal system, or it can be an ADS Service via SAP BTP. If you are looking for the standard ADS setup with the SAP JAVA system, you can check it here. In today’s article, we will see a specific error with ADS setup, CSoapExceptionTransport: HTTP send returned with status code (100.101). So, let’s get started.
CSoapExceptionTransport: HTTP send returned with status code (100.101)
This error normally comes up if you have an issue with the Proxy setup or if there is a configuration issue between the SAP ABAP system and the ADS Service provider. An error can be reproduced by executing any ADS test program, like
The exact error will be displayed at the bottom of the screen as below.
SYSTEM ERROR: SOAP Framework error: SOAP Runtime Exception: CSoapExceptionTransport : HTTP send returned with status code (100.101).
Let’s see how to address this error with both scenarios, i.e. with SAP JAVA and with SAP BTP acting as ADS Service provider.
Case 1 : Common Checks Irrespective of ADS Service Provider
ADS configuration is client dependent. Therefore, if it works fine on one client it should work on other clients as well. But if one of the client-dependent configurations, like HTTP service or Proxy configuration, is not the same across all clients, then it can be the issue. To check it, please proceed as follows.
Check HTTP service is connected and the host is not misspelled. Transaction SMICM -> Goto -> Services
Service HTTP & HTTPS should be active and the hostname should be the same across all clients.
Check the Proxy configuration match on both clients. Transaction SICF-> Execute-> Client-> Proxy Settings
Proxy configuration should be the same across all clients as shown below screenshot.
Also ReadMissing Icons in WEBGUI
Case 2 : SAP JAVA/Portal acting as ADS Service provider
In the case of SAP JAVA/Portal acting as ADS Service provider, please check as follows.
- Login to the SAP ABAP system
- Go to SM59 and open ADS RFC
- Check and validate that the Hostname, Port, and path prefix are maintained correctly.
- It might be possible that the misspelled hostname is maintained or there is an extra character in the path prefix, hence the issue.
- If all entries are correct, then login to AS JAVA NWA and make sure the ADS service is up and running.
- Also, validate the “enableSSL” property of the “Document Services Data Manager“, it should be set to “false”. To check it, go to NWA, then Configuration -> Infrastructure -> Java System Properties -> Services -> Document Services Data Manager
- If changes are done, then you need to take restart of your SAP JAVA instance. Please note that only restarting ADS Service will not be sufficient here.
Case 3 : SAP BTP acting as ADS Service provider
In the case of SAP BTP acting as an ADS Service provider, please check as follows.
- Login to the SAP ABAP system and go to transaction STRUSTSSO2
- Check and validate that the SSL Client PSE for ADS is available, if not you need to create it as per standard.
- Note down the CN entry from the SSL Client PSE for ADS
- Check ADS RFC in SM59 for the SAP ABAP system
- Note down the Technical Name for the Sub-Account on the BTP side, it usually will be the entry after the first dash (-) and before the first dot (.)
- Login to your BTP Global account and search for this sub-account via the technical ID noded above.
- Double-click on that sub-account to enter, Click on Services from the left side menu
- Select “Forms Service by Adobe“
- Under the Take Action section, click on Roles & Destinations
- You will see the Roles menu with two roles ADSAdmin & ADSCaller.
- Click on each one and make sure that the CN entry from SSL Client PSE for ADS (which was noted before) is assigned as a user in the bottom area
- Under Destination, check and validate the maintained entry for FP_ICF_DATA_<SID>. Ensure the data maintained here is correct and the connection test works fine.
That’s it. If the above checks are done and necessary corrections are maintained, then the issue should be resolved. Let us know if this helped by putting details in the comment section below.
Stay Healthy, Stay Safe, Jai Hind!