HTTP Error 403.2 - Forbidden

You have attempted to view a resource that does not have Read access.

Most likely causes:

  • The Rights and Permissions setting for the requested resource does not allow Read access.
  • The default document specified for the Web site does not exist. For example, you specified Default.htm but this file does not exist.
  • Directory browsing is not enabled.
  • The configuration/system.webServer/handlers@accessPolicy attribute does not have "Read" configured for the requested resource at the server, site, application, or page level.

Things you can try:

  • Enable Read access for the requested resource.
    1. Open IIS Manager and navigate to the level you want to manage.
    2. On the Features page, double-click the Handler Mappings feature.
    3. On the Handler Mappings page, in the Actions pane, click Edit Handler Permissions.
    4. In the Edit Handler Mappings dialog box, select Read to enable handlers that require read access.
  • Verify the default document does exist and matches what is specified in the Web site properties.
  • Verify that directory browsing is enabled. Directory browsing needs to be enabled if you want a Web site to show a directory listing (all files in the folder you are accessing).
  • Verify the configuration/system.webServer/handlers/accessPolicy setting at the server, site, application and page level. If this setting is specified, make sure "Read" is listed as one of the flags.
  • Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

Detailed Error Information:

Module   IIS Web Core
Notification   MapRequestHandler
Handler   StaticFile
Error Code   0x80070005
Requested URL
Physical Path   \\boswinfs04\home\users\web\b2886\ywh.ewgrovecom\_private\othclas\obit_mem\loveeula.htm
Logon Method   Anonymous
Logon User   Anonymous

More Information:

This problem occurs when the access permission for the requested resource does not have Read access enabled. Change this setting at the server, site, application, or file level. To resolve this problem, verify the Read access permissions setting at each of these levels, and set the appropriate access permissions at the desired level.

View more information »

Microsoft Knowledge Base Articles:

  • 247677
  • 838790