Not able to run any process from control room

[ritansh.jatwani]

Hi All,

We are trying to setup the infrastructure of Blue prism for a client and we have almost completed everything. While performing the testing, we have identified that we are not able to run any process from control room.

We don't have access to runtime resources and only IT folks can login and do the required configuration/changes. For running listener on runtime resource, we have asked IT people to login to the machine and run the listener from their account and then disconnect from the machine (not logging off from the machine). We have also setup a task scheduler to run the listener in case, the machine gets restarted. 

Now, our query is what could be the possible cause of process getting terminated from the control room?

None of the developers have access to the runtime resources and neither we have any bot accounts created for the environment (non-prod environment). For running a process from the control room, does the developer should have access to runtime?

Or there could be some configuration issue? Is there something which we are missing?

When we tried running the process, launching of application is happening (as verified by IT folk from the task manager) but post that nothing is happening. It seems the blue prism is unable to identify the launched application and hence failing every time.

Note- we are using BP version 7 but have configured it the same way like BP version 6.

[henrynli]

Hi Ritansh,

Not sure if you have tried disabling firewall on the Interactive Console machine you are connected and if you can set up a local RR on the same machine for testing.

There is a document guiding how to do Connectivity test if you have access to BP Portal....make use of that document and follow all the steps you should be able to identify issues.

Henry

[Walter.Koller]

Unfortunately I cannot figure out what the actual issue is you are facing?

What do you mean with 'listener'?
Did you follow the enterprise installation guides? (if so you would not need someone to start anything manually)
Did you follow the recommended way on remotely connecting to runtime resources? (do not use RDP, Windows Remote Desktop)
Do you want to start processes directly (drag&drop to runtime resource) or as Schedule?
Do processes start but terminate (what error message?) or are they rejected right away?
What is the status of the runtime resource shown in Control?