topic I see this problem pretty in Product Forum

Scheduler - Timed out waiting for valid connection

Daniel_JebarajJ — Fri, 28 Apr 2017 13:41:00 GMT

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?

Behind the scenes manually

Denis__Dennehy — Fri, 28 Apr 2017 19:50:00 GMT

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.

Hey do you have a solution

CKOMORO — Wed, 31 May 2017 19:51:00 GMT

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

I see this problem pretty

Carl__Carter — Tue, 06 Jun 2017 01:44:00 GMT

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.

I can confirm that restarting

SørenCarlsen — Wed, 20 Sep 2017 16:16:00 GMT

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

I'm having this issue as well

ryanamiller — Tue, 26 Sep 2017 18:20:00 GMT

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.

Retart of the application

LintoThomas — Wed, 27 Sep 2017 14:26:00 GMT

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.

Hi all,

AlexanderBopp — Mon, 02 Oct 2017 23:27:00 GMT

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

Hello,

Carol.Ouellet — Tue, 05 Dec 2017 00:57:00 GMT

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

RE: I see this problem pretty

SunilSharma — Wed, 31 Jul 2019 16:14:00 GMT

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

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

RE: Hi all,

ChetnaAgarwal — Mon, 28 Sep 2020 22:12:00 GMT

Hi Alex,

Trick you provided worked for me and saved my time from restarting Production server and business loss. Thank you so much.

------------------------------
Chetna Agarwal

------------------------------

RE: Hi all,

Walter.Koller — Wed, 10 Nov 2021 11:51:00 GMT

Thanks for posting the workaround.
We recently upgraded from 6.4 to 6.9 and since then we had two cases when resources rejected any schedule with the 'waiting for valid connection' error.

------------------------------
Walter Koller
Solution Manager
Erste Group IT International GmbH
Europe/Vienna
------------------------------

RE: Hello,

AlexanderBopp — Tue, 04 Oct 2022 15:47:00 GMT

Happy to see that the workaround helped at least in some cases! Meanwhile we are on BP v6.10 and I just faced the same issue with a user. Two machines timed out waiting for valid connection, hence the Schedule did not trigger the bots anymore.
I was really hoping for this to be fixed and now even this workaround does not seem to help in this case.

------------------------------
Alexander Bopp
Business Automation Engineer
Credit Suisse AG
Europe/Zurich
------------------------------