Retour
-
Titre
Why does the "Service Name" of a Windows 5.8.1 FglAM have to be set to "FglAM" in order for the FglAM to shut down? -
Description
When the service for a 5.8.1 FglAM is created with the "sc create" command and "FglAM" is not used as the service name the FglAM does not shut down when one attempts to stop it. -
Cause
The following "sc create" command was used to create the service with the service name "FglAM". The problem occurs when "FglAM" is not used as the argument passed to " sc create" as the service namesc create FglAM binpath= '\"C:\Quest_Software\Foglight_Agent_Manager\bin\fglam.exe\" --manager-start-service' DisplayName= "Foglight Agent Manager" start= auto -
Résolution
In order for the FglAM launcher to be able to control the service, it needs to know what it is configured service-name is. This value is defined as part of the FglAM configuration, and is used by the launcher when it creates (via fglam.exe --install-service) or removes (fglam.exe --remove-service) the service.When registering the FglAM install as a service directly via the Windows 'sc' process, you must use the same service name that FglAM would have used if the "--install-service" option was used. If you choose something different to register the service name under and you later ask the FglAM process to stop the service; it expects that the service-name is 'FglAM' and it tries to stop that service. It has no idea that the service it is supposed to be able to control was registered by another process and gave it an arbitrary name.