...
If you receive an HTTP receive error, please review the setup noted in the following article: Configuring Outbound PowerConnect Splunk Connection in SAP (PowerConnect ABAP 8.X) . The most common causes for an HTTP receive error include:
...
If you receive an SSL connection error, please ensure that you have imported the latest valid certificate using the instructions noted here: Optional Recommended - Using SSL Encryption between SAP and Splunk (PowerConnect ABAP 8.X) . The most common causes for an SSL connection error include:
Firewall change blocking connection from the SAP system to Splunk via port 443 or port 8088. To test this, log into the SAP server at the operating system level, and perform a telnet command using the following syntax: telnet <url> 443 if connecting via port 443 OR telnet <url> 8088 if connecting via port 8088. If there is a firewall issue, please reach out to your network team to fix the issue. PowerConnect support should not be contacted to remediate networking issues. Here are two telnet command examples:
telnet 172.1.0.61 8088
telnet softwareone.splunkcloud.com 443
Not importing the client, intermediate, and root certificates into the appropriate note in the STRUST transaction. If you apply a valid client certificate, but have updated the root certificate, the latest root certificate needs to be imported using these instructions: Optional Recommended - Using SSL Encryption between SAP and Splunk (PowerConnect ABAP 8.X). Please note that PowerConnect support should not be contacted to update or generate SSL certificates.
SSL certificate expiration for the Splunk endpoint. PowerConnect support should not be contacted to update or generate SSL certificates. You can update the SSL certificate using the following instructions:
How to acquire the latest Splunk certificate: Configure SSL in Splunk (Optional)
How to update the SSL certificate in the SAP system: KB 151 - Update SSL Certificates
If none of these steps meet your scenario, please export the ICM trace file for further analysis: KB 111 - Change ICM Logging Level for Connection Troubleshooting
...