SAP Knowledge Base Article - Public

2501871 - Diagnostics Agent does not start due to error 'Cannot connect to Message Server' in dev_jstart - Solution Manager 7.1/7.2

Symptom

The Diagnostics Agents does not start correctly and the dev_jstart shows the error:

F Fri <timestamp>
F  ********************************************************************************
F  Java environment properties (/usr/sap/DAA/SMDA98/work/jstart.jvm)
F    root directory    : /usr/sap/DAA/SMDA98/exe/sapjvm_6
F    vendor            : SAP AG
F    version           : 1.6.0_101
F    cpu               : amd64
F    java vm type      : server
F    java vm version   : 6.1.083 25.51-b02
F    jvm library name  : libjvm.so
F    library path      : /usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/amd64/server:/usr/sap/DAA/SMDA98/exe/sapjvm_6/jre/lib/amd64
F    executable path   : /usr/sap/DAA/SMDA98/exe/sapjvm_6/bin
F  ********************************************************************************
F    SAP extensions    : available
F  ********************************************************************************
I  [Thr 139776594798464] MtxInit: 30002 0 2
F  [Thr 139776594798464] *** WARNING => connection to Message Server not possible (j2ee/ms/host = , j2ee/ms/port = 36). [sfxxmsc.hpp  531]
F  [Thr 139776594798464] *** WARNING => connection to Enqueue Server not possible (j2ee/enq/host = , j2ee/enq/port = 32). [sfxxenc.hpp  194]
F  [Thr 139776594798464] *** LOG => Run level 0 completed.
F  [Thr 139776594798464] *** LOG => Instance state is "Instance terminated" (STOPPED @ 0, INACTIVE).
F  
F  ********************************************************************************
F  *** ERROR => Cannot connect to Message Server.
F  ***
F  *** Please see section 'Instance initialization issues'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************
F  
F  [Thr 139776594798464] *** LOG => exiting (exitcode -21000, retcode 2).

Environment

  • SAP Solution Manager 7.1 and 7.2
  • SAP Solution Manager Diagnostics Agent

Reproducing the Issue

  1. Open the Diagnostics Agent's dev_jstart log
  2. This KBA is applicable if the dev_jstart contains the error in the symptom section of this KBA

Cause

The 'system/type' property is either missing or wrongly configured. This causes the Diagnostics Agent to try to estabilish a connection to a non-exisitng message server 

Resolution

The 'system/type' property for the SMDAgent is configured in the DEFAULT.PFL, ensure that the DEFAULT.PFL exists correctly in the SMDAgent 'profile' folder:

  • <drive:>\usr\sap\<SID>\SYS\profile

On the host with the Diagnostics Agent that has the issue described in this KBA:

  1. Navigate to the folder <drive:>\usr\sap\<SID>\SYS\profile
  2. Open the file DEFAULT.PFL
  3. Check the  property system/type. It should have the value:
    system/type=SMDA
  4. Change the property system/type if necessary

Keywords

KBA , SV-SMG-DIA-SRV-AGT , Agent Framework , How To

Product

SAP Business ByDesign all versions