Re: HTTP 403.1 Forbidden: Execute Access Forbidden

From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 08/28/04 

Date: Fri, 27 Aug 2004 20:33:07 -0700

This sounds like an Visual InterDev behavior/requirement -- I really have no
idea what it should be.

However, IIS does not care about the setting you describe (other than to
execute ASP script, you MUST have the "Scripts" execute permission [so
scripts and executables is not necessary to run the default.asp page]).

Whether Virtual InterDev and FrontPage likes your change or not -- that is
between you and those products. IIS is merely doing what you configured. 

-- 
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"blogman" <blogman@newsgroup.nospam> wrote in message
news:6A7DCF00-9D2C-4D5D-90DA-5ED04003B38E@microsoft.com...
Hi,
I am running Windows 2000 Pro, Ver. 5.0.2195, SP 4, Build 2195 (IIS 5.0).
Using the Computer management tool I have modified the Execute Permissions
parameter, that lives under the Home Directory tab, to include both scripts
and executables. I have done this both at the top level (IIS level) and at
the the default web page level. Front page server extensions are loaded. I
am
using the default script designations. I have created a default.asp script
under c:\inetpub\wwwroot. I am trying to load the site into an Visual
InterDev 6.0 project in master mode using the Web Project Wizard. At the
dialog box entitlrd "Select Your Web", I am selecting "Connect to an
existing
Web Application". When I hit the finish button I receive the following
Interdev error messae:
"Unable to rereive folder information from the server. An HTTP error has
occurred. The sever could not complete your request. ......make sure that
server has Front Page Server Extensions installed and that Web application
exists on the srver."
If I then try to load the Web page in the browser I receive the following
browser error: "HTTP 403.1 Forbidden: Execute Access Forbidden". Then I
return to computer management and the Execute Permissions parameter at the
default web page level has reverted to "None".
It appears as though Interdev is resetting the parameter, because if I reset
the parameter to include both scripts and executables, I can once again
successfully access the web site.
Anyone have any thoughts?
Regards,
blogman
Loading