Re: Web application causes Web Access Failed message

From: Simon Jefferies (simon_at_cooltoolsonline.co.uk)
Date: 04/14/04


Date: Wed, 14 Apr 2004 22:01:43 +0100

Thanks for your reply,

> When you set the IIS default webserver's ip as unassigned and port as
> 81and
> create a web project, have you changed the default location
> (http://localhost/WebApplication[n]) to
> http://localhost:81/WebApplication[n] ?
> If not, the VS.NET will use the 80 default port to connect the IIS default
> site.

I tried the http://localhost:81/webapplication[n], things have progressed.
I got an error about ASP .NET 1.1 not being installed, so I installed it by
running the asp_regiis program as mentioned in MSDN.

> Also, I suspect that whether your default site's HOme directory's
> LocalPath
> (by default should be "[system disk]:\inetpub\wwwroot) has been changed to
> other location. IF so, since the VS.NET will by default mapping the
> default
> site's localhost address to the [x]:\inetpub\wwwroot, it'll unable to
> locate it. So please check it in the IIS.

My local path is: c:\inetpub\wwwroot

> In addition, there're some former cases on this problem which is caused by
> firewall security was tightened and the setting in the browser was not
> checked to by pass the proxy when making a request to the local host. You
> may try going to tools/options/internet connections/ and click LAN
> settings in IE. Then
> check bypass proxy server for local addresses.
>

Checked this item in the settings.

> Further more, please restarting the IIS server and then visit the default
> IIS site via the http://localhost/ (if the port is 80) to see whether the
> IIS is running correctly. Thanks.

This is where the problems are. When I try to create the web project, i get
"The Web server reported the following error when attempting to create or
open the Web project located at the following URL:
'http://localhost:81/WebApplication1'. 'HTTP/1.1 403 Access Forbidden'.

When I restarted the IIS, and visited http://localhost:81, I get "The page
cannot be displayed" with the following message: "HTTP 403.1 Forbidden:
Execute Access Forbidden Internet Information Services".

Any ideas how to solve this issue?

Simon Jefferies
Tools Programmer, Headfirst Productions
mailto:simonj@headfirst.co.uk
-

"Steven Cheng[MSFT]" <v-schang@online.microsoft.com> wrote in message
news:gWte$VfIEHA.3636@cpmsftngxa06.phx.gbl...
> Hi Simon,
>
> Since you created the webproject locally, I think this will be helpful
> that
> we needn't worry about the remote shared scenario which may cause security
> issues.
>
> When you set the IIS default webserver's ip as unassigned and port as
> 81and
> create a web project, have you changed the default location
> (http://localhost/WebApplication[n]) to
> http://localhost:81/WebApplication[n] ?
> If not, the VS.NET will use the 80 default port to connect the IIS default
> site.
>
> Also, I suspect that whether your default site's HOme directory's
> LocalPath
> (by default should be "[system disk]:\inetpub\wwwroot) has been changed to
> other location. IF so, since the VS.NET will by default mapping the
> default
> site's localhost address to the [x]:\inetpub\wwwroot, it'll unable to
> locate it. So please check it in the IIS.
>
> In addition, there're some former cases on this problem which is caused by
> firewall security was tightened and the setting in the browser was not
> checked to by pass the proxy when making a request to the local host. You
> may try going to tools/options/internet connections/ and click LAN
> settings in IE. Then
> check bypass proxy server for local addresses.
>
> Further more, please restarting the IIS server and then visit the default
> IIS site via the http://localhost/ (if the port is 80) to see whether the
> IIS is running correctly. Thanks.
>
> Regards,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx
>
>
>
>



Relevant Pages

  • Re: .Net 2.0 website is running on a different port?
    ... server instance a random local port by default, ... If you want to develop the ASP.NET application in IIS directly, ... choose "http" when you create the web project and select the proper virtual ... configuration. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: .Net 2.0 website is running on a different port?
    ... The server won't care if the app was running through a different port in development. ... As for the ASP.NET 2.0 web projects, you can create it through both IIS ... after you use "http"/IIS to create the web project ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: .Net 2.0 website is running on a different port?
    ... how do i move my website and solution from the test server to IIS so i can ... server instance a random local port by default, ... after you use "http"/IIS to create the web project ...
    (microsoft.public.dotnet.framework.aspnet)
  • Turn Off SSL
    ... for secure communications. ... replace 8000 with any other port you choose) ... Restart IIS. ... >settings for the Secure identities are not enabled. ...
    (microsoft.public.inetserver.iis.security)
  • Cant create new project on local server
    ... I'm having trouble creating a new Web project using VS .NET 2003 on ... A possible cause of this error is insufficient access rights to ... "Unable to set permissions on the 'bin' folder to restrict browse ... Settings", I have the "Preferred Access Method" set to "File Share", ...
    (microsoft.public.dotnet.framework.aspnet)