PRB: Unable to Access Web Project - Access Forbidden Error (175800)


The information in this article applies to:

  • Microsoft Visual InterDev 1.0
  • Microsoft Visual InterDev 6.0
  • Microsoft Internet Information Server 3.0
This article was previously published under Q175800

SYMPTOMS

The following error occurs when you try to preview a Web site:
HTTP/1.0 403 Access Forbidden error.

CAUSE

This error is typically caused by either a misnamed document or permissions settings.

RESOLUTION

Misnamed Document

Make sure that the Default.htm or Default.asp file names are listed in the Default Document edit box that is located on the Directories tab in the Properties sheet for the WWW service of the Internet Information Service Manager. More than one type of default page can be listed by including additional names that are separated by a comma and space (Default.htm, Default.asp, Test.asp, and so forth).

Incorrect Permissions

Make sure that directories that contain ASP files have Execute permissions. To check Execute permissions, follow these steps:
  1. Open the Internet Service Manager and double- click the WWW Service.
  2. Scroll to the directory in question, and then click Properties.
  3. Under Access, click Execute.
Directories that contain script files, such as ASP files, need Execute permissions to run but should not have Read permissions for security reasons. If a directory that contains an ASP file has Read but not Execute permissions, when the Web client requests the ASP file, the ASP script code will be displayed in the browser. Directories that contain HTML files should have Read permissions.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

Misnamed Document
  1. Create or open an existing Web project in Visual InterDev.
  2. Rename the Default.asp or Default.htm to a name that is not listed as one of the Default Documents in Internet Information Service Manager.
  3. Save the renamed file, and preview the project in the browser.
Execute Permissions
  1. Open Internet Service Manager.
  2. On the Directories tab, scroll to a directory that contains ASP files, and open the Properties dialog box.
  3. Clear Execute permissions for the directory in question.
  4. Try to browse the ASP page in the directory without Execute permissions.
NOTE: If the directory contains ASP pages and has only Read permissions, the ASP code will be displayed in the browser.

REFERENCES

For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:

http://support.microsoft.com/search/default.aspx?qu=vinterdev

Modification Type:MajorLast Reviewed:5/2/2006
Keywords:kberrmsg kbprb kbWebServer KB175800
©2004 Microsoft Corporation. All rights reserved.