Scheduler - Timed out waiting for valid connection

[Daniel_JebarajJ]

Hi, I have scheduled a process in Lower environment (DEV) and the same in Higher environment (PROD). In DEV, the scheduler works properly, but it fails with the following error message in PROD (while checking the scheduler log). "Resource XXXXXXXX : Timed out waiting for valid connection" If I manually drag the process to a resource in the control room, the process runs fine. But fails to kick off if I schedule the same process on the same resource. Please refer to the attached image. I have verified that all the scheduler settings in Blue Prism are the same for both the environments. Can Somebody please help me out finding a solution for this?

[Denis__Dennehy]

Behind the scenes manually starting in control room is a direct telnet/tcp command between your pc and the production resourcepc. However, behind the scenes schedules are started off by a direct telnet/tcp command between the application server rand the production resourcepc. The next thing for you to investigate therefore is your connectivity between the application server and the resourcepc.

[CKOMORO]

Hey do you have a solution for this Problem? i have the same Problem.

[Carl__Carter]

I see this problem pretty regular. I've completed all relevant connectivity tests, but still unable to find the cause of this problem. A restart of the Application Server service resolves this for me.

[SørenCarlsen]

I can confirm that restarting the Application Server worked for my team aswell. We been through several troubleshooting steps before hand, but this did the trick! Thanks a bundle! =) /Søren

[ryanamiller]

I'm having this issue as well, are you on 5.0.32.0? I agree, that a restart of the App server and relevant Resource Machines resolves the issue, but it seems to happen on a weekly basis. Wondering if there's a root cause, or a known Blue Prism bug with this version.

[LintoThomas]

Retart of the application server did the trick for us as well. Support Execitives of my team is mulling over the idea of having the Application Server weekly identifying the low/nill load time.

[AlexanderBopp]

Hi all, we faced this same issue and were looking for couple of days how to fix (without restart). In the end a simple trick helped: - setting the resource to “retired” in „System Manager“ > „Resources“. - starting the startup script results now fairly with the message: Listener failed : Unable to register with the database - Cannot register resource PC xxxx because it has been retired - now activate the resource again in System Manager and restart the startup script. Afterwards the Scheduler was able again to connect to the resource PC. As this changes nothing on the resource it seems like a bug with the Scheduler. It would be appreciated if Blue Prism can fix this problem. best regards

[Carol.Ouellet · Accepted solution]

Hello, Having to create an RFC every time we need a reboot is not really convenient so we tried Alexander Bopp's work around and it worked very well. Terminate automatec.exe on the resource Retired the resource Waited a few seconds Un-retire I hope Blue Prism is working on fixing this issue though. thanks Carol

[SunilSharma]

I have similar problem and restarted the machine couple of times, still it doesn work.

------------------------------
Sunil Sharma
Senior Consultant
EY
America/Toronto
------------------------------