Hi Vikram
It seems like there might be another version of your listener file initiated somewhere in the background. It can happen often if there are other users logging in/out of a machine regularly. You can set the listener file to kill any other instances of the listener before it starts to prevent this from being an issue.
The listener file should look something like this:
FOR /F "tokens=1,2,*" %%a IN ('TASKLIST /v /FI "ImageName eq Automate.exe"') DO TSKILL %%b
"C:\Program Files (x86)\Blue Prism Limited\Blue Prism Automate\Automate.exe" /resourcepc /public /dbconname "PROD ENVIRONMENT"
This will look for any tasks with the name automate.exe, terminate it then launch your new listener instance.
Hope this helps 🙂
------------------------------
Michael ONeil
Technical Lead developer
Everis Consultancy
Europe/London
------------------------------