topic RE: Scheduler Settings in Product Forum

Scheduler Settings

Vikram.R — Tue, 15 Dec 2020 06:06:00 GMT

Hi I am Vikram.R
I am facing an issue in scheduler settings due to which I am not able to schedule the process. I am getting an error like "Listener failed : Unable to start listener - is this machine already running as a Resource PC? : An attempt was made to access a socket in a way forbidden by its access permissions". Can anyone help me out with this problem.

Thanks and regards
Vikram.R

------------------------------
Vikram Ramesh, Programmar Analyst
------------------------------

RE: Scheduler Settings

PritamPoojari — Tue, 15 Dec 2020 08:28:00 GMT

Hi

It suggests that there is another instance of BluePrism running using the same port. Check in Task Manager if you see anything which instance of Blue Prism , maybe as another user on same machine.

------------------------------
Pritam Poojari
Solution Architect
Capgemini
Europe/London
------------------------------

RE: Scheduler Settings

NileshJadhavBP — Tue, 15 Dec 2020 16:20:00 GMT

Hi Vikram,

Please check below link..it will help you.

https://bpdocs.blueprism.com/bp-6-8/en-us/Guides/Installing/typical-bp-application-server.htm?Highlight=start%20listener

Thanks

------------------------------
Nilesh Jadhav
Senior RPA Specialist
ADP
India
------------------------------

RE: Scheduler Settings

Vikram.R — Wed, 16 Dec 2020 04:12:00 GMT

No, I have closed all the instances, and when I tried to run from the command prompt

------------------------------
Vikram Ramesh
------------------------------

RE: Scheduler Settings

johnwild — Wed, 16 Dec 2020 16:04:00 GMT

Check your firewall settings.

I had the same issue caused by automate.exe being blocked by Windows Firewall.

------------------------------
John Wilding
Robotic Architect
ReAssure Ltd
Europe/London
------------------------------

RE: Scheduler Settings

michaeloneil — Wed, 16 Dec 2020 16:13:00 GMT

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
------------------------------