ASP Errors

Since upgrading to Windows 2003 Server from Windows 2000
Enterprise Server we have had alot of ASP problems. The
problems are centered around asp pages which are one level
or more below the main folder within a web site. We have
many web sites which have used the database interface
wizard in FrontPage which puts these pages up to three
levels deep inside the folder hierarchy of the main site.
The pages will not work with IIS 6. I have had to re-
engineer many of these sites without the database
interface wizard. My solution at this point is to put all
ASP pages at the root level which seems to work but
negates all version of Frontpage management including
FrontPage 2003 Beta. This is a serious problem!
Especially for us who teach FrontPage and ASP!

Ray
Mon Sep 15 15:37:09 CDT 2003

What errors?

Drop Frontpage man!

Ray at work

"David Jacobus" <davidjacobus@hotmail.com> wrote in message
news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...
> Since upgrading to Windows 2003 Server from Windows 2000
> Enterprise Server we have had alot of ASP problems. The
> problems are centered around asp pages which are one level
> or more below the main folder within a web site. We have
> many web sites which have used the database interface
> wizard in FrontPage which puts these pages up to three
> levels deep inside the folder hierarchy of the main site.
> The pages will not work with IIS 6. I have had to re-
> engineer many of these sites without the database
> interface wizard. My solution at this point is to put all
> ASP pages at the root level which seems to work but
> negates all version of Frontpage management including
> FrontPage 2003 Beta. This is a serious problem!
> Especially for us who teach FrontPage and ASP!

David
Mon Sep 15 15:49:03 CDT 2003

HTTP 500 - Internal Server Error
>-----Original Message-----
>What errors?
>
>Drop Frontpage man!
>
>Ray at work
>
>"David Jacobus" <davidjacobus@hotmail.com> wrote in
message
>news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...
>> Since upgrading to Windows 2003 Server from Windows 2000
>> Enterprise Server we have had alot of ASP problems. The
>> problems are centered around asp pages which are one
level
>> or more below the main folder within a web site. We
have
>> many web sites which have used the database interface
>> wizard in FrontPage which puts these pages up to three
>> levels deep inside the folder hierarchy of the main
site.
>> The pages will not work with IIS 6. I have had to re-
>> engineer many of these sites without the database
>> interface wizard. My solution at this point is to put
all
>> ASP pages at the root level which seems to work but
>> negates all version of Frontpage management including
>> FrontPage 2003 Beta. This is a serious problem!
>> Especially for us who teach FrontPage and ASP!
>
>
>.
>

Ray
Mon Sep 15 15:50:24 CDT 2003

http://www.aspfaq.com/2109

Ray at work

"David Jacobus" <davidjacobus@hotmail.com> wrote in message
news:05fd01c37bca$cc6a3ab0$a101280a@phx.gbl...
> HTTP 500 - Internal Server Error
> >-----Original Message-----
> >What errors?
> >
> >Drop Frontpage man!
> >
> >Ray at work
> >
> >"David Jacobus" <davidjacobus@hotmail.com> wrote in
> message
> >news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...
> >> Since upgrading to Windows 2003 Server from Windows 2000
> >> Enterprise Server we have had alot of ASP problems. The
> >> problems are centered around asp pages which are one
> level
> >> or more below the main folder within a web site. We
> have
> >> many web sites which have used the database interface
> >> wizard in FrontPage which puts these pages up to three
> >> levels deep inside the folder hierarchy of the main
> site.
> >> The pages will not work with IIS 6. I have had to re-
> >> engineer many of these sites without the database
> >> interface wizard. My solution at this point is to put
> all
> >> ASP pages at the root level which seems to work but
> >> negates all version of Frontpage management including
> >> FrontPage 2003 Beta. This is a serious problem!
> >> Especially for us who teach FrontPage and ASP!
> >
> >
> >.
> >

Tom
Mon Sep 15 16:10:22 CDT 2003

I think since he's teaching it, he can't really drop it.

Now I'm not familiar with Frontpage or even Win2003, but I believe there's a
setting in 2003 that is on by default (off by default in 2000) for
references to Parent directories.
If Frontpage is anything like interdev, then by default it references files
in a goofy manner. Often, I'll get things like
"../../Home/something/Default.asp" which is really in the same folder I'm
already in (up two down two), which I'm sure would cause a problem in 2003.



"Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
news:ODM7jk8eDHA.2328@TK2MSFTNGP09.phx.gbl...
> What errors?
>
> Drop Frontpage man!
>
> Ray at work
>
> "David Jacobus" <davidjacobus@hotmail.com> wrote in message
> news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...
> > Since upgrading to Windows 2003 Server from Windows 2000
> > Enterprise Server we have had alot of ASP problems. The
> > problems are centered around asp pages which are one level
> > or more below the main folder within a web site. We have
> > many web sites which have used the database interface
> > wizard in FrontPage which puts these pages up to three
> > levels deep inside the folder hierarchy of the main site.
> > The pages will not work with IIS 6. I have had to re-
> > engineer many of these sites without the database
> > interface wizard. My solution at this point is to put all
> > ASP pages at the root level which seems to work but
> > negates all version of Frontpage management including
> > FrontPage 2003 Beta. This is a serious problem!
> > Especially for us who teach FrontPage and ASP!
>
>

Tom
Tue Sep 16 07:55:58 CDT 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;332117


"Tom B" <shuckle@hotmail.com> wrote in message
news:%23yyhJ38eDHA.2352@TK2MSFTNGP09.phx.gbl...
> I think since he's teaching it, he can't really drop it.
>
> Now I'm not familiar with Frontpage or even Win2003, but I believe there's
a
> setting in 2003 that is on by default (off by default in 2000) for
> references to Parent directories.
> If Frontpage is anything like interdev, then by default it references
files
> in a goofy manner. Often, I'll get things like
> "../../Home/something/Default.asp" which is really in the same folder I'm
> already in (up two down two), which I'm sure would cause a problem in
2003.
>
>
>
> "Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
> news:ODM7jk8eDHA.2328@TK2MSFTNGP09.phx.gbl...
> > What errors?
> >
> > Drop Frontpage man!
> >
> > Ray at work
> >
> > "David Jacobus" <davidjacobus@hotmail.com> wrote in message
> > news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...
> > > Since upgrading to Windows 2003 Server from Windows 2000
> > > Enterprise Server we have had alot of ASP problems. The
> > > problems are centered around asp pages which are one level
> > > or more below the main folder within a web site. We have
> > > many web sites which have used the database interface
> > > wizard in FrontPage which puts these pages up to three
> > > levels deep inside the folder hierarchy of the main site.
> > > The pages will not work with IIS 6. I have had to re-
> > > engineer many of these sites without the database
> > > interface wizard. My solution at this point is to put all
> > > ASP pages at the root level which seems to work but
> > > negates all version of Frontpage management including
> > > FrontPage 2003 Beta. This is a serious problem!
> > > Especially for us who teach FrontPage and ASP!
> >
> >
>
>

David
Tue Sep 16 12:40:07 CDT 2003

WOW! Thanks so much for helping us with this problem, we
are in business now. Again Thanks
>-----Original Message-----
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;332117
>
>
>"Tom B" <shuckle@hotmail.com> wrote in message
>news:%23yyhJ38eDHA.2352@TK2MSFTNGP09.phx.gbl...
>> I think since he's teaching it, he can't really drop it.
>>
>> Now I'm not familiar with Frontpage or even Win2003,
but I believe there's
>a
>> setting in 2003 that is on by default (off by default
in 2000) for
>> references to Parent directories.
>> If Frontpage is anything like interdev, then by default
it references
>files
>> in a goofy manner. Often, I'll get things like
>> "../../Home/something/Default.asp" which is really in
the same folder I'm
>> already in (up two down two), which I'm sure would
cause a problem in
>2003.
>>
>>
>>
>> "Ray at <%=sLocation%>" <myfirstname at lane34 dot com>
wrote in message
>> news:ODM7jk8eDHA.2328@TK2MSFTNGP09.phx.gbl...
>> > What errors?
>> >
>> > Drop Frontpage man!
>> >
>> > Ray at work
>> >
>> > "David Jacobus" <davidjacobus@hotmail.com> wrote in
message
>> > news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...
>> > > Since upgrading to Windows 2003 Server from Windows
2000
>> > > Enterprise Server we have had alot of ASP
problems. The
>> > > problems are centered around asp pages which are
one level
>> > > or more below the main folder within a web site.
We have
>> > > many web sites which have used the database
interface
>> > > wizard in FrontPage which puts these pages up to
three
>> > > levels deep inside the folder hierarchy of the main
site.
>> > > The pages will not work with IIS 6. I have had to
re-
>> > > engineer many of these sites without the database
>> > > interface wizard. My solution at this point is to
put all
>> > > ASP pages at the root level which seems to work but
>> > > negates all version of Frontpage management
including
>> > > FrontPage 2003 Beta. This is a serious problem!
>> > > Especially for us who teach FrontPage and ASP!
>> >
>> >
>>
>>
>
>
>.
>