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

AppInsight for SQL not working on WMI node?

I have a WMI node that I setup in Orion with SQL Server running on it; however, it's not showing the AppInsight for SQL as an option under the List Resource section. When I try to force assign AppIngight for SQL in SAM it gives me a timeout when trying to authenticate. The logs on my server indicate that Orion is telling the system that it's using a Direct SQL login but sending Windows Mixed Mode credentials which will never work.

Anybody have any thoughts on this?

Find more posts tagged with

Accepted answers

All comments

byrona

This is the 2nd time recently I have had issues with AppInsight for SQL, did something change with how this works in a recent update? This should be very easy, it's a WMI node yet Orion isn't discovering AppInsight for SQL on the node and when I try to force it on to the node it also fails. Below is a screenshot of the errors I am seeing from SQL on the issue:

SQL Authentication Errors 2.png

Clearly isn't trying to use the wrong account type but I don't have an option to change this.

nglynn

I've seen those log entries even on nodes that I add that DO work properly initially. Not sure I would focus on that yet. Is SQL listening on the default ports and on a network that your Orion can communicate with over those ports? I've also seen where moving the node to another polling engine and back and then re-running List Resources have fixed similar issues.

~Nick

byrona

In this specific case it's a failover cluster and the Node I am trying to add this to is the VIP which I have created a node for in Orion. I have confirmed that it's listening on all ports. Data-collections on the node itself are working perfectly so I know it's not an issue with WMI. I have confirmed that UAC is off as I have had problems with that in the past. The account I am using has Domain Admin rights and in SQL it's set as a SysAdmin. I did try an alternate method of creating the account as per the SolarWinds documentation located HERE but that didn't change anything. I have setup this exact thing before and never run into these types of issues; however, I thought you used to be able to specify the login method to use (Windows Authentication vs SQL Server Authentication) when setting this up but it appears that is only possible once it's assigned but it won't let me assign it because of the login failures.

byrona

What would be really helpful is understanding how Orion determines if AppInsight is applicable or not in the List Resources section because it isn't showing it as an available resource to monitor which I have never had a problem with in the past.

aLTeReGo

byrona, WMI is not used as the polling method for AppInsight for SQL. It's used only as one of the discovery/detection methods for determining that MSSQL is installed and is a supported version. All data is collected by AppInsight for SQL is done directly using the SQL protocol itself. I would recommend launching SQL Studio on the Orion server and attempt to connect to that SQL server using the same IP address and credentials as provided to AppInsight for SQL.

csasser

Our AppInsight for 2 of 3 SQL Servers connects very intermittently. It can be up for hours, then down for days, then back up. All of this without changing any thing on the servers. This is what I know:

The two SQL servers that it fails on our PRODUCTION servers. SolarWinds still monitors the other components (Window's Scheduled Tasks), but not SQL server.
- Because the account can connect to SQL server itself, it does monitor the databases, etc., but not the SQL services.
The box that it has consistent connection to is our fail over DB server.
Our error message is: Server unavailable using WMI. Unable to connect to "10.1.4.9" for WMI access. Unable to connect to server "10.1.4.9" as user "xxxxxx\Solarwinds_Service".
The Solarwinds_Service account is the local Admin on all servers that SolarWinds interacts with.

The Error Log from the SW server states the following:

DCOM was unable to communicate with the computer 10.1.4.9 using any of the configured protocols; requested by PID 167c (C:\Program Files (x86)\Common Files\SolarWinds\JobEngine.v2\SWJobEngineWorker2x64.exe).

What I don't know is why it seems to lack a consistent connection. The AppInsights for our web servers work well without a problem.

Any and all suggestions are greatly appreciated.

aLTeReGo

Windows Scheduled Tasks does not use WMI. It uses RPC. This may explain why Windows Scheduled Task monitoring is working and AppInsight for SQL is not. AppInsight for SQL gathers roughly 90% of its information via SQL, and the other remaining 10% via WMI. It sounds like WMI is not working on that machine. You may want to look through the WMI troubleshooting doc to see if that helps you resolve the issue.

http://www.solarwinds.com/documentation/apm/docs/APMWMITroubleshooting.pdf

csasser

Thanks. I will take a look. It is bizarre how it goes up and down. I wonder if SQL is interfering with the WMI connection.