Network Management

SolarWinds Platform Web Console is inaccessible with Error 500 displayed after upgrading to 2026.1.1

This article describes a post-upgrade issue in SolarWinds Platform 2026.1.1 where the SolarWinds Platform Web Console becomes unstable and periodically returns “ERROR 500”, often requiring service restarts to recover.

First published date

4/23/2026 5:49 PM

Last published date

5/8/2026 6:14 PM

Overview

After upgrading to 2026.1.1, the web console may become unstable and crash with ERROR 500 every few minutes, requiring a restart of services to bring the console back online.

 

In Feature Service logs, you may see repeated errors when executing the gRPC method GetFeatures, followed by a SQL connectivity timeout during the pre-login handshake.


[.NET TP Worker] ERROR Grpc.AspNetCore.Server.ServerCallHandler - (null) Error when executing service method 'GetFeatures'.
System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=21025; handshake=0; 

Product section

Network Performance Monitor

Cause

After upgrading to SolarWinds Platform 2026.1.1, the Feature Service may attempt to initialize and call GetFeatures before SQL connectivity is stable/available, leading to a SQL connection timeout during the pre-login handshake.

Resolution

  1. Locate and open swnetperfmon.db for editing - this is by default found in C:\Program Files\SolarWinds\Orion
    Edit the timeout value in the first paragraph of the swnetperfmon.db file. The default is 20.

  2. Increase the timeout value
    Change the timeout value from the default 20 to 120.

  3. Save the file
    Save the changes in swnetperfmon.db.

  4. Restart SolarWinds services
    After saving the change, restart the services.