Thanks Sareesh - this worked for me - but I have a full OBIEE 12.2.1.3 installation that I copied the metadata/config.xml file from. Started the BI Publisher configuration and then kept trying to copy in the file until the install had got far enough through for the copy to succeed. MiKe

All, As DOC ID 2270711/1, in OBIEE – Administration Console – servers, I have the Listen Address set as the FQDN for both AdminServer and bi_server1. If after having ‘ssl.sh internalssl true’, I then run the check ‘ssl.sh report’, I get a ping failure Ping failures (1): Target: bi_server1:BI-SECURITY-SOAP @ <myhost>:9505…

All, I note the Oracle Document OBIEE 12c: ssl.sh Report Report Fails with - Ping Failures (1) - Target: Bi_server1:BI-SECURITY-SOAP Error (Doc ID 2270711.1) updated 20/06/2017. Mike

All, I note the Oracle Document OBIEE 12c: ssl.sh Report Report Fails with - Ping Failures (1) - Target: Bi_server1:BI-SECURITY-SOAP Error (Doc ID 2270711.1) updated 20/06/2017. Mike

HI, Oracle Support have a published BUG 24745827 relating to ' SSL3_GET_SERVER_CERTIFICATE:certificate verify failed '. I'm going to wait for a resolution. In the meantime operate in 12.2.1.2 without 'internalssl true' Mike

Again no solution, just an update. Oracle support have now recreated the SSL PING error for BI-SECURITY-SOAP shown by the 'ssl.sh report' command, but are advising that in my particular circumstances I should ignore the test script report. The error " BI-SECURITY-SOAP" is a known issue in our test machine as we have the…

Just some rambling thoughts. I'm working on linux, so looking at the sslcommand .log file it implies I set my openssl configuration by export OPENSSL_CONF=/install/oracle/ofm_domains/user_projects/domains/<YOUR_DOMAIN>/config/fmwconfig/biconfig/core/ssl/openssl.cnf then I can run openssl s_client -showcerts -connect…

I’ve not found the solution. I raised an SR with Oracle Support 2 months ago but no solution, they tell me they are unable to reproduce the error. Mike

I see the same errors. Did you solve the issue? The ssl.sh report command is logging to $DOMAIN_HOME/bilogs/sslcommand.log. Unfortunately each time you run this is overwrites the log. I assume you have tried to enable ' ssl.sh internalssl true' prior to running the report 'ssl.sh report', so the log of the enable has been…