cancel
Showing results for 
Search instead for 
Did you mean: 

Blue Prism 7.3.1 Upgrade – Login Latency & Timeout Issues

vinothinfosys
Level 3

We are upgrading Blue Prism from version 7.0.1 to 7.3.1 in a parallel setup with SQL Server. The application server, Interactive Client (IC), and runtime resources are hosted on new VMs with Active Directory (AD) configuration. However, we are facing the following issues:

1. Application Server

  • Logging into Blue Prism (using SQL Windows authentication) takes almost 3 minutes.
  • I created an additional connection using the "Blue Prism Server Connection" mode within the application server and observed the same delay.
  • I suspect this is due to SQL connection latency, but I'm unsure whether the root cause is database-related or network-related.

2. Interactive Client & Runtime Resources

  • Successfully established a connection between the Interactive Client/Runtime Resource and the application server, and the connection is validated.

  • However, when attempting to log in using Active Directory, the request times out with the following error:

  • vinothinfosys_0-1740628559165.png
  •  

    Error Message:
    "Login failed. The request channel timed out while waiting for a reply after 00:00:00. Increase the timeout value passed to the call to Request or increase the Send Timeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout."

Looking for suggestions like to start debugging and resolve the latency issue.

2 REPLIES 2

Hi - There is a KB article with the error you are describing:

https://support.blueprism.com/en/support/solutions/articles/7000079032-bpe-error-the-request-channel-timed-out-while-waiting-for-a-reply-after-00-00-00-during-login

 

Brigiana Kopec Senior Product Support Engineer (Bilingual) – Americas

vinothinfosys
Level 3

Fix for this issue

1.Change the "Default Encryption Scheme" to "Database and give the same key used in Key Store in  BPServer Config.

2.Change Active Directory Domain under Single SIgn on to Manual instead of Auto and update respective info.

This fixed my issue.