Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Network Performance Monitor (NPM) > 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 back up of SWNetPerfMon.db located in 
  2. C:\Program Files (x86)\SolarWinds\Orion\SWNetPerfMon.DB, in case you need to roll back later.
  3. Edit the SWNetPerfMon.db using notepad or any text editor, to have Max Pool Size = 1000..You need to  add the following line before 'Persist Security Info=': Max Pool Size = 1000;
    Note: You only need to edit the top 3 strings, as the product has archived the connection strings not used in the file.
  4. Save the file and exit.
  5. Restart the Orion Services using the Orion Service Manager.
Last modified