|
| |
|
|
and13345
Posts: 100
Joined: 10/7/2003
Status: offline
 |
Upgrading to Windows 2003 Server breaks my site. - 4/16/2004 10:38:58
Our I/T group recently moved my production server from Windows 2000 Server to Windows 2003 Server. In doing so my site no longer works. I get the following error
***********************************************************************
Active Server Pages error 'ASP 0131'
Disallowed Parent Path
/internal/oem_support_priorities/priorities_tracking/Default.asp, line 77
The Include file '../../_fpclass/fpdblib.inc' cannot contain '..' to indicate the parent directory.
***********************************************************************
If I remove the ../../ before the directory it will work, but only if the Page calling the include is at the root of the web.
I am guessing that this is a change MS made for security reasons, but how do I get my site to work again? Most of my pages were created using the FP DRW and I can't just change the path settings because FP will change it back when you save the file.
What are my option? Is there some tool MS has to make the necessary changes to my pages? Do I need some kind of update for FP?.
Can I continue to Develop on my W2K Server and publish to this W2K3 Server?
You input is greatly appreciated.
Keith
|
|
|
|
BeTheBall
Posts: 6381
Joined: 6/21/2002
From: West Point Utah USA
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 4/16/2004 12:46:32
Keith, there is a setting in IIS where one allows/disallows Parent paths. Tell IT to allow them. Here are the steps:
1. Go to your IIS Manager
2. Right click your web site
3. Choose Properties >
4. Select Home Directory Tab
5. Click ‘Configuration’ button
6. Select App Options Tab
7. Check the Enable Parent Paths
8. Click OK and your new configuration will be saved.
Good luck!
_____________________________
Duane
Some people are like Slinkies . . . Not really good for anything . . . . . But they still bring a smile to your face when you push them down a flight of stairs.
| |
|
|
|
kushaljn
Posts: 2
Joined: 5/26/2004
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 5/26/2004 18:29:22
Were you able to solve this problem. My ISP does not want to allow the parent directory. Is there any way around to such a problem. I am having the same problem in the DRW from frontpage
| |
|
|
|
and13345
Posts: 100
Joined: 10/7/2003
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 5/26/2004 18:42:18
The problem I am having is on an internal server managed by myself. I simply emabled parrent paths for my web. I don't know of any workaround.
| |
|
|
|
BeTheBall
Posts: 6381
Joined: 6/21/2002
From: West Point Utah USA
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 5/26/2004 18:55:42
If your host will not enable parent paths, then you will need to use include virtual syntax and spell out the full path from the root of the web. The syntax is like this:
<!--#include virtual="/<virtual path>/<filename.ext>"-->
So if your includes are in the _fpclass folder and that folder is in a folder called MyWeb which is just below the root then the path to your includes would be something like:
<!--#include virtual="/MyWeb/_fpclass/fpdbrgn2.inc"-->
Hope it helps.
_____________________________
Duane
Some people are like Slinkies . . . Not really good for anything . . . . . But they still bring a smile to your face when you push them down a flight of stairs.
| |
|
|
|
Shirley
Posts: 3127
Joined: 1/8/1999
From: Omaha, Ne USA
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 5/26/2004 19:04:10
Or drag the necessary files fpdbrgn2.inc etc into the same folder as the page.
_____________________________
Everything But Cake
| |
|
|
|
kushaljn
Posts: 2
Joined: 5/26/2004
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 5/27/2004 17:20:41
Thanks for your replies. The virtual path works very fine and sweetly for all the ASP pages which I have created. But for the pages which are getting created by Frontpage For Eg. Files in "Editor" folder under "XXXX_interface" Folder I can not edit these files. Even though I try to edit these pages, when I hit save it says The contents of the Frontpage have been changed they will be changed back and the annoying part is it comes back to original state.
I tried to add the code from fpdbrgn2.inc and other files in the page but then you can not get rid of the include line from the code. Seems like this is a catch-22. I am sure MS must have thought of this problem before coming out with windows 2003 and not enabling the parent paths. I do realize there are security concerns because of this but then what happens to the database wizard from FrontPage.
Any answers would be welcome.
| |
|
|
|
Scottie
Posts: 18
From: San Jose CA USA
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 2/13/2006 16:59:22
Does this mean that DRW stuff can no longer be used with Windows 2003 with Parent Paths disabled?
Strange because on my site most of my DRW stuff broke when I upgraded to 2003, except for one page that still works.
Oh, nevermind. It just occurred to me that the reason that single page continues to work is because it's in the root folder.
Ok, I guess I'll put the rest of the DRWs on the spooky diet and change to virtual explicit paths.
Thanks for your posts on this topic. I was going nuts trying to figure it out!!
_____________________________
| |
|
|
|
evansforsyth
Posts: 277
Joined: 12/11/2001
From: Grande Prairie, Alberta, Canada
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 7/21/2006 13:29:46
Having the same problem--but unable to understand the solution!
quote:
<!--#include virtual="/MyWeb/_fpclass/fpdbrgn2.inc"-->
- Where does this line go?
- In the page's Header or in the DIW code?
- There are four files in the _fpclass folder. How is that handled?
- Can the code be added in one location so it covers multiple pages? Kinda like CSS?
- my physical path is /d:/virtuals/CWH/abfind_com/jasonscott_net/Web
Sorry to be so clueless!
- Here is the offending code.
----------------------------------------
<!--webbot bot="DatabaseRegionStart" s-columnnames="ID,FirstName,LastName,Company,Address1,City,State,PostalCode,WorkPhone,ContactDate,Comment" s-columntypes="3,202,202,202,202,202,202,202,202,135,203" s-dataconnection="JasonScott" b-tableformat="TRUE" b-menuformat="FALSE" s-menuchoice="ID" s-menuvalue="ID" b-tableborder="TRUE" b-tableexpand="TRUE" b-tableheader="TRUE" b-listlabels="TRUE" b-listseparator="TRUE" i-listformat="0" b-makeform="TRUE" s-recordsource="Sphere" s-displaycolumns="ID,FirstName,LastName,Company,Address1,City,State,PostalCode,WorkPhone,ContactDate,Comment" s-criteria s-order="[FirstName] +" s-sql="SELECT * FROM Sphere ORDER BY FirstName ASC" b-procedure="FALSE" clientside suggestedext="asp" s-defaultfields s-norecordsfound="No records returned." i-maxrecords="1000" i-groupsize="500" botid="0" u-dblib="../../../_fpclass/fpdblib.inc" u-dbrgn1="../../../_fpclass/fpdbrgn1.inc" u-dbrgn2="../../../_fpclass/fpdbrgn2.inc" tag="TBODY" startspan preview="<tr><td colspan=64 bgcolor="#FFFF00" width="100%"><font color="#000000">This is the start of a Database Results region.</font></td></tr>" b-WasTableFormat="TRUE" --><!--#include file="../../../_fpclass/fpdblib.inc"-->
<% if 0 then %>
<SCRIPT Language="JavaScript">
document.write("<div style='background: yellow; color: black;'>The Database Results component on this page is unable to display database content. The page must have a filename ending in '.asp', and the web must be hosted on a server that supports Active Server Pages.</div>");
</SCRIPT>
<% end if %>
<%
fp_sQry="SELECT * FROM Sphere ORDER BY FirstName ASC"
fp_sDefault=""
fp_sNoRecords="<tr><td colspan=11 align=""LEFT"" width=""100%"">No records returned.</td></tr>"
fp_sDataConn="JasonScott"
fp_iMaxRecords=1000
fp_iCommandType=1
fp_iPageSize=500
fp_fTableFormat=True
fp_fMenuFormat=False
fp_sMenuChoice="ID"
fp_sMenuValue="ID"
fp_sColTypes="&ID=3&FirstName=202&LastName=202&Company=202&Address1=202&City=202&State=202&PostalCode=202&WorkPhone=202&ContactDate=135&Comment=203&"
fp_iDisplayCols=11
fp_fCustomQuery=False
BOTID=0
fp_iRegion=BOTID
%>
<!--#include file="../../../_fpclass/fpdbrgn1.inc"-->
<!--webbot bot="DatabaseRegionStart" endspan i-checksum="41817" -->
------------------------------------
Any help would really be appreciated! I'm frustrated into the ground!
The host is not willing to turn on the parent directory. This is on a DIW-created page. The site has scores of such pages--so the Spooky Diet isn't the preferred solution!
Many thanks!
Evans
< Message edited by rdouglass -- 7/21/2006 14:29:37 >
| |
|
|
|
rdouglass
Posts: 9280
From: Biddeford, ME USA
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 7/21/2006 14:28:33
quote:
<!--#include virtual="/MyWeb/_fpclass/fpdbrgn2.inc"-->
That line would replace this line:
<!--#include file="../../../_fpclass/fpdblib.inc"-->
but you don't have it on the page. See when the <!--#include file="blah is used, everyhthing is based from where that file actually is located in the web. When you use 'virtual', everything is relative from the root of the web.
So when Windows 2003 turns off parent paths by default, the file paths that use "../" no longer work so you fix them by making includes based at the root of the web and then using the path accordingly from the root.
That make sense or did I loose you? If not then;
So each place there is a <!--#include file and a "../" in the path need to be 'fixed' similarly and not just the one.
That help any?
_____________________________
Don't take you're eye off your final destination.
ASP Checkbox Function Tutorial.
| |
|
|
|
evansforsyth
Posts: 277
Joined: 12/11/2001
From: Grande Prairie, Alberta, Canada
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 7/21/2006 15:04:57
Thanks! Almost there! A great help!
With the following physical FTP path, to the site itself, what would that line of code look like?
/d:/virtuals/CWH/abfind_com/jasonscott_net/Web
<!--#include virtual="/Web/_fpclass/fpdbrgn2.inc"-->
or maybe
<!--#include virtual="/jasonscott_net/_fpclass/fpdbrgn2.inc"-->
So far nothing seems to work! For example, if the second "maybe" try at the code is used . . . then when the page is saved it reverts back to the original!
Thanks
Evans
< Message edited by evansforsyth -- 7/21/2006 15:27:26 >
| |
|
|
|
rdouglass
Posts: 9280
From: Biddeford, ME USA
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 7/21/2006 15:27:32
It has everything to do with the root of the web. Where is the root and how do you get from the root to the file.
IOW most FP files are installed from the root so most times (*not* all times) you can just use:
<!--#include virtual="/_fpclass/fpdbrgn2.inc"-->
Does that one work?
_____________________________
Don't take you're eye off your final destination.
ASP Checkbox Function Tutorial.
| |
|
|
|
evansforsyth
Posts: 277
Joined: 12/11/2001
From: Grande Prairie, Alberta, Canada
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 7/21/2006 15:35:30
Nope. Tried it without the / and with the / (<!--#include virtual="_fpclass/fpdbrgn2.inc"--> .
Each time got the "Contents will be overwritten when you save the page" message.
| |
|
|
|
evansforsyth
Posts: 277
Joined: 12/11/2001
From: Grande Prairie, Alberta, Canada
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 7/21/2006 16:25:33
OK--but with the number of DIWs in the site (20) using the Diet isn't a cure I relish! Particularly since the customer often asks for changes in the DIW.
Surely MicroSoft has a solution--their FrontPage and their server security . . . (Foolish me, it is MicroSoft, sorry.)
Am I to take it that you are not aware of anything else to try?
Thanks
Evans
| |
|
|
|
evansforsyth
Posts: 277
Joined: 12/11/2001
From: Grande Prairie, Alberta, Canada
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 7/21/2006 16:46:42
Here's a question.
How does the new Expression web builder handle parent paths being turned off?
| |
|
|
|
evansforsyth
Posts: 277
Joined: 12/11/2001
From: Grande Prairie, Alberta, Canada
Status: offline
|
RE: Upgrading to Windows 2003 Server breaks my site. - 7/22/2006 2:04:38
Partial Solution:
For sites already created with one DIW, only.
After creating a DIW, drag and drop the results_page.asp file in with the "Editor" folder files.
Then Click/Drag/Move the four _fpclass ".inc" files into the "Editor" folder--this will point most of the DIW links to the same folder. That way pathing won't even be used!
Then Click/Drag/Copy the four ".inc" files back to the _fpclass folder. (Use the CTRL key.) This is so you can use the same trick when you create the next DIW.
Then go in and fix the "delete.asp" file--it won't update the path! Use Find/Replace to find the ../../_fpclass and replace it with nothing.
Now the DIW will work just fine--and you can create new DIWs using the same technique.
Unfortunately, this is a partial solution. It won't fix multiple DIWs that have already been created. Better find a cooperative webhost who will set it up with the parent paths allowed! (See Spooky's post above.)
Many thanks--sure appreciate your support and help.
| |
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
k¥ 
