SAP Knowledge Base Article - Preview

3417503 - ASCS instance of SolutionManager can't be started when system/secure_communication is enabled

Symptom

  • After SolutionManager's server reboot, ASCS instance of SolutionManager can't be started, in SAPMMC, the status of "msg_server.EXE" and "enserver.EXE" is "Running but not responding". 
  • Issue occurs when the following parameter has been set in profile, doesn't occur when the following parameter has been removed from profile and restarted SAP system. 

               ----------------------
               system/secure_communication = ON
               ----------------------

User would like to check if there is any other solution except deactivating the parameter system/secure_communication. 


Read more...

Environment

  • SAP Netweaver
  • ABAP Platform

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP S/4HANA all versions

Keywords

system/secure_communication; SSSLERR_NO_SSL_REQUEST; SapSSLSessionStartNB failed; running but not responding; ASCS; ASCS instance; SECUDIR; environment variable. , KBA , BC-CST-STS , Startup Service , BC-CST-MS , Message Service , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.