Quantcast
Channel: THWACK: All Content - Server & Application Monitor
Viewing all articles
Browse latest Browse all 12281

AppInsight for SQL credentials

$
0
0

Hello Everyone!

 

I'm starting this thread because most of my SQL database servers, which are added into NPM & SAM won't accept their credentials. Here's the situation explained:

 

After adding the "AppInsight for SQL" monitor to my SQL database servers, the servers and SQL instances are visibile on the Orion interface tab "Application". But all of them have a grey LED. This is obviously because i need to provide the credentials so that Orion can monitor the SQL instance correctly.

 

When providing the "SQL database instance login-allowed" credentials, the credential test "Fails". No matter what credentials I use. The credentials i've tried have domain admin rights, SQL sysadmin rights and I even tried with dba owners. None of  them work.

 

The funny thing is. I've also got a SQL server which DOES accept it's credentials. and all of the above SQL credentials i've tested with work correctly. So i've tried to see what the difference is between the servers who do and don't accept the SQL credentials. But I could'nt find any logical explanation.

 

However I am interested in the log file, but I don't know which and where i can't find it.

 

For the record: Both working and not working server have the same: SQL -> Security -> Logins -> accounts and rights.

 

Some info on the tested servers:

 

Correctly working server:

Win server 2008 R2 Enterprise SP1

 

MS SQL Server 2008 R2

MS SQL Server Management Studio 10.50.1600.1

(SQL) Operating System 6.1.7601

 

Not working server:

Win Server 2008 R2 Enterprise SP1

 

MS SQL Server 2008 R2

MS SQL Server Management studio 10.50.4000.0

(SQL) Operation System 6.1.7601

 

I really don't know what could cause this problem. So if anyone could help me out here?

 

 

 

 



Viewing all articles
Browse latest Browse all 12281

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>