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
Store

SW Crashing every 2 hours

On saturday we upgraded our Primary, 2x additional pollers and Web Front End to NPM 12.0. Along with updating SAM, NTA, NCM UDT and VNQM.

Our instance was rock solid stable on ver 11.5.3

Now it's crashing every 2 hours. Every time it says "unexpected SQL error" A Network related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL server is configured to allow remote connections. (Provider: Named Pipes Provider. error:40 - Could not open a connection to SQL Server).

The workaround we have for now is the stop and restart the services in Orion Services Manager which then seems to "fix" things for a while.

Also we've noticed events recently. Don't know if its related or not but it very well could be:

"Plugin "VNQM Business Layer failed to start on (servername) Please restart the module Engine service on (servername)

This appears more or less every 1:30 to 2 hours.

Find more posts tagged with

Accepted answers

All comments

orioncrack

Similar issue?

DB connectivity error

theonitan

I had the same darn thing happen to me. It took me 10 days to finally figure out was wrong with the help of Dan from SolarWinds.

Problem

I received an error stating that there was a problem on my network or I didn't have the latest and greatest tool update.

Root Cause

Network connections that were connected to the SolarWinds server during the time of upgrade were not disconnected. This lead to a CLOSE_WAIT issue that kept creating new sessions that ultimately caused port exhaustion.

Fix-Action

Step 1. Applied all HotFixes for NPM 12.0 and NCM 7.5.

Step 2. In command prompt window, type in netstat | more. Identify the CLOSE_WAIT Workstations, disable/re-enable the NIC, and rebooted them.

Step 3. Reset IIS. iisreset. iisreset /stop>iisreset /start

TIME_OUT Issue

Resolved with the Hotfix

CLOSE_WAIT Issue

Resolved by manually rebooting the workstations that were causing CLOSE_WAIT

theonitan

So if you have a CLOSE_WAIT problem, you need to reboot the computers that are stuck in CLOSE_WAIT.

If you have a TIME_WAIT problem, you need to apply the hotfix.

You would think that an IISRESET was resolve the problem, but it seems like the remote computers like to keep an old open connection. I hope this helps, because I was on the verge of rebuilding SolarWinds NPM 12.0.

orioncrack

We upgraded and are still having these problems. Any update @solomon78?

This issue kills SAM for us.

solomon78

So since yesterday our's has been stable. The SW guy enabled TLS 1.2 on our main poller via a registry entry and I deleted alot of AGENTS that simply didn't want to connect. I think that more than anything else caused port exhaustion which required a services stop\start every few hours.

Also on FRIDAY night we upgraded .net Framework on our SQL box to enable TLS 1.2 encryption. So one or a combination of all 3 those things seems to have stabilised our environment for the time being. There was a notification "bell" icon on the top right hand corner of the web Portal which gave me a warning about Agents not communicating but i disregarded that and I shouldve paid closer attention to that.