2237710 - SUM:WAIT-AS-JAVA-START - SSSLERR_BAD_SRVNAME

Software Update Manager (SUM) is used for upgrade/update and error such as the following can be found in the WAIT-AS-JAVA-START phase of SUM as:

LOG FILE PATH : /<SUM Dir>/sdt/log/SUM/WAIT-AS-JAVA-START_XX.LOG
___
  [Info  ]:   Command line: F:\usr\sap\<SID>\J<nr>\exe\sapcontrol -nr 0 -host <hostname> -user <sidadm> <SecureField> -prot NI_HTTPS -function GetSystemInstanceList 
  [Info  ]:   Standard out: F:\SUM\SUM\sdt\log\SUM\SAPCONTROL_GETSYSTEMINSTANCELIST_0_XX.OUT
  [Info  ]: Process ID 1, name sapcontrol has been finished, exit code 1.
  [Error ]: Error getting the status of the instance with number 0 on host com.sap.sdt.tools.sapcontrol.SAPControlException: Sapcontrol client could not perform action get system instances list on instance 0
  Return code condition success evaluated to false for process sapcontrol for action get system instances list.
  [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not check status of SAP instance with number 0.
  Error getting the status of the instance with number 0 on host <hostname>.
  Sapcontrol client could not perform action get system instances list on instance 0
  Return code condition success evaluated to false for process sapcontrol for action get system instances list.
___

SAPCONTROL_GETSYSTEMINSTANCELIST_0_XX.OUT throws traces of error as
---
GetSystemInstanceList
FAIL: SSSLERR_BAD_SRVNAME (WSATYPE_NOT_FOUND: The specified class was not found.), SapSSLSetSessionParam failed in plugin_fopen()
---

-Upgrade/Update using SUM tool.
-Kernel 740/741

SSSLERR_BAD_SRVNAME, SapSSLSetSessionParam, plugin_fopen, WSATYPE_NOT_FOUND, com.sap.sdt.tools.sapcontrol.SAPControlException, Sapcontrol , KBA , BC-UPG-TLS-TLJ , Upgrade tools for Java , BC-SEC-SSL , Secure Sockets Layer Protocol , Problem