arodriguezm
Member
Hello Everyone
First of all sorry to bother you again, there is something I don’t know how to solve with my experience so im reaching you.
The thing is that we are testing our RPA in the test machine which has the BPServer.exe running and the automate.exe instance to execute the processes in the scheduler. This scheduler works fine and if the server is running always there is no problem. BUT when I stop and re start the BPServer.exe (simulating a system reboot), the tasks in the scheduler are not executing. To make this tasks in the scheduler run again, I need to manually in blueprism control room make an update to the schedules with the server running at all times. I can end and restart the automate.exe instance any number of times as long as the server is running. So I think this is a BPServer related problem.
This is a problem because in a real environment, servers can be rebooted and they will be rebooted, as an automation we want the minimum of human participation as possible in the process. And with this problem a simple reboot will make the scheduler fail.
So my questions are if there is a configuration im missing, and why this is happening? Can it be solve?
Thanks a lot for your help.
First of all sorry to bother you again, there is something I don’t know how to solve with my experience so im reaching you.
The thing is that we are testing our RPA in the test machine which has the BPServer.exe running and the automate.exe instance to execute the processes in the scheduler. This scheduler works fine and if the server is running always there is no problem. BUT when I stop and re start the BPServer.exe (simulating a system reboot), the tasks in the scheduler are not executing. To make this tasks in the scheduler run again, I need to manually in blueprism control room make an update to the schedules with the server running at all times. I can end and restart the automate.exe instance any number of times as long as the server is running. So I think this is a BPServer related problem.
This is a problem because in a real environment, servers can be rebooted and they will be rebooted, as an automation we want the minimum of human participation as possible in the process. And with this problem a simple reboot will make the scheduler fail.
So my questions are if there is a configuration im missing, and why this is happening? Can it be solve?
Thanks a lot for your help.