2203294 - "ThSysAdmMsg: bad server name" in dev_w*

• The following trace is shown in dev_w*

  M  *** ERROR => ThSysAdmMsg: bad server name >[hostname_SID_Instance-Number]

• Sometimes, an ABAP stack will be shown after the above trace, for example

  M  *** ERROR => ThSysAdmMsg: bad server name >[hostname_SID_Instance-Number]     < [thxxab.c     10206]  
  M
  M  ABAP-Stack at ThSysAdmMsg
  M  -------------------------
  M  1: TH_SEND_ADM_MESS of program SAPLTHFB (Function)
  M  2: GET_CURRENT_WPS_FROM_SERVER of program SAPLSPF1 (Form)
  M  3: RZL_GET_BA_LIST of program SAPLSPF1 (Function)                         <====
  M  4: GET_OPMODE_LIST of program RSRZLST0 (Form)
  M  5: UPD_DUMMYBA of program RSRZLST0 (Form)
  M  6: PERF_EXT_FORM_SINGLE of program SAPMSSY6 (Form)
  M  7: AUTO_ABAP of program SAPMSSY6 (Form)
  M  8: PBO_1100 of program SAPMSSY6 (Module)

• Release 702 SAPKB70201 - SAPKB70224
  Release 731 SAPKB73101 - SAPKB73130
  Release 740 To SAPKB74027
  Release 750 To SAPK-75023INSAPBASIS
  Release 751 To SAPK-75114INSAPBASIS
  Release 752 To SAPK-75210INSAPBASIS
  Release 753 To SAPK-75308INSAPBASIS
  Release 754 To SAPK-75406INSAPBASIS
  Release 755 To SAPK-75504INSAPBASIS
  Release 756 To SAPK-75601INSAPBASIS

   

ThSysAdmMsg, bad, server name, instance name, operation mode, opmode, TH_SEND_ADM_MESS, RZ12, shutdown, inactive application servers , KBA , BC-CST , Client/Server Technology , BC-CCM-CNF-OPM , Operation Modes , Problem