When trying to start an SAP system with the sapcontrol tool and the "StartSystem" method, the following error message is returned ("XX" stands for the instance number):
hostname:sidadm > sapcontrol -nr XX -function StartSystem
<date and time>
FAIL: SSSLERR_SSL_CONNECT (No such file or directory), SapSSLSessionStart failed in plugin_fopen(), <errordetails xmlns="urn:SAPControl"><errordetails xmlns="urn:SAPControl">Checking Start permission on https://virtual-host:5XX14 failed: SSSLERR_SSL_CONNECT (No such file or directory), SapSSLSessionStart failed in plugin_fopen()</errordetails></errordetails>
- The parameter "system/secure_communication" is set to "ON".
- The ASCSxx instance was installed / configured to use a virtual hostname (not necessarily in a high availability - cluster - environment).
- SAP product based on SAP NetWeaver 7.4 or newer
- Client/Server Technology - Starup Service
KBA , BC-CST-STS , Startup Service , BC-CST , Client/Server Technology , BC-OP , Operating System Platforms , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.