2473880 - ENQU: RAISE_EXCEPTION dump with CONNECT_TO_ENQ_SERVER_FAILED

Symptom

The following symptoms appear on system:

In ST22 show RAISE_EXCEPTION dumps on transaction with CONNECT_TO_ENQ_SERVER_FAILED exception.
In SM21 the entries can be observed as

<TIME> <instance name> DIA  <WP> 000 <USER>                 GI  0 Error calling the central lock handler

<TIME> <instance name> DIA  <WP> 000 <USER>               GI    4 > Dequeue All call failed

When checking in related work process trace files (dev_w*) , the entries can be seen as

E  *** ERROR => EnsaCliDoRequest: DoRequest failed (rc=107): 436 bytes on con. 0 in layer 0 (EncCli) (1/0) [ensacli.c    406]
E  {root-id=16AEF4B5AD471ED7AECFEE96B5C30027}_{conn-id=00000000000000000000000000000000}_0

E  *** ERROR => ENSA_Connect(): AlHARegisterComponent() failed with error 254 [ensaclnt.c   1100]
E  {root-id=16AEF4B5AD471ED7AECFEE96B5C30027}_{conn-id=00000000000000000000000000000000}_0

E  *** ERROR => EncCliIConnect: failed to connect to enqueue server at <instance name where ENQ is running> through layer EncCli (rc=-3) [enccli.c     1084]
E  {root-id=16AEF4B5AD471ED7AECFEE96B5C30027}_{conn-id=00000000000000000000000000000000}_0

E  *** ERROR => EncCliReq: failed to connect to server [enccli.c     507]
E  {root-id=16AEF4B5AD471ED7AECFEE96B5C30027}_{conn-id=00000000000000000000000000000000}_0

OR


E *** ERROR => ENSA_CommInit: failed to connect to server at <host>/<service> through layer EncCli (rc=7) [ensaclnt.c 764]

M  *** ERROR => SecuSSL_SessionStartNB(): incomplete SSL handshake [ssslsecu.c   4955]
M  {root-id=5489F7880C7B0B20E10080000A96551F}_{conn-id=5F5E41FBFC18375CE10000000A61121D}_1
M  *** ERROR => NiISSLStartOnClientConn: SapSSLSessionStartNB failed (-10, SSSLRC_CONN_CLOSED) [nixxi.cpp    10898]
M  *** ERROR => EncNiConnect: failed initialization of SSL connection (rc=-30 => NIESSL_CONN_CLOSED) => closing connection (see SAP note 1943531) [encomi.c     506]

E  *** WARNING => EncCliIConnect: protocol error when connecting to enqueue server at <instance name where ENQ is running> through layer EncCli (rc=-3) [enccli.c     1076]

E  *** WARNING => EncCliIConnect: check the configuration of the enqueue server [enccli.c     1078]

E  *** WARNING => EncCliReq: failed to connect to server (see SAP note 1943531) [enccli.c     507]
E  *** ERROR => EnsaCliDoRequest: DoRequest failed (rc=107): 376 bytes on con. 0 in layer 0 (EncCli) (1/1) [ensacli.c    408]
E  *** ERROR => ENSA_DoRequest(): Error 7 returned from EncCliReq() [ensaclnt.c   1393]
E  *** ERROR => Enqueue: ENSA_DoRequest() errror 8 [enxxhead.c   3155]

It can happen to entire system or few affected instances.

Environment

SAP NetWeaver release independent.

Product

SAP NetWeaver all versions

Keywords

SM12 ,rdisp/wp_no_enq ,enque/serverhost ,enque/process_location , GI 0 ,Error calling the central lock handler , GI 4 , Dequeue All call failed , EnsaCliDoRequest: DoRequest failed , (EncCli) (1/0) , ENSA_Connect(): AlHARegisterComponent() failed with error 254 , EncCliIConnect: failed to connect to enqueue server , EncCli (rc=-3) , EncCliReq: failed to connect to server , EnsaCliDoRequest: DoRequest failed (rc=107) , Classical integrated enque server , SAP Netweaver, dialog instance, enque server , profile ,Lock management operation mode , Internal lock management in same work process , KBA , BC-CST-EQ , Enqueue , BC-CST-DP , Dispatcher, Task Handler , 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.