Windows 2003 Server + Frontpage 2002 (Full Version)

All Forums >> [Web Development] >> ASP and Database



Message

Valaire -> Windows 2003 Server + Frontpage 2002 (6/11/2003 0:52:55)

Hi, my webhost just upgraded my website to Windows 2003 and now ASP frontpage-based webpages will not work and report an error.

An example of this can be found at:

http://www.apxonline.com/window/distresults.asp?Name=B.J.%20Wolfe

Same type of error can be found on my ASP subdomain script:

http://database.apxonline.com

Any clue what I should tell my host?

I believe the 2002 extensions are installed, even though they liked to keep them at 2000 for stability.

Thanks,
Chad



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 12:45:03)

Can anyone please help me with this? It' s been a couple days and I' ve found only one other post on this website dealing with a problem with Windows 2003. All of my FP-based ASP scripts -no longer- work due to this parent path error, and sometimes mappath error. The spooky login no longer works either.

My webhost is completely confused and had no idea there would be a problem with 2003 and Frontpage, as it seems I am the guinea pig.

Does -anyone- here have Windows 2003 Server with Frontpage, and do your DRW pages and other ASP scripts work?

Any help would be appreciated, as I decide what my options are from this point.

Chad



bobby -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 14:14:35)

This is a total shot in the dark... I haven' t played with a 2003 server yet...

Have you tried saving one of your ASP pages with a .aspx extension and then run it?

I doubt if this has anything to do with it, but might be worth a shot...

.aspx is the extension for ASP.NET - ASP pages should still function under an .aspx extn... maybe Server 2003 is confused and wants to look for ASP.NET pages instead of " classic ASP" ?



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 14:31:17)

Tried and a no go -- application error.

Thanks though. :>

- Chad



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 14:53:39)

The basic problem is that 2003 is preventing my pages from accessing the Frontpage includes files in rootdirectory/_fpclass/.... the webbot makes a relative path to the directory on the fly, using ../_fpclass/
but Win2k3 will not allow it to use .. to indicate parent directory. I don' t know why but it won' t let you use relative locations, I can' t try an absolute location, because as far as I know, I can' t get the webbot to write anything different than it was originally intended.



bobby -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 14:57:27)

Hmmm....

I' ve been all over their website, and I didn' t see anything relating to FP 2K2 and Server ' 03.

They have all sorts of downloads and patches for Server 2K, but nothing newer...

Have you tried using an SSI (Server Side Include) rather than FP include? There are differences, but they are subtle and it may be the key to getting your pages to work, at least until you can get this figured out?



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 14:59:57)

I could rewrite all of the DRW pages into pure ASP but:

1. It will take a considerable amount of time.
2. I have no gaurantees that another error will not pop up.

Thus my dilemma.

How could this server be released with such an utterly basic bug that disrupts core Frontpage functions?

- Chad, " The Win2k3 Guinea Pig" :p



bobby -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 15:06:19)

Changing to SSI wouldn' t require re-writing your ASP/DRW code (I don' t think...)

Just replace the FP Include bot code in HTML view with:

<!--#include file=" pathtofile/filename.htm" -->

In the filename.htm you would need to delete the <html> <head> and <body> tags, just leaving the " meat" of the page... since an SSI won' t parse those out like the FP bots...

Whatever is in the included file will be " copy-pasted" into the parent page by the server prior to processing ASP/DRW code.

but other than that it should function just fine in an ASP page, regardless of whether or not it' s DRW or hand coded...

It may still be a daunting task to replace all of the FP Include bots with SSI, but it might work to get your site running agin until you can figure out what the problem is...

I' d start with one or two key pages just to test it out (make backup copies of course)

I' m kind of surprised that ../ doesn' t work tho...


[8|]



bobby -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 15:08:23)

quote:

How could this server be released with such an utterly basic bug that disrupts core Frontpage functions?


Variations of that same question have been asked since the release of Win 3.0

[;)]



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 15:20:19)

I' m trying to strip down the webbot at the moment and work in notepad to see if I can get the hard path in for the includes to see if it works.

- Chad



Gil -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 15:53:52)

quote:

How could this server be released with such an utterly basic bug that disrupts core functions?


ROTFLMAO!

Can you spell M-i-c-r-o-s-o-f-t ?



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 15:56:25)

Well the general consensus has it, I' ve been microsofted. Anyone know why the absolute path to my include path also won' t work?

http://www.apxonline.com/window/distributors.asp

Thanks,
Chad



bobby -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 16:16:46)

quote:

I' ve been microsofted

LOL!

Sorry I don' t have any more ideas... keep me posted tho, I' m curious how this works out...

At a guess, I' d say there is a patch due for FP extns on Server 2K3 [sm=tongue.gif]



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/13/2003 17:33:21)

I have found a guide at Microsoft' s website that details every change made to 2003, and due to the security blitz, many of the changes are going to mess up existing applications/code... they have some workarounds listed. I' m seeing if my webhost can make sense of it but I doubt it.

Design Changes

- Chad



Snipe -> RE: Windows 2003 Server + Frontpage 2002 (6/17/2003 1:31:39)

Don' t feel lonesome,

