Runtime Resource Problem - Listener Failed : Unable to Start Listener
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
27-04-18 04:32 PM
Hi, Wondering whether anyone has had this issue, I've searched the forum and not turned up any threads.
We recently rebuilt a PC which was being used by a Process Admin as a resource PC and configured it to be a Runtime Resource. Since then it fails to report back in after the login has run. The batch file runs and launches automate with the parameters but the automate resource pc window shows the following error.
Listener Failed : Unable to Start Listener - is this machine already running as a Resource PC? : Only one usage of each socket address (protocol/network address/port) is normally permitted
The machine has been rebuilt several times and the same issue appears which would suggest something needs to be addressed on the app server or DB.
Any ideas?
Thanks,
Steve
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-05-18 06:13 PM
Knowledgebase article: https://portal.blueprism.com/customer-support/knowledge-base/error-unable-start-listener-when-running-resource-pc-command-line
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-06-18 08:07 PM
I too face similar issue while connecting VM from Blue Prism. Manually if we connect to VM and exit the Resource PC and run the ResourcePC bat file, it runs successfully and can see in Control room as connected.
