Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Unable to open new database connection

Unable to open new database connection


The traps are not visible in Trap viewer. The following message is received:


Service was unable to open new database connection when requested.

Exception Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Connection string - Data\MSSQL2012;Initial Catalog=SolarNPM;User ID=sql_solarnpm;Password=*******;Connect Timeout=20;Load Balance Timeout=120;Application Name="Solarwinds Trap Receiver Service";Workstation ID=SJC4SOLAR02



NPM V11 through version 11.5.2


Database connections have run out of pooled connections. Theoretical maximum is 100 connections per process (default Connection Pool limit). 


SolarWinds recommends to increase the connection pool size on the Main Poller as this hosts Traps\Syslogs and Alerts Services.
This could also be applied on Additional Pollers or any additional Web Server, if needed.


  1. Create a backup of SWNetPerfMon.db, in case you need to roll it back later. The default location is:
    C:\Program Files (x86)\SolarWinds\Orion\SWNetPerfMon.DB
  2. Edit the SWNetPerfMon.db file using Notepad or any text editor. Include the following line:
    Max Pool Size = 1000;
    Add the Max Pool Size entry before th
    e Persist Security Info entry.
    Note: You only need to edit the top 3 strings, as the product has archived the connection strings not used in the file.
  3. Save the file and exit.
  4. Restart the Orion Services using the Orion Service Manager.
Last modified