IIS Server monitor - Issues encountered while adding an IIS server monitor

IIS Server monitor - Issues encountered while adding an IIS server monitor

Unable to add an IIS server monitor

Prerequisites: Make sure you have performed all the prerequisites for the IIS server monitor.

Follow the steps mentioned below to add an IIS server monitor:
  1. IIS Server URL accessibility:
    1. Check whether the IIS Server URL is accessible from the Applications Manager server.
    2. For IIS Server URL-related error messages, refer here.
  2. Proxy configuration: (if required)
    1. If your environment requires the use of a proxy server to access IIS Server URL ( http(s)://[Host/IP]:[PORT] ), then configure the same in Applications Manager. To know how to configure proxy in Applications Manager, click here. For IIS Server URL-related error messages, refer here.
    2. If proxy is configured in Applications Manager and if you want to bypass the IIS Server host/IP from routing through the proxy then add the host/IP under the "Do not use proxy for addresses beginning with" column in the same 'Configure Proxy' page in Admin tab > "Connectivity" under " Product Settings " and click "Proxy Server".
  3. IIS Server credential: (WMI credential)
    1. For Applications Manager versions till 15110, we use the respective server (Windows) monitor credential to fetch data from the remote server. So adding the Server monitor is mandatory to fetch IIS Website and Application Pool statistics.
    2. From v15120 of Applications Manager onwards, we check the WMI credential during monitor addition as we started collecting the server credential as input parameters in IIS Server monitor itself, removing the server monitor dependency. 
      Note: WMI credential is mandatory only to monitor Website & Application Pools statistics.
    3. If unable to add the IIS Server monitor by providing WMI credential, follow the steps below:

      1. Open command prompt in administrator mode in Applications Manager-installed machine.

      2. Navigate to  <Applications Manager Home>\working\conf\application\scripts  directory.

      3. Execute the below command by replacing  hostname,  username, and  password  with that of the reported IIS server:

        cscript wmiget.vbs  hostname username password "Select * from Win32_PerfRawData_PerfOS_Processor where Name='_Total'"
      4. Check the output of the above command. If script output returns expected data but still unable to add monitor, try adding the monitor again with "print-all-logs" enabled.

Reach out to our support team with the add monitor page screenshot to  appmanager-support@manageengine.com  along with the latest  Support Information File (SIF)  from Applications Manager with print all logs [ Admin > Logging > choose 'Print all logs' ] enabled for analysis.


Error: "Authentication failed. Kindly verify the IIS Server URL response header as the 'Response Header Check' is failed."

Check whether IIS Server URL's response header contains the keyword 'IIS', if not, then disable the 'Response Header Check' option while adding a new monitor to bypass IIS Server URL response header check, as we look for the 'IIS' keyword in the response header.

Error: "Authentication failed. Kindly verify the host and port details provided."

Check the hostname and port details in the Edit monitor page ( Go to IIS monitor page > click 'Monitor Actions' > 'Edit Monitor' ) and update the respective values and poll the monitor. 

Error: "Authentication failed. Kindly verify the username and password provided for the Host."

Check the username and password details in the Edit monitor page ( Go to IIS monitor page >  click 'Monitor Actions' > 'Edit Monitor' ) and please update the respective values and poll the monitor and check once.

Error: "Error while discovering the IIS service with error code {0}. Kindly check whether IIS Service is running or not."

For IIS Server URL-related error messages, refer here.

Error: "Data Collection failed. Unable to fetch Websites and Application Pools statistics as no data returned for basic WMI query."

  1. Refer to section C (IIS Server credential) in the above steps to add IIS Server monitor and try connecting to the IIS server from the Applications Manager server. Execute a basic WMI query to verify whether the given WMI credential is able to fetch data from the remote server.
  2. If the issue persists in remote script execution, use the WBEMTEST tool (Microsoft tool to check WMI data) and check whether the same basic WMI query returns data. To know more about WBEMTEST, click here.
  3. If the issue persists in WBEMTEST when remoting from Applications Manager to IIS Server, try once directly in the local server (IIS server) itself and check if the data is available or not.

Error: "Could not connect to the System. The System may be down or RPC Server is not available."

Follow the steps mentioned in any of the required links mentioned below to resolve the issue:
If any proxy configured, double-check whether the URL is accessible from the system where Applications Manager is installed.

Error: "The object exporter specified was not found."

To access WMI utility to a NATed machine, add the server's name and ip address to the host file and then connect using the host name. Microsoft reference link: Link

For example if the remote server is named serv1 and has a public ip address of 192.27.111.111 then you need to add the following to your local hosts file located at C:\WINDOWS\system32\drivers\etc
192.27.111.111     233-Serv2

Then when you go to connect simply use the remote computer name such as:
\\serv1\root\cimv2

This should allow you to connect to a remote server using DCOM even if it is behind NAT, as long as the DCOM 135 port on the remote server public IP is accessible and forwarded to the private IP address.

On adding IIS monitor you would specify serv1 as the server name and login using serv1\username.

                    New to ADSelfService Plus?

                      • Related Articles

                      • IIS Server monitor - Troubleshooting steps

                        Unable to add IIS Server monitor Follow the below given below to add an IIS server monitor in Applications Manager: First, check whether all the prerequisites are done. Check the IIS Server URL is accessible from Applications Manager server. If your ...
                      • Issues in creating server monitor

                        Please do test credentials before adding a particular monitor. Troubleshooting the SSH Configuration :  I cannot add remote server monitor using SSH password authentication Please follow our suggestions below, 1) When adding that server monitor, ...
                      • IIS Server monitor - Troubleshooting 'No data available' error for IIS Websites and Application Pools statistics

                        Error: "No data available for IIS Website statistics." User must have the permission to execute WMI queries on 'root\CIMV2 ' namespace of the IIS Server. Steps to check the IIS Websites using AppManager script "wmiget.vbs" to execute the WMI query in ...
                      • Troubleshooting URL Monitor

                        Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...
                      • REST API Monitor - FAQS

                        1. What should I do when Basic Authentication fails in REST API monitor? Verify if the credentials provided in the Applications Manager are correct. Try if sending username and password in Authorization request header works Get an BASE-64 encoded ...