Blue Prism has stopped working while starting as runtime resource
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-04-20 06:36 AM
Hi ,
After successfully configuring a run time resource to a DB where no SSO enabled , tried configuring a runtime to a DB connection with sso enabled and facing issues . Problem I am facing is sometimes when the resource pc startup script runs , Resource PC comes up and closes saying Blue Prism has stopped working
Run time resource script used
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\automate.exe" /resourcepc /public /port 8200 /sso
Multiple Errors from event Logs in BP v6.2
The communication object, System.ServiceModel.Channels.ReliableRequestSessionChannel, cannot be used for communication because it is in the Faulted state.
Sometimes there is no issue , sometime issue comes up , Any help will be appreciated
------------------------------
Nighil Tom
Senior Analyst, Automation | NSW Department of Education | nighil.tom@det.nsw.edu.au | education.nsw.gov.au
------------------------------
After successfully configuring a run time resource to a DB where no SSO enabled , tried configuring a runtime to a DB connection with sso enabled and facing issues . Problem I am facing is sometimes when the resource pc startup script runs , Resource PC comes up and closes saying Blue Prism has stopped working
Run time resource script used
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\automate.exe" /resourcepc /public /port 8200 /sso
Multiple Errors from event Logs in BP v6.2
The communication object, System.ServiceModel.Channels.ReliableRequestSessionChannel, cannot be used for communication because it is in the Faulted state.
Sometimes there is no issue , sometime issue comes up , Any help will be appreciated
------------------------------
Nighil Tom
Senior Analyst, Automation | NSW Department of Education | nighil.tom@det.nsw.edu.au | education.nsw.gov.au
------------------------------
Nighil Tom
Senior Analyst, Automation | NSW Department of Education | nighil.tom@det.nsw.edu.au | education.nsw.gov.au
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-04-20 09:49 AM
You can't use the same DB for both native and AD authentication. You have to choose the authentication method when you create the DB and after that it cannot be changed.
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-04-20 04:22 PM
Agreed with John's solution.
------------------------------
Md Afaque Ahmad Rahmani
Senior Consultant
Ernst & Young
Asia/Kolkata
------------------------------
------------------------------
Md Afaque Ahmad Rahmani
Senior Consultant
Ernst & Young
Asia/Kolkata
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-04-20 07:40 AM
Thanks for the reply John . Both are different DBs investigation till now , have found the issue mostly happens when connection is made via a load balancer url and stays stable when direct app server connection is mentioned
------------------------------
Nighil Tom
Senior Analyst, Automation | NSW Department of Education | nighil.tom@det.nsw.edu.au | education.nsw.gov.au
------------------------------
------------------------------
Nighil Tom
Senior Analyst, Automation | NSW Department of Education | nighil.tom@det.nsw.edu.au | education.nsw.gov.au
------------------------------
Nighil Tom
Senior Analyst, Automation | NSW Department of Education | nighil.tom@det.nsw.edu.au | education.nsw.gov.au
