AppDynamics for Databases
2.9.x Documentation
On this page:
When monitoring CPU information on a Windows based machine with AppDynamics for Databases, either the OS collector part of the database collector, or the Server collector, Windows Management Instrumentation (WMI) is used to remotely gather the metrics. WMI is often frustrating to troubleshoot. This article explains some potential problems and pitfalls.
WMI makes use of RPC. RPC listens on a well-known port (135) but then allocates a dynamic port for subsequent communication. Therefore, you need to configure your firewall to allow 135 (always) and follow the dynamic RPC ports. It can be done - you do not need to restrict the port range, and there are several articles already on the internet that explain this, just ask Google!
To delegate permissions for WMI Control, run wmimgmt.msc. If you don't have a shortcut to the program, then simple click the Start Menu, and then search for the executable.
Now step through the following instructions to confirm you will have the correct permissions:
If you miss any one of the three then you end up with one of:
Error=800706BA The RPC server is unavailable. SWbemLocator
or
Error=80070005 Access is denied. SWbemLocator
You can also setup extra security in the WIndows Distributed Component Object Model (DCOM) to prevent unauthorized users from accessing WMI remotely. The following prevents users other than those configured as follows from remotely accessing the WMI. You can configure the named user account under which you would like to run AppDynamics for Databases as follows: