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.
      

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

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

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: "The object exporter specified was not found."