Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

After NPM 12.3 upgradation getting an error & How to fix this error permanently and what can be the reason behind it?

Hi All,

I am getting an error after "2018.2" NPM 12.3 upgradation. Database connectivity being the loss and getting below error. What can be the solution?

Service was unable to open new database connection when requested. SqlException: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.) Connection string - Data Source=xyz;Initial Catalog=SolarWindsOrion;Persist Security Info=False;User ID=xyz;Password=*******;Max Pool Size=1000;Connect Timeout=20;Load Balance Timeout=120;Packet Size=4096;Application Name=SolarWinds.ServiceHost.Process@Service-SolarWinds.Cortex.DataCollection;Workstation ID=abc

Orion Platform 2018.2 HF3, UDT 3.3.1, VNQM 4.5.0, SRM 6.6.0, WPM 2.2.2, DPAIM 11.1.0, NPM 12.3, VMAN 8.2.1 HF1, NetPath 1.1.3, CloudMonitoring 2.0.1, SAM 6.6.1, NTA 4.2.3

Find more posts tagged with

Accepted answers

All comments

vinay.by

I am suspecting the issue is due to number of hits to the DB, raise a case with SolarWinds and they would let you know where exactly do you have to change the default values (I can't remember where but one of the config files holds these default values in it -> Pool Size=1000;Connect Timeout=20;Load Balance Timeout=120, its not a recommended change, but they would collect the diag from you and suggest an optimal value for your environment, these changes are specific to your environment), that should solve your problem for sure.

I had a similar issue a couple of years ago and could fix the same by changing these values accordingly.

Hope it helps.

er.vansh17091

Hi Vinay,

Thank you ! do you have that case no?

Deltona

I would REALLY like to know what needs to be modified. It sounds like settings you would add in the SWNetPerfMon.DB file. Pool Size=1000 is already being used by er.vansh17091 as seen in his log. So maybe timeout and balance timeout should be added?

vinay.by

Hi @Deltona, I truly cant remember, I faced this issue in NPM 10x lot many years ago, but I am sure this is a known issue to SolarWinds support folks, I remember adding an additional parameter into SWNetPerfMon.DB (thanks for pointing that out) something that represents a timeout (not sure if that's wait timeout or some other param), shrinking the database might as well help in resolving this issue (but not 100% sure on that).

But I am sure i added an additional parameter and probably changed pool size value, combination of those parameter values fixed the issue in my environment. (SolarWinds as well mentioned its not recommended to change those values and was time being till we upgrade)

I did read another thread which contained a similar issue -> alterego mentioned it could be due to connection pooling

A connection was successfully established with the server, but then an error occurred during the pre-login handshake (SQ…

vinay.by

Hi er.vansh17091, I dont have the case number that i had raised - this happened long time back, rather I was asking you to raise a case with SolarWinds vendor, I am sure they know the fix for this as this is a known error. Strange thing is I couldn't find any reference to it on thwack

alankar.srivastava

I am facing the same issue in Orion 2020.2 . My SAM monitors automatically going to unknown state and showing not licensed after 20 min of orion service reboot. SAM license is ALX. Also logged case with solarwinds , but no luck so far . Did all service repair and license reactivation but not worked yet.

Any help