- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-05-24 01:45 PM
Hi All,
When we are configuring to blue prism RT machines getting SOAP Authentication error in windows 2019 server. Please help me to resolve error.
Answered! Go to Answer.
Helpful Answers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
16-05-24 02:24 PM
We documented how to resolve that in the following KB Article (LINK HERE). That issue happened after an update from Microsoft and is required to set the SPN on the Blue Prism server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-05-24 03:15 PM
Could you give more context on this error please? When does it show up exactly?
Can you provide a screenshot?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-05-24 03:42 AM
Hi @asilarow
Thanks...,
please find below screen shot. Below error we are getting, connecting RT machine to app server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-05-24 10:31 AM - edited 10-05-24 10:32 AM
This means that your server is using the SOAP protocol for authentication, and your SOAP authentication headers sent from the resource machine are not valid.
You should configure your resource machine connection settings to match those on the server:
You can find more details on this topic here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
14-05-24 08:39 AM
we are able to connect app server.
We configured as per the document but we are getting soap error in RT machines.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
15-05-24 10:27 AM - edited 15-05-24 10:28 AM
I think this issue lies in the server set up, the server will be running but the callback protocol will likely be the issue preventing the application from connecting to it. If log into the application server and you go to the folder BP is installed in and open the BPServer e.g. C:\Program Files\Blue Prism Limited\BPServer.exe
When this opens select edit and then select the ASCR Settings tab and in here you will need to change the callback protocal to gRPC and in the Binding settings under Hostname you need to add your server name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
16-05-24 02:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
16-05-24 02:24 PM
We documented how to resolve that in the following KB Article (LINK HERE). That issue happened after an update from Microsoft and is required to set the SPN on the Blue Prism server.