We recently setup the AppInsight for SQL and everything seems to be working except for one thing. By default there is a table called All Databases and it shows the status and size of each database on that server. The list of databases are click-able and I would think when clicked it would take you to historical stats or something, but when we click on any databases on any of the monitored servers it gives an error page saying "Unexpected Website Error Object reference not set to an instance of an object." Are we not supposed to be able to click the database objects or is there something wrong with our SolarWinds?
Top Replies
-
You are correct that clicking on a database should take you to the Database Details view. What you're seeing is a very rare bug that is fixed in SAM 6.2.1, which is due out shortly and tracked internally… -
In the end, the SolarWinds engineers could not resolve the issue and came to the conclusion that it was a Microsoft/SQL Server issue. It took longer than I cared for, but I created backups of every database… -
SQL Server Analysis Services? AppInsight for SQL only monitors the database engine, not SSAS or SSRS for that matter.
-
You are correct that clicking on a database should take you to the Database Details view. What you're seeing is a very rare bug that is fixed in SAM 6.2.1, which is due out shortly and tracked internally under SAM-477. In the meantime you can fix the problem on your own by going to [Settings -> Manage Views] and delete the "SQL Database" view. There may be another one named "SQL Database (1)" also. Delete that one as well. Now go back to AppInsight for SQL and click on a database. You should no longer receive and error when attempting to access the Database details page.
-
-
-
-
-
-
-
-
aLTeReGo, I installed the SAM 6.2.1 upgraded, rebooted both servers late Friday evening and checked everything this morning.
I read a thread posted by dabs (Appinsight for SQL), and read the mentioned Microsoft article. Thinking I might have an issue with the counters, I performed the following.
However, when I opened a fresh browser and clicked on the MSSQLSERVER Application Monitor on either of my database servers, this is what I'm getting:
I saved the error report and tried looking through it but can't make heads or tails because I'm not sure what to look for. I'm going to submit a ticket but in case there is someone who has solved this or is familiar with the error logs, I've attached the generated error log.
-