aLTeReGo ✭✭✭✭✭

It's not always the size of the database but the number of transactions being handled. I would suggest looking at the database server and ensuring your aren't queuing I/O On the DB server, open PerfMon.exe and monitor "Current Disk Queue Length". Zero is the best this value can be. This number being as high as 20 for any…

Appears to work for me using SAM 6.6.1. Ensure there are no unexpected carriage returns when pasting the certificate into the text field.

Running the script through the Agent should in effect be no different than running that same script manually on the same machine, provided you set the execution mode to 'Local Host' and forced impersonation by enabling 'Run the script under specified account'.

I've dug deep and haven't been able to turn up any conclusive answers for you. I did manage to find one other case similar to yours that was traced back to an issue with Lotus Notes/Domino. There is also a KB article for the Report Scheduler that denotes a potential issue defining the user account the report scheduler is…

Have you tried using something like WMI Explorer to troubleshoot the query outside of SAM? It may be the syntax of the query or what is being queried is not available for some reason. I would suggest starting with "Select * From MSBTS_SendPort"

Are there multiple SQL Instances running on this server? Also, what does Task Manager report for memory (Memory - Working Set). A screenshot of all memory usage related to this process would be helpful.

This information is indeed collected by AppInsight for Exchange for each mailbox database.

Simply select 'Component' from the drop-down list of what you want to report on. It's not AppInsight specific. You can then specify the component name in the alert definition if so desired. It should auto-complete so you know you're on the right track.

If you're willing, post your ticket number(s) here and I'll ask support to look into it.

Presumably you should be fine now. If this occurs again in the future, or you'd like to determine the root case of why this issue occurred in the first place, I recommend opening a case with support so they can rummage though your diagnostic logs in search of that answer.

So what you are saying is that I should make a copy of the original template and then MultiEdit the instance name. That would be reasonably efficient, but I have to wonder if there isn't a cleaner way to do this in the future. Following this method, I'll end up with 150 templates. From a display standpoint, it'd be a lot…

hcy01uk‌, it's difficult to say for certain without additional information. The problem is likely permissions related, but without diagnostics it's difficult to say for certain. I would recommend opening a case with support so we can assist you with determining the cause. mike s‌, the problem you are experiencing with the…

Correct. You will lose historical volume usage and interface utilization information. CPU, Memory, availability, and response time information will however be retained.

If you run the Scalability Engines Installer or the Offline HotFix installer on your polling engine and there's nothing to install, then the hotfix is already applied.

The hotfix bundle only contains hotfixes. You will need to download the latest full offline installer to upgrade to the latest GA releases. In the screenshot you posted above, it appears you're still running on the first Release Candidate.

mxr662 wrote: Are we at HF 1 or HF3. Installer says 1 and web console says 3 How do you get to HF3 with the online installer? Our db is not ready for NTA upgrade yet. The right side of that screenshot that's off the screen should be asking you a question regarding your MSSQL database. Something like 'click to confirm'.…

Do you have an open support case for this issue? If so, can you post your case number here so I can look into it?

This thread is rather old and discusses many of the features included in APM 4.2. Server & Application Monitor (SAM) 5.0 has since been released. SAM is the direct replacement/upgrade to APM. We renamed APM to SAM to more accurately reflect the new features and functionality of the product in the 5.0 release. As Dan stated…

The chart is in seconds. There are 1000 milliseconds in a second, so .05 should be 50 milliseconds. Someone check my math on that one please.

We've done some preliminary tests in the lab. On average, each monitored SQL instance consumed 261MB of storage space in the Orion database with 90 days of historical data was collected. Network traffic for a monitored SQL Instance running on an SNMP managed node averaged approximately 11kbps. Actual millage may vary as…

I'm not able to reproduce. It may be that you're choosing a similar but different field from the ones I've selected though. I would suggest sticking to the "Nodes" and "Node Current Statistics" categories. I have a feeling you might be selecting items from the "Asset Inventory" category that applies only to servers and not…

I'm trying to reproduce this issue myself internally. In the meantime I've logged this under FB321097. If you wouldn't mind, please open a case with support so we can look through your diagnostics as we attempt to reproduce this in our lab environment.

You are executing this in a PowerShell window. You need to execute this at the command prompt. To get to a command prompt click "Start -> Run" then type "cmd" and click "ok". Open a Command Prompt window

once you get the kinks worked out you should post this to the Thwack Content Exchange. I'm sure this would be very useful for other customers as well. Thanks for sharing!

SAM does support monitoring of IBM's pSeries servers for things like CPU, Memory, Volumes, etc. through SNMP. IBM's Director Agent for the pSeries does not provide hardware health information, so that information is not available. SAM does however provide full support for IBM's xSeries servers, including full Hardware…

Yes, that is correct.

Hmm.. The only thing I can think of offhand is that maybe there is an orphaned job stuck in the collector/Job Engine v2 database. I recommend following the steps outlined in the KB article below to clear out this temporary database. Post back and let us know if this does or does not resolve the issue. * SolarWinds…

Ok, that's what I thought. Unfortunately there's no simple streamlined process for monitoring Mount Points with SAM. Because the instance name is likely unique for each instance there's no simpler way to monitor these metrics than the way you're currently using.

So monitoring of services works for some, but not all nodes. Are you able to manage one of these problematic nodes in Orion via WMI instead of SNMP? One thing I would suggest trying is to run WMIExplorer from the Orion server and rung the following query against this remote host using the same credentials that are assigned…

Here's another Screenshot using Process Explorer.