Hi @Robert Switala
The switchover of the application shouldn't actually cause a duplicated message server executable to spawn. During the switchover, the SCS simply switches the other application running in BACKUP mode to PRIMARY.
I have seen duplicate instances spawned when LCA couldn't get the PID of the existing application already running that is not connected to localhost LCA (to intimate its run mode). In such cases, LCA couldn't find any application running, and GA/GAX/SCI will show the application in a STOPPED state. Now, if someone starts the application from GA/GAX/SCI or via host services, then it could a new instance is started with a different PID.
Such scenarios can arise when,
- The two instances are launched by two different users on the host who do not have visibility into each other's application instances.
- The two instances have different command line arguments, with the dormant one usually connecting to an incorrect config server host or port. This causes the application executable to run in a loop trying to connect to the wrong config server and never actually starting up, yet the PID will be running. Without connecting to the config server, it cannot complete the startup sequence and cannot connect to localhost LCA.
If you could share the SCS, LCA logs, and the PID of both the message server instance via a support case, we can look into it and share a detailed analysis.
------------------------------
Vinod Balan
Staff Engineer | Genesys Engage Reporting & Analytics
------------------------------
Original Message:
Sent: 06-24-2025 13:51
From: Robert Switała
Subject: Duplicated services after switchover server Backup to Primary
Hello All,
After switchover for example Message server from Backup to Primary in SCI - I noticed in Windows server duplicated message service.
Is it possible?
#Platform/SystemAdministration
------------------------------
Robert Switała
------------------------------