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

NPM 12.5 issues on Windows 2019 and SQL 2017

We have recently done an upgrade from 2008 systems to 2016 then to 2019 and SQL 2017. We seem to be running into a lot of connectivity issues to the SQL DB from the application. The one major thing we keep seeing is that the management system can't connect to the DB. However, from the management system, we can connect just fine with the UDL and same username and password.

Has anyone else had any issue with the new version working on Windows 2019 and SQL 2017?

Find more posts tagged with

Accepted answers

All comments

mwb

I have not - I'm running SQL 2017 in two instances and while my main Orion nodes are still on Server 2016, I have more than a dozen APEs on Server 2019.

I have had issues with the current version reporting into SQL in a timely fashion over slower connections, acknowledged by Support, but I believe that is independent of the SQL or OS version. You could call it a connectivity issue, but I'm looking at it as a software bug.

Does the data end up in the DB eventually?

justin.alcorta

Thanks for the response. The issue is that the application doesn't make that connection. It was working for about 4 hours and data was being written and the web console was able to present it, but then the services start stopping and starting and then the software stops connecting. However, the udl file test connects just fine. For a couple of days if we just reboot the portal everything starts working but now that stopped working. We are starting over on the portal system but just wondering if anyone else had an issue.

justin.alcorta

We have had a case open and multiple engineers and it turns out that there is a bug. We aren't sure what the bug is but SolarWinds is reaching out the the developement team.

designerfx

Let me tag the new NPM PM to see if he can make any comment to head this one off. jason.carrier do you know of justin.alcorta's ticket and/or can you confirm if this is an internally tracked bug?

justin.alcorta

I am sorry let me clarify something. It is with NAM 12.5.

aLTeReGo

Without logs and a better understanding of your envionment, it's difficult to say for certain. it could be something as silly as a concurrent connection limit define on the account used by Orion to connect to SQL. The problem could also be more complex, such as a port exhaustion issue. My first recommendation would be to disabled Named Pipes on the SQL server and ensure you're using the IP address of the SQL server in the database section of the Configuration Wizard. Next, monitor the latency of SQL server itself from Orion.

justin.alcorta

Yeah, we have sent a ton of logs. We have disabled, enabled name pipes, we did this in a greenfield environment with only polling 4 nodes. Connections are at 60 or 1000 and the latency is at 4ms at peak. We looked at port exhaustion and that is when he considered it a bug. I threw this question out here before getting more help and having the issue escalated up the chain. Apparently, there are more cases like this and are being looked at by the developers.

justin.alcorta

Our issue numbers are: 00365213 and 00358341

aLTeReGo

Thanks justin.alcorta. We're looking into it now.

justin.alcorta

If anyone is at SolarWinds management or engineering could please take a look at what is going on with this case to help our tech support engineer that would be very appreciative. We have an issue open since May and still nowhere. We can't even get the system to register our licenses.

Thank you.

aLTeReGo

Your case has just been transferred to one of our best Applications Engineers.

mistik84

what is the result of this issue?

dpad

Up! We're also planning on migrating to Windows 2019 and SQL Server 2017.

justin.alcorta

We are still working through it but everything is looking better. We have run into some gotchas. I will update what we did or had to do when we get stable.

mistik84

So far done migrate to 2019 and sql 2017. Workig fine. Just i just know that rabbitmq now using chiper.

pratikmehta003

We also have a new customer coming up with these config... will keep an eye on this thread..

justin.alcorta

Yes we had multiple issues but the one that solved a majority of the issues was making sure the ciphers are set correctly. IISCrypto is the tool we used.