Applications Systems
403 Forbidden error on AppInsight for IIS components
Problem - When monitoring AppInsight for IIS, the following error is received under the "Site Details" components labeled HTTP Bindings Monitor, and HTTPS Bindings monitor: "Access denied, authorization failed. The remote server returned an error: (403) Forbidden." The "Configure Server" button completes without error. The test connection completes fine as well.
First published date
Last published date
Overview
Problem - When monitoring AppInsight for IIS, the following error is received under the "Site Details" components labeled HTTP Bindings Monitor, and HTTPS Bindings monitor:
The "Configure Server" button completes without error. The test connection completes fine as well.
Product section
Cause
-
This can be due to improper permissions to the IIS website being monitored
-
This can also happen where there isn't a Web Service hosted on the other end such as AppInsight for Exchange or WSUS. You will get the same HTTP Code when attempting to browse to it from a Web Browser
Resolution
Resolution 1
- Right click on the Website Folder in question on the target machine (Default to C:\inetpub\).
- Click "Properties".
- Navigate to the "Security" tab.
- Click "Edit" to change permissions.
- Click the "Add" button, add the "IIS_IUSRS", and click OK.
- Ensure that this IIS_IUSRS has been granted the following:
- Read & Execute
- List Folder Contents
- Read
Note: If you receive a HTTP 403 when browsing from an Internet Browser then the issue lies on the Website side. It may be that it doesn't actually host a Website but is hosting some service instead.
Resolution 2
If the above resolution doesn't work you may also try to change the URL to a valid one.
1. From the Site Details view of the website that returns a 403 response when monitoring the root click "Edit Thresholds"
2. From there expand the HTTP or HTTPS Bindings Monitor (Site Name), click "Override Instance" for the URL setting and edit the URL parameter with a URL that works for that site.