11-11-20 08:16 AM
Client is unable to finish the security negotiation within the configured timeout (00:00:00). The current negotiation leg is 1 (00:00:00)
I checked the below link trying to resolve the problem but we don't use Proxy settings so this should not be the problem:
Support Center | Blue Prism Portal
What is strange that after we restart the machine there is a high chance that the listener will start without any problem.
Anybody has an idea what should be checked in our system?
Kind regards,
Gyula
15-11-20 11:24 PM
This issue can occur because when you start the program using BPServer.exe, it is starting as the user that is currently logged onto the server, and not as the system account. However, the Access Control List (ACL) has been set to the SYSTEM account.
To solve the issue
Start the Blue Prism Server as a service and not through BPServer.exe.
16-11-20 06:58 AM
18-11-20 04:06 PM
18-11-20 04:14 PM
Hi Hossein,
Thanks for the reply! We start Blue Prism server from a .bat file which starts two services. E.g.
sc start "Blue Prism Server:Default"
sc start "Blue Prism Server:RPA_UAT" "RPA-UAT"
Kind regards,
Gyula
19-04-22 01:31 PM
16-12-22 02:54 AM
28-01-24 11:26 AM
Your message indicates a detailed and technical approach to ensuring a secure connection, specifically with WCF Transport encryption. The mention of associating certificate thumbprint in the resource PC startup script demonstrates a careful consideration of security measures. Additionally, addressing the importance of having consistent cipher suites in TLS 1.2 registry settings, especially when using a Layer 4 load balancer, highlights a comprehensive approach to securing end-to-end connections. This level of attention to encryption and load balancing practices is commendable for maintaining a robust and secure system.Fm Whatsapp Apk