DIW creating path to root site instead of current site

[Bill M]

I am unable to create working databases on any of the sites on my 2003
virtual server. These sites were created as new 2002 server extensions web
sites, not sub sites. I am getting the same error as noted in the post
called "FrontPage Database Interface Wizard", posted by Bob on 3/29/2007:
"The Include file '../../../_fpclass/fpdblib.inc' cannot contain '..' to
indicate the parent directory."

The resolution would be fine, I'm sure, if I actually was housing my
databases in the root web. As each site is independent and has its own IP,
I'm not sure what is configured incorrectly that would make FrontPage 2003
think it needs to use the fpdblib.inc file from the root web instead of the
current site, even though I select the check box to add to the current site.

Is there a way I can correct this path so it knows it should use the
_fpclass/fpdblib.inc file in the current web instead? I know I can't change
the web bot. Is there somewhere this is configurable? Any guidance anyone
can provide is greatly appreciated.

 

[Ronx]

"The Include file '../../../_fpclass/fpdblib.inc' cannot contain '..' to
indicate the parent directory."

This indicates that Parent Paths are not allowed on the server. Regardless
of which folder the path is pointing to, the DIW cannot be used, since the
DIW always uses Parent Paths in one or more of the files in the _fpclass
folder.

Whether Parent Paths are allowed or not is a setting on the server, in IIS
configuration. Many hosts disallow Parent Paths for security reasons - it is
too easy to access a folder outside the website.

The depth of the path ( ../../../ ) indicates that the page using the DIW is
three folder levels down from the root application - one or two is normal,
and another "source" for the Parent Paths problem. The path is from the asp
Aplication root to the page, the depth of folders could be because the
application root is the folder above the root folder for the website. The
Application Root should (normally) be the same folder as the website root
folder. This setting is normally correctly applied when the FP extensions
are installed, or a subweb created - subwebs have their own asp
applications.

Your only options are:
1) Allow Parent Paths on the server (then investigate the actual paths used)
2) Write your own scripts instead of using the DIW
3) Change to a new host who does allow Parent Paths

--
Ron Symonds
Microsoft MVP (Expression)
http://www.rxs-enterprises.org/fp

Reply only to group - emails will be deleted unread.

 

[Bill M]

Ron,

Thanks for your reply. I have already implemented option 1, since I also
control the server to get me by for now.

I am, in fact, in the process of learning to code my own scripts using ADO.
Just haven't had much time to devote to learning it yet.

Lastly, someone had recently suggested that each of my websites should have
their own application pool instead of using the default application pool.
Would this have anything to do with correcting the path? Would this give it
its own asp application, as you describe above?
--
Thanks,
Bill M

"The Include file '../../../_fpclass/fpdblib.inc' cannot contain '..' to
indicate the parent directory."

This indicates that Parent Paths are not allowed on the server. Regardless
of which folder the path is pointing to, the DIW cannot be used, since the
DIW always uses Parent Paths in one or more of the files in the _fpclass
folder.

Whether Parent Paths are allowed or not is a setting on the server, in IIS
configuration. Many hosts disallow Parent Paths for security reasons - it is
too easy to access a folder outside the website.

The depth of the path ( ../../../ ) indicates that the page using the DIW is
three folder levels down from the root application - one or two is normal,
and another "source" for the Parent Paths problem. The path is from the asp
Aplication root to the page, the depth of folders could be because the
application root is the folder above the root folder for the website. The
Application Root should (normally) be the same folder as the website root
folder. This setting is normally correctly applied when the FP extensions
are installed, or a subweb created - subwebs have their own asp
applications.

Your only options are:
1) Allow Parent Paths on the server (then investigate the actual paths used)
2) Write your own scripts instead of using the DIW
3) Change to a new host who does allow Parent Paths

--
Ron Symonds
Microsoft MVP (Expression)
http://www.rxs-enterprises.org/fp

Reply only to group - emails will be deleted unread.

 

[Ronx]

That is exactly what I was trying to refer to.
--
Ron Symonds
Microsoft MVP (Expression)
http://www.rxs-enterprises.org/fp

Reply only to group - emails will be deleted unread.

Ron,

Thanks for your reply. I have already implemented option 1, since I also
control the server to get me by for now.

I am, in fact, in the process of learning to code my own scripts using
ADO.
Just haven't had much time to devote to learning it yet.

Lastly, someone had recently suggested that each of my websites should
have
their own application pool instead of using the default application pool.
Would this have anything to do with correcting the path? Would this give
it
its own asp application, as you describe above?

 

[Bill M]

Ron,

Thanks for the clarification and your direction. I did get this working by
enabling the parent path on my sites, at least for now. As time allows
between projects, I will try to pursue individual application pools for each
site.