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:Solarwinds SAM Test Connection Failed

Hi All SAM Experts,

i am newbie to Solarwinds.I am currently configuring AppInsight for SQL for two of my DB Servers in cluster. Both the servers are monitored properly in Orion using WMI. As per the

documentation we did create a SQL Account with respective permissions. However, whenever i do a test connection..it says Test Failed. Does this SQL Account need to be mixed mode?

Am i missing any settings on SQL Server ? Where to check this logs on Solarwinds ?

Find more posts tagged with

Accepted answers

All comments

Petr.Vilem

One important thing about AppInsight for SQL and clusters: AppInsight for SQL application should be assigned to orion node created on virtual cluster IP - i.e. not directly to nodes representing individual cluster members. See online help for more info.

Mixed mode is not required - windows authentication should definitely work.

Can you verify that you are able to connect from SQL management studio (ideally from orion machine, logged in with same credentials that are used for monitoring)?

orwin

Hi Petr,

Thanks for your reply. i am using sql authentication for this one.So you mean ...the Cluster itself has to be managed from Solarwinds SAM ?

Petr.Vilem

Yes. It will most likely get name from currently active member machine but you can change it on the last step of add node wizard (to avoid confusion from having two nodes with the same name in orion).

orwin

Hi Petr,

Correct. thanks for your information.But curious if the SQL gets fail-over to another node , will the monitoring get affected ?

Also, we are using SQL 2014. & when i try to add it says Unable to connect to server "XXXXXXX" as user "XXXXXX" for SQL 2012 Analysis Services application monitor.

cdowning

I'm having the same problem as the original post... I'm trying to add AppInsight for SQL to several instances in a clustered environment, but the test connection continues to fail. The AD user was configured using the script found at SolarWinds Knowledge Base :: AppInsight for SQL Requirements and Permissions. And I can verify that the user can log into that instance via SQL Management Studio on the Orion application server. Any other ideas?

EDIT: Scratch that... I may have figured it out myself. When I was trying to add the AppInsight monitor, I would use the instance VIP, add the node as a WMI node, and the node would always show up as the server that the instance was currently on. I assumed that was normal and carried on, but the AppInsight monitor would never connect to the SQL instance. Now, I've removed AppInsight from all of the individual server nodes and created a new node using the "External Node" polling method. I was then able to add the AppInsight monitor that new node, and it was able to connect to SQL! It's still in the "initial polling" phase, but I'm hopeful!

EDIT 2: So, that ALMOST worked! I did have to go back and change the polling method to "Windows Servers: WMI and ICMP" to get the polling to work. After changing the polling method, I verified that the ONLY template applied to the node was AppInsight for SQL for that specific SQL instance. Now I'm seeing all of the details about that instance under that node.

Also, for the record, I went through this process on an instance I could play with, so I put the instance through a couple of failovers. It looks like Solarwinds had no trouble following the instance, no matter what cluster node it fell on.