3056794 - setuphadr fails at companion host due to running repsrvr, dbltm, dbsrv17 processes detected - SAP SRS

• While running setuphadr at companion host with OS windows 2019, Japanese language locale, below error shows up in setuphadr.log:
  ****************************
  (SQL command) sap_pre_setup_check dr, PRIM, COMP
  ...omitted
  ...omitted
  DiagnoseEnvironment Task End Tue May 11 10:32:58 JST 2021
  DiagnoseEnvironment Hostname host1
  ValidateLocalDREnv Task Name Validate Local Disaster Recovery Environment
  ValidateLocalDREnv Task State Error
  ValidateLocalDREnv Short Description Verify that the local environment is setup and ready for disaster recovery replication setup to run.
  ValidateLocalDREnv Failing Command Error MessagePRIM - Replication Server - The Replication Server process [Program: 'repsrvr.exe', PID: '???p???????C???X?^???X?????????????B'] is still running. The existed Replication Server related processes running from the same installation directory of Replication Server instance to create will cause the new Replication Server instance can not be started.
  PRIM - Replication Server - The Replication Server process [Program: 'dbsrv17.exe', PID: '???p???????C???X?^???X?????????????B'] is still running. The existed Replication Server related processes running from the same installation directory of Replication Server instance to create will cause the new Replication Server instance can not be started.
  PRIM - Replication Server - The Replication Server process [Program: 'dbltm.exe', PID: '???p???????C???X?^???X?????????????B'] is still running. The existed Replication Server related processes running from the same installation directory of Replication Server instance to create will cause the new Replication Server instance can not be started.
  ...omitted
  ...omitted
  ValidateLocalDREnv Failing Command Error MessageCOMP - Replication Server - The Replication Server process [Program: 'repsrvr.exe', PID: '???p???????C???X?^???X?????????????B'] is still running. The existed Replication Server related processes running from the same installation directory of Replication Server instance to create will cause the new Replication Server instance can not be started.
  COMP - Replication Server - The Replication Server process [Program: 'dbsrv17.exe', PID: '???p???????C???X?^???X?????????????B'] is still running. The existed Replication Server related processes running from the same installation directory of Replication Server instance to create will cause the new Replication Server instance can not be started.
  COMP - Replication Server - The Replication Server process [Program: 'dbltm.exe', PID: '???p???????C???X?^???X?????????????B'] is still running. The existed Replication Server related processes running from the same installation directory of Replication Server instance to create will cause the new Replication Server instance can not be started.
  ValidateLocalDREnv Hostname host2
  2021-05-11 10:32:58 エラー: RMA の設定...失敗
  ****************************

• RMA log from both PRIM and COMP site contains below error message:
  ****************************
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [ConnectionManager ] - ConnectionManager: Create connection failed java.sql.SQLException: JZ006: IOException が検出されました: java.net.ConnectException: Connection refused: connect (local port xx to address xxx, remote port xx to address xxx (host2)).
  [TRACE] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - Testing port availability: Socket is closed, port number 4905
  [TRACE] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - Testing port availability: Socket is closed, port number 4906
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - Execute PS command: '[C:\Windows\System32\wbem\wmic.exe, process, where, "name='repsrvr.exe', and, ExecutablePath='Fakepath\\repsrvr.exe'", get, processid]'.
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - Output of the PS command are following:.
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - ???p???????C???X?^???X?????????????B
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - Execute PS command: '[C:\Windows\System32\wbem\wmic.exe, process, where, "name='dbsrv17.exe', and, ExecutablePath='Fakepath\\dbsrv17.exe'", get, processid]'.
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - Output of the PS command are following:.
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - ???p???????C???X?^???X?????????????B
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - Execute PS command: '[C:\Windows\System32\wbem\wmic.exe, process, where, "name='dbltm.exe', and, ExecutablePath='Fakepath\\dbltm.exe'", get, processid]'.
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - Output of the PS command are following:.
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [DREnvUtils ] - ???p???????C???X?^???X?????????????B
  [ERROR] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [ValidateLocalDREnv ] - Task Validate Local Disaster Recovery Environment - Failed with error message - host2 - Replication Server - The Replication Server process [Program: 'repsrvr.exe', PID: '???p???????C???X?^???X?????????????B'] is still running. The existed Replication Server related processes running from the same installation directory of Replication Server instance to create will cause the new Replication Server instance can not be started.
  host2 - Replication Server - The Replication Server process [Program: 'dbsrv17.exe', PID: '???p???????C???X?^???X?????????????B'] is still running. The existed Replication Server related processes running from the same installation directory of Replication Server instance to create will cause the new Replication Server instance can not be started.
  host2 - Replication Server - The Replication Server process [Program: 'dbltm.exe', PID: '???p???????C???X?^???X?????????????B'] is still running. The existed Replication Server related processes running from the same installation directory of Replication Server instance to create will cause the new Replication Server instance can not be started.
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [ValidateLocalDREnv ] - Task Validate Local Disaster Recovery Environment - State - Error
  [INFO ] [RMI TCP Connection(5)-IP xx.xxx.xx.xxx][RMA] - [ConnectionManager ] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:host2:5000/master'.
  ****************************

• Tasklist shows no running PID like repsrvr.exe, dbltm.exe, dbsrv17.exe.

• Also a manual check via below commands will return outputs in Japanese language, meaning "No Instances Available" in English
  C:\Windows\System32\wbem\vmic.exe process where "name='repsrvr.exe' and ExecutablePath='Fakepath\\dbsrv17.exe'" get processid
  C:\Windows\System32\wbem\vmic.exe process where "name='dbsrv17.exe' and ExecutablePath='Fakepath\\dbsrv17.exe'" get processid
  C:\Windows\System32\wbem\vmic.exe process where "dbltm.exe' and ExecutablePath='Fakepath\\dbsrv17.exe'" get processid

• SAP Adaptive Server Enterprise (ASE) 16.0 with Always-on Option (HADR)
• SAP Adaptive Server Enterprise (ASE) 16.0
• SAP Replication Server (SRS) 16.0
• Windows 2019 with Japanese language

vmic.exe, repsrvr, dbltm, dbsrv17, ExecutablePath, CR824808, 824808, CR 824808 , KBA , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , Product Enhancement