Re: ASP.NET webs not working
From: Dennis (*NoSpam*impactweb_at_paradise.net.nz)
Date: 09/02/04
- Next message: Jim Buyens: "Re: Update changes in database?"
- Previous message: Thomas A. Rowe: "Re: Hyperlinks (friggin things)"
- In reply to: Kevin Spencer: "Re: ASP.NET webs not working"
- Next in thread: Thomas A. Rowe: "Re: ASP.NET webs not working"
- Reply: Thomas A. Rowe: "Re: ASP.NET webs not working"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 2 Sep 2004 15:36:43 +1200
Thank you Kevin. I am running IIS5.1 on XP PRO SP1
Naturally the folder exists as I can access it via C:\...\wwwroot\... and
localhost and the error message instantly led me to that possibility. I did
not ignore what is being reported. The *few* changes I made to the
application settings were simple and easily reversible in an effort to
eliminate possibilities. As I mentioned, I have no idea on the appropriate
security settings or user rights the ASP.NET user account should have and
didn't want to risk messing with that. The ASP.NET Machine Account is a
member of Users. The Default Web Site in IIS has "Anonymous access" checked.
The default security and applications should be correctly configured by
default when I installed the framework. I don't like and resent having to
tweak or change anything to do with IIS or .NET and prefer if they just ran
normally from the start. IT DIDN'T.
FrontPage03 DIDN'T create the application when I published the web from the
live Internet site to my local XP Pro machine (naturally I let FP create the
web on the localhost not just published to a directory in wwwroot). How
could I publish the site incorrectly???
Everything is set to default settings IIS and .NET. The only difference is
that I created a application for that web in IIS as FP didn't. Like many
issues with software interaction, it should be "pretty darned simple" but
how many times does something simple just not work. E.g.. There is an update
available for my XP OS (SP2) so my auto update says. It is a very simple to
click on that icon in my system tray and install it and Microsoft has made
this process very simple for me but as you probably know, the XP ng is
getting overrun with support questions and problems with SP2. Sometimes
things don't work the way they should.
"Kevin Spencer" <kspencer@takempis.com> wrote in message
news:ebqTMdEkEHA.2948@TK2MSFTNGP11.phx.gbl...
> > "Server cannot access application directory 'c:\inetpub\wwwroot\clt\'.
The
> > directory does not exist or is not accessible because of security
> settings."
>
> Did you determine whether or not the folder exists? Before making all of
> those other changes (heaven knows now how it is all configured), you
should
> have checked that first. Then you would know whether or not it was a
> security issue. If it is a security issue, the answer is relatively
simple:
> Give the ASP.Net user account the necessary permissions.
>
> If you want to work with ASP.Net, you'd better bone up on security.
ASP.Net
> is a fully-compiled technology, and it has security out the wazoo.
>
> > Also, do I need to create an application for every .NET web manually.
> > Shouldn't FP do this for me?
>
> If you create a new web correctly, FrontPage certainly WILL create the
> application for you.
>
> In conclusion, I don't know where you first went off track, but getting
back
> ON track pertty much depends on all of the "off track" stuff you
configured
> being set back as it was before, and it's pretty hard to tell from your
> description. Kind of reminds me of the Tar Baby story. You should have
asked
> first before fooling with your configuration.
>
> Setting up an ASP.Net web site is pretty darned simple with FrontPage.
Just
> install the .Net Framework, install ASP.Net on IIS, and use FrontPage to
> create a new web site. All ASP.Net is is an ISAPI (Internet Server
> Application Programming Interface) that handles requests for .aspx files.
It
> requires an application configured on the web, and ASP.Net to be running
on
> the web server. It runs under a specific User account (what account
depends
> upon what OS your web server is running), and that account must have the
> necessary permissions to do what needs to be done. End of story.
>
> --
> HTH,
> Kevin Spencer
> .Net Developer
> Microsoft MVP
> Big things are made up
> of lots of little things.
>
> "Dennis" <*NoSpam*impactweb@paradise.net.nz> wrote in message
> news:cOmZc.1599$mZ2.137276@news02.tsnz.net...
> > Hi, I solved one problem only to move on to the next one. For a while
now
> I
> > have had problems with my .NET sites not working on my localhost. The
> error
> > I receive when I run the page is:
> >
> > "Server cannot access application directory 'c:\inetpub\wwwroot\clt\'.
The
> > directory does not exist or is not accessible because of security
> settings."
> >
> > I have created and ASP.NET application for the web site via IIS. Tried
> > giving it write permissions, giving it execute permissions for scripts,
> then
> > scripts and executables, basically tried changing many settings to get
the
> > thing to work but no luck. I haven't touched any of the settings for the
> > .NET user account and don't know anything about 'Local Security
Settings'
> to
> > even consider experimenting with it.
> >
> > Does anyone know what's up? Should I just reinstall the .NET framework
> > again? I bypassed installing 1.0 first in favor of just having the one
> > install of 1.1.
> >
> > Also, do I need to create an application for every .NET web manually.
> > Shouldn't FP do this for me? I don't program the pages using FP, just
get
> > the raw aspx and ascx pages from my programmer (VB.NET) and build a site
> and
> > incorporate the design around the pages.
> >
> > Hope someone can help
> > Cheers
> >
> >
>
>
- Next message: Jim Buyens: "Re: Update changes in database?"
- Previous message: Thomas A. Rowe: "Re: Hyperlinks (friggin things)"
- In reply to: Kevin Spencer: "Re: ASP.NET webs not working"
- Next in thread: Thomas A. Rowe: "Re: ASP.NET webs not working"
- Reply: Thomas A. Rowe: "Re: ASP.NET webs not working"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
