- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
26-03-20 09:28 PM
Hello everyone,
I am trying to use the BluePrism Control Room to start a process, however every time I drag and drop the process to the Resource PC, this error pops ups : "Not Connected "XXXX" can't start process"
The resource PC is in IDLE status with No Session.
The Blueprism Server is up and running.
Thanks in advanced !
------------------------------
Rafael Fernandes
------------------------------
Answered! Go to Answer.
Helpful Answers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
19-08-20 08:02 AM
I managed to "resolve" this error by simply restarting my resource machine and then it connected successfully again.
What exactly fixed it by restarting, I unfortunately have no idea about, but at least it solved the problem.
Hopefully this helps you as well!
------------------------------
Jesper Bruun Hansen
Management Consultant
Implement Consulting Group
Europe/Copenhagen
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
27-03-20 10:50 AM
------------------------------
PS Support
PS Support Account for all of Professional Services
Blue Prism
Europe/London
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
27-03-20 12:00 PM
Hello,
Yes, i have checked the Resource PC and it is running. Also, the icon is Blue.
------------------------------
Rafael Fernandes
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
27-03-20 05:05 PM
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\Automate.exe" /resourcepc /public
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
27-04-20 05:59 PM
In the Control Room on my App Server, I see my ressource as State: Idle, but Connection: Not Connected. When I log out I see the icon change to the locked/key icon as expected, but the connection is still Not Connected.
When I run the script as you mention @John Carter on my resource pc, a small window appears logging the following:
[2020-04-27 18:44:48Z] Initialising (events logged in Romance Standard Time)
[2020-04-27 18:44:48Z] ..checking connection 'BP-PROD'
[2020-04-27 18:44:48Z] ..connected to 'SRV-BPAPP01'
[2020-04-27 18:44:48Z] ..initialising AMI
[2020-04-27 18:44:48Z] Activity log set to log externally
[2020-04-27 18:44:48Z] Startup sequence complete
[2020-04-27 18:44:48Z] Listener started.
I see "Active Connections": 0, Port 8181, Running Processes - 0 + 0 pending.
Any ideas on what might be causing this problem?
I'm running BP v.6.7.1 on both ressource and App Server btw.
------------------------------
Jesper Bruun Hansen
Management Consultant
Implement Consulting Group
Europe/Copenhagen
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
18-08-20 09:17 PM
he only other piece of information I can add is that for the resource I'm having this issue on I did include SAS services and did enable/turn on the first option for SAS when installing. I wish I captured or could remember this specific option.
Anyway, any insight or feedback would be appreciated.
------------------------------
Paul Robinson
Solutions Creator
National Grid
America/New_York
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
19-08-20 08:02 AM
I managed to "resolve" this error by simply restarting my resource machine and then it connected successfully again.
What exactly fixed it by restarting, I unfortunately have no idea about, but at least it solved the problem.
Hopefully this helps you as well!
------------------------------
Jesper Bruun Hansen
Management Consultant
Implement Consulting Group
Europe/Copenhagen
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-11-20 05:12 PM
Were you also able to resolve your issue also by a restart? I tried restarting but i still get exactly the same error. I upgraded from 6.5.0 to 6.7.3. Another of my resource is working fine.
------------------------------
Prashant
Software Engineer
IMF
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
23-06-22 11:39 AM
------------------------------
Dinesh Kumar Mathireddi
------------------------------