My Web host also upgraded to 2003 ILLS-6. Same thing happened to me. None of my FrontPage database pages worked. Others had problems with ASP as you say. They finally got the ASP thing fixed with a Microsoft patch. They gave up on my FrontPage DBR and moved all my sites back to Windows 2000 servers. I last heard from them yesterday that Microsoft was coming out soon with a " Fixit" that should solve the problems. They have meanwhile stopped " Upgrading" their servers. I posed the same question you asked on several forums including this one and was told by several Guru' s that Windows 2003 works fine right out of the box. Tain' t so McGee.

Respectfully,



bobby -> RE: Windows 2003 Server + Frontpage 2002 (6/17/2003 10:07:18)

quote:

told by several Guru' s that Windows 2003 works fine right out of the box

That would have been a first...

[:D]



Gil -> RE: Windows 2003 Server + Frontpage 2002 (6/17/2003 10:14:17)

quote:

was told by several Guru' s that Windows 2003 works fine right out of the box.



Guru' s huh? [:D]



Cookie -> RE: Windows 2003 Server + Frontpage 2002 (6/17/2003 12:00:34)

Hi Chad,

I had exactly the same problem with the parent path include files. They originally told me to use SSI, but I explained that I would have to go through all applications, put them on the " Spooky" diet and amend. So they turned this feature off, and all my sites are now back working a treat!!

Apparently it is a new patch for IIS, and can be quite easily turned off.

Hope this helps!



clum1 -> RE: Windows 2003 Server + Frontpage 2002 (6/17/2003 12:46:52)

quote:

I' ve been microsofted


How was your first time? I' ve felt the cold hands of MS on my neck many a time now...

Anyway; who actually upgrades servers to a new MS OS within a year of release?!?!? We' re still running NT4 here (not as a web-host) and may move to Win 2K if we don' t move entirely to Linux.

Oh, and Win 2003 no longer uses CDONTs; it' s CDOSYS now as I have found out from my host!

clum1



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/18/2003 13:37:17)

Hi, thank you for all the replies. I sent the technical reference from Microsoft' s website to my webhost and they have disabled some feature or provided a workaround and my DRW pages now work.

As far as CDOSYS? I know that Windows 2003 will verify the send-from address...should I be rewriting my CDONTS code?

Thanks,
Chad



clum1 -> RE: Windows 2003 Server + Frontpage 2002 (6/18/2003 16:23:43)

Here' s a link to the support forum where I found this out - I' m actually just about to rewrite my CDONTs code at the momemt - I' ll post back...



clum1 -> RE: Windows 2003 Server + Frontpage 2002 (6/18/2003 16:57:30)

the link to the Sitepoint article in the post above is INVALUABLE! Follow this for CDOSYS e-mail info: http://www.sitepoint.com/avantgo/article.php?aid=1139&pid=21



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/23/2003 13:29:19)

Thank you Clum, I am updating my code right now. Excellent link! [;)]

- Chad



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/23/2003 13:32:22)

Okay, I only have one issue left with regards to the change in platforms... I have 3 DRW pages that are identical except for the table they draw records from... they have the same search form, same variables, etc. They all worked fine but oddly, one of them does not work now, while the other two function perfectly.

The one that doesn' t work is returning no records found for unique ID searches... I have checked the database and it is fine, and has about 15 records, which ID' s 1-15.

I will post the code in a little bit, but I have printed out its html vs the html of one of the other pages that does work and I see no difference. I refreshed all the DRW content and it still does not work.

- Chad



Valaire -> RE: Windows 2003 Server + Frontpage 2002 (6/23/2003 13:56:07)

I tried making a completely new DRW page to connect to this table in my database, and it still will not query it correctly. The database looks fine in access yet I receive no results from this query which I use on the other 2 tables: 

fp_sQry=" SELECT * FROM External WHERE (ID =  ::ID:: OR Name =  ' ::Name::'  OR Company =  ' ::Company::'  OR State =  ' ::State::' )" 
fp_sDefault=" ID=NULL&Name=NULL&Company=NULL&State=NULL"


- Chad



hzarabet -> RE: Windows 2003 Server + Frontpage 2002 (6/26/2003 20:21:05)

This thread has scared the ^%&%*)_ out of me. My WHOLE site is FP databases and CDONTS. I just called my host. Thankfully they are not moving anyone/upgrading anything.

He did say the Windows 2003 does not read FP2000 extensions! Only FP 2002!



Parcom -> RE: Windows 2003 Server + Frontpage 2002 (8/5/2003 16:40:24)

Just wanted to add a hosting perspective which may or may not help much. [:D]

We called Microsoft and got official word that the basic WAIS search function is not supported on Windows 2003 using Frontpage 2002. Index server is the only search feature that is supported now. We will be posting the official documents from Microsoft on our web site which is at least one whitepaper on this search problem. In short, " not supported" [;)]

Change of subject...

CDOSYS taking over for CDONTS was an interesting one that we found the day Windows 2003 came out as a beta for us to test. CDONTS worked on one of the betas, then it was pulled out. The change over to CDOSYS was also documented on the Microsoft site - although, probably tough to find.

Hope some of this helped?! This sort of thing always happens from version to version.

Best regards,

Dave
Parcom Internet Services Inc.
http://www.parcom.net



Shirley -> RE: Windows 2003 Server + Frontpage 2002 (8/24/2003 22:28:22)

I have an easy fix for your problem if you haven't found one yet./

I just drug the files from _fpclass/ into the folder where the pages are.
It updated all of the links and it works fine. I then copied them and pasted them back into the _fpclass folder just in case.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.125