Process Engine service won't start, following 'MaxConcurrentProcesses' config alteration

Updated on December 9th, 2022

Table of Contents

X

Symptom

Following an alteration to the Process Engine configuration file, more specifically the ‘MaxConcurrentProcesses’ key, attempting to start the process engine service results in an error.

Potential Log File Errors:

2018-01-17 14:10:02,254 (-05:00) [6] ERROR Components.Misc.Logging.Logger - [ProcessEngineService, ValidateLicence] - Licence agent error - LicenceAgent: CONNECT failed

Components.Licensing.LicenceAgent.LicenceAgentException: Licence agent error - LicenceAgent: CONNECT failed

   at Components.Licensing.LicenceAgent.LicenceAgentBroker.HandleReturnCode(Int32 code)

   at Components.Licensing.LicenceAgent.LicenceAgentBroker.Initialise()

   at Services.ProcessEngine.Library.ContractImplementation.ProcessEngineService.ValidateLicence()

2018-01-17 14:10:02,269 (-05:00) [6] ERROR Components.Misc.Logging.Logger - [ProcessEngineService, OnStart] - Problem checking licence status. Licence agent error - LicenceAgent: CONNECT failed

Services.ProcessEngine.Library.ProcessEngineException: Problem checking licence status. Licence agent error - LicenceAgent: CONNECT failed

   at Services.ProcessEngine.Library.ContractImplementation.ProcessEngineService.ValidateLicence()

   at Services.ProcessEngine.Library.ContractImplementation.ProcessEngineService.Initialise()

   at Services.ProcessEngine.Hosts.WindowsService.ProcessEngineService.OnStart(String[] args)

Resolution

To resolve this issue it is necessary to first restart the Licence Manager service, then attempt to start the Process Engine service.

Was this article helpful?