Has Blue Prism provide any solution to anybody? New Login Agent has not solved the problem and error ""Session creation failed on resource 'RESOURCE': Failed to create session on Resource - No reply from Resource PC"" still occurs multiple times per hour.
We have been able to reproduce this error with multiple combinations including different OS (2012R2, 2016, 2019), Blue Prism versions (5, 6.2.1, 6.3), connection types (WCF, .NET), platforms (Hyper-V, Azure, Vmware) and different ports for login agent.
Our investigation appoints that the problem exists with Blue Prism scheduler as it cant handle the load which can be reproduced with under 10 runtime resources.
Yesterday we upgraded our pre-production environment to 6.3 version and for the first time we have faced this error.
The runtime resource is configured to start a runtime process automatically when a windows user logs in (to run processes by connecting with login agent). But, as a PRE machine, developpers are allowed as well to log in and start Control Room to develop and schedule processes.
I guess that the problem is related when scheduling a process and there's a Control Room session running in the same machine.
Just to update for you all.
We have been working with Blue Prism to resolve this problem as it has been identified. The problem exists (usually) when you have more than 5 runtime resources which are doing login-do the tasks-logout multiple times a day. If you are doing login on the morning and logout on the evening, you probably don't have this problem.
It would be nice if Blue Prism itself would update this thread, but we, in Digital Workforce, hope that the fix will be released in this month as we are already testing versions which includes it.
Thanks for the update Jvekka
We only got one running runtime resource.
Its correct that logout in the evening and in the morning is working, but we need to do it manually from the control room.
Hello all.
We are working on version 6.3 and facing same issue with the scheduler. Thanks to jvekka for giving some tips that could help. I have just removed logouts after each task, so now all the logouts will be done at the end of day. Hope it helps.
In a meantime - did anybody check if the latest release (6.3.1) fixes the problem? This is really annoying that it takes so long for BP to resolve such critical issue...
Out of curiosity, have you tried connecting the resources to the DB instead of the controller? Despite what BP Support has told us on the phone, we're getting full functionality out of this solution and have had no issues with login agent-controlled VMs.
To clarify, BP Support has told us that this solution will not support scheduling or encryption. We use both, going directly to the SQL server. I have also configured an environment going through the controller, and have noticed no difference in functionality. (Just that the controller pass-through is slower.)
We are also having the same problem where we are able to run the process through Control Room, but same process won't run through the scheduler. It will fail after 'x' number of retries. Please let me know if someone has a viable solution, we are on 6.3.1.