See if the following helps:
Open IIS Manager
Expand Web Sites
Right Click on Default Web Site
Select Properties
Select Home Directory
Under Application Settings, click Remove, then click Create
If you have Norton Security / Anti-Virus install, there is a script blocking setting that you have
disable.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
"Earl Partridge" <(E-Mail Removed)> wrote in message
news:9jfIc.13306$(E-Mail Removed)...
> According the Microsoft's page:
> "To enable ASP pages
> 1.
> In IIS Manager, expand the local computer, and then click Web Service
> Extensions.
>
> 2.
> In the details pane, click Active Server Pages, and then click Allow.
>
> I open IIS, expand the local computer but do not have Web Service
> Extensions.
> Two folders exist, Web Sites and Default SMTP Virtual Server.
> Expanded both
> of those and neither provide Web Service Extensions managment.
>
> What am I missing?
>
>
>
>
> "Andrew Murray" <(E-Mail Removed)> wrote in message
> news:40ee5627$0$1298$(E-Mail Removed)...
> > IIS is installed from Add/Remove Programs > Windows Setup.....etc It is on
> the
> > Windows XP Pro install disk.
> >
> >
> > "Thomas A. Rowe" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Out of the box IIS supports ASP and installs the FP2000 extensions.
> > >
> > > --
> > > ==============================================
> > > Thomas A. Rowe (Microsoft MVP - FrontPage)
> > > WEBMASTER Resources(tm)
> > > http://www.ycoln-resources.com
> > > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
> > > ==============================================
> > > To assist you in getting the best answers for FrontPage support see:
> > > http://www.net-sites.com/sitebuilder/newsgroups.asp
> > >
> > > "Earl Partridge" <(E-Mail Removed)> wrote in message
> > > news:ImeHc.6607$(E-Mail Removed)...
> > > > Would that server be the IIS 5.1 that was included with XP Pro?
> > > > And any suggestion as to how to get ASP supported?
> > > > I've been searching MS KBs and every attempt to download FP 2000
> > > > Extensions indicates that I either already have or don't need the item
> > > > I'm asking for.
> > > > Earl
> > > >
> > > >
> > > > "Jens Peter Karlsen[FP MVP]" <(E-Mail Removed)> wrote in message
> > > > news:(E-Mail Removed)...
> > > > > No, you don't need to use the Wizard. Just write your own ASP to
> interact
> > > > with the DB.
> > > > >
> > > > > From your simple test though it appears that ASP are not supported
> on the
> > > > Server.
> > > > >
> > > > >
> > > > > Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
nntp://msnews.microsoft.com/microsoft.public.frontpage.client/<locHc.6451$(E-Mail Removed)>
> > > > >
> > > > > Frontpage 2000, Access 2000, XP Pro
> > > > >
> > > > > Just upgraded to XP Pro. In the past, with Windows 98 all my
> databases
> > > > were
> > > > > stored in a central (root type) folder called DB, and all database
> > > > > connections
> > > > > worked fine. Now with XP (Using built in IIS), with new hard drive,
> etc.,
> > > > I
> > > > > can not
> > > > > access any of my databases. I have used ODBC to set the DSN.
> > > > >
> > > > > After reading most of the messages in this newsgroup, it appears
> that
> > > > > perhaps
> > > > > the database needs to reside on each individual web... in the
> "fpdb"
> > > > folder.
> > > > > I
> > > > > have never used the Database Interface Wizard in the past. Do I
> need to
> > > > use
> > > > > that and keep the database in a folder named fpdb?
> > > > >
> > > > > I have a feeling it has to do with ASP and Frontpage. I just
> created a
> > > > > test.asp
> > > > > page with a Response.Write "Hello World", and nothing was written.
> > > > >
> > > > >
> > > > >
> > > > > [microsoft.public.frontpage.client]
> > > >
> > > >
> > >
> > >
> >
> >
>
>