Blue Prism 5.0登录异常及SQL Server Error26连接故障求助

Hey Harsha, sorry to hear you're hitting this roadblock so early with Blue Prism—let's work through this step by step, since the root issue is the SQL Server connection failure that's causing Blue Prism's login fields to gray out.

First, let's fix the SQL Server connection error you're seeing in SSMS, because once that's resolved, Blue Prism should start working again. Here's what to check:

1. Make sure your SQL Server instance is running #

• Press Win + R, type services.msc and hit Enter to open the Services console.
• Look for a service named SQL Server (INSTANCE_NAME)—if you used the default setup, this will be SQL Server (MSSQLSERVER). If it's a named instance, it'll have your custom instance name instead.
• If the status isn't "Running", right-click it, select Start, and set the startup type to Automatic so it doesn't stop after a reboot.

2. Verify your SQL Server instance name and network settings #

• Open SQL Server Configuration Manager (find it in the Microsoft SQL Server folder in your Start Menu under "Configuration Tools").
• Expand SQL Server Network Configuration, then click on Protocols for [YOUR_INSTANCE_NAME].
• Ensure TCP/IP is enabled (right-click it and select Enable if it's not).
• Double-click TCP/IP, go to the IP Addresses tab, scroll to the bottom, and note the TCP Port (default is 1433 for default instances; named instances might use a dynamic port).
• When connecting in SSMS, use the correct instance format:
  • Default instance: localhost or your machine's IP address
  • Named instance: localhost\YOUR_INSTANCE_NAME or [YOUR_IP]\YOUR_INSTANCE_NAME
  • If using a dynamic port: [YOUR_IP],[PORT_NUMBER] (e.g., 127.0.0.1,1433)

3. Check remote connection settings (even for local connections) #

• Once you can connect to SQL Server via SSMS (after fixing the above steps), right-click your server in SSMS and select Properties.
• Go to the Connections tab and check the box for Allow remote connections to this server.
• In SQL Server Configuration Manager, under SQL Server Network Configuration, ensure the remote connection settings are set to allow both TCP/IP and Named Pipes.

4. Rule out firewall interference #

• Open Windows Defender Firewall > Advanced Settings.
• Create a new inbound rule to allow traffic on the SQL Server port (default 1433) or allow the SQL Server executable (usually located at C:\Program Files\Microsoft SQL Server\MSSQLXX.MSSQLSERVER\MSSQL\Binn\sqlservr.exe—replace XX with your SQL Server version).
• As a quick test, you can temporarily disable the firewall and try connecting in SSMS. If it works, the firewall was blocking the connection, so make sure your new rule is correctly configured.

5. Fix Blue Prism's database connection string #

Once SSMS connects successfully, update Blue Prism's configuration to match the working connection:

• If you can open Blue Prism's System Manager, go to System > Database Connections and verify the connection string matches the one you used in SSMS.
• If you can't open System Manager, navigate to your Blue Prism installation folder (default is C:\Program Files\Blue Prism Limited\Blue Prism Automate) and open BluePrism.Server.exe.config in a text editor.
• Look for the <connectionStrings> section and ensure the Data Source value matches your working SQL Server instance. For example:

  <add name="BluePrism" connectionString="Data Source=localhost\MSSQLSERVER;Initial Catalog=Default Connection;Integrated Security=True;" />
  

• If you're using SQL authentication instead of Windows auth, the string will look like this:

  <add name="BluePrism" connectionString="Data Source=localhost\MSSQLSERVER;Initial Catalog=Default Connection;User ID=your_sql_username;Password=your_sql_password;" />
  

After making these changes, restart the Blue Prism service and client, then try logging in again. The username/password fields should no longer be grayed out if the database connection is working.

内容的提问来源于stack exchange，提问作者KHV