Resource pc looks offline

Hi All ,

I was facing issue/error on control room > availble resource section "Resource pc looks offline" . After that I have logout and relogin Blueprism Server and Resource PC come back to online . But I want to know what is reason behind this issue and what is resolution ( it may be multiple resolution)

Please provide help.

Thanks
Vimal

Hi Vimal.
There is a setting under System--> Setting in BP as (Start a personal run time resource on this machine when users sign in to blue prism) and by default this is checked, which means only when some body login to BP resource pc will be available else it will be in Offline.

you can un check this setting and run the below command from command prompt to launch resource pc even BP is not logged in.

C:\Program Files\Blue Prism Limited\Blue Prism Automate\Automate.exe /resourcepc /public

Regards,
Siraz.

Hi,
My resource PC oalways used t show connected once I log in to blueprism. Now it suddenly shows disconnected even if I am logged in. If I ping my PC , I can see it connected but I am not able to use it as it is "offline" in Blueprism.
I have also tried logging off and relogging in , but no helps.
Please suggest

RPA_Automation said:

Hi,
My resource PC oalways used t show connected once I log in to blueprism. Now it suddenly shows disconnected even if I am logged in. If I ping my PC , I can see it connected but I am not able to use it as it is "offline" in Blueprism.
I have also tried logging off and relogging in , but no helps.
Please suggest

Click to expand...

Hi,

I have the same problem, Did you manage to fix it?

Hi, sometimes it happened also to our PC. We are creating BAT file to connect the resource PC again. Basically the BAT file is to run this file C:\Program Files\Blue Prism Limited\Blue Prism Automate\Automate.exe .

I hope it solved your problem

Are you trying to run Blue Prism on an interactive client and also make that machine a runtime resource? If so, I don't believe that is possible. As for a disconnected runtime resource, @MariaChristy's BAT file solution, when run on the runtime resource directly, will restore the connection. Just remember to close any existing runtime that is running on that machine first.