Hello Every one, Hope you people can help me out.

One of my clients is using Front Page to publish his site on the server. I have increased the Server Time out in the httpd.conf from 300 sec to 1500 sec. He says it has helped in to some extent, but he still has the problem.

According to his email , This is what he has to say
____________________________________________________

"Tried uploading whole site again and still have problem - although it got furter than usual. Still cannot open web from host unless i have first opened it from my hdd and published to host, and that copy of frontpage is still running."

____________________________________________________

Can any one tell me as to ,How do i tune my Htttp so that i can do away with this Front Page Time out Error ?

Regards/-

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q205601&

We secifically recommend to our customers the part about: "Create the web remotely, on your staging server, in order to avoid having to transfer the web."

Thanks Bitserve,

I have given the link to my client, and will revert back here after i hear from him.

Regards/-

hi Bitserve
my client has replied back with the comments , i m pasting it below

++++++++++++++++++++++++++++++++++++++++++++++

This is not quit the problem - i will insert comments below
SYMPTOMS
When you use the Publish Web command to copy an existing web to a remote Web site, you may receive one of the following error messages:

An unexpected Web Extender error occurred on the server. Authors- please contact the Webmaster for this server's site. WebMasters- please see the server's logs for more details.
-or-

Poorly formed http response.
THE MESSAGE I GET IS EITHER "Could not find a web server at 'xxxxx.biz' on port 80 " after a very long time or just nothing ever happens and front page will not respond to even close

WORKAROUND
To work around the limitations of the time-out period, use any of the following methods:
Use a faster modem. I AM USING 512/128 ADSL -
A 28.8 (28,800 bits per second [bps]) modem is twice as fast as a 14.4 modem.
Use sub webs instead of a root web to avoid creating webs whose transfer speed exceeds the time-out period.
WE ARE JUST TALKING ABOUT VERY SMALL SITES THAT STILL HAVE THE PROBLEM

Create the web remotely, on your staging server, in order to avoid having to transfer the web.
THIS DOEST WORK EITHER AS PREVIOUSLY MENTIONED.
Use the FrontPage Publishing Wizard to transfer your web, and then recalculate the links on the web when it reaches the server.

The FrontPage Publishing Wizard initiates an FTP session to your server and automates the transfer of FrontPage webs using FTP. FTP is not subject to the same time-out limitations as HTTP and can often move data more reliably. In addition, the Publishing Wizard allows you to transfer only the files that were changed since the last post, which results in less data being transferred. The FrontPage Publishing Wizard can be set to transfer all files or some files in the Web.
I TRIED THIS BUT IS VERY DIFFICULT- ONCE I USE FTP WITH A SITE IT IS VERY HARD TO GET IT TO USE HTTP AGAIN, AND TO OPEN SITE FROM HOST TO RECALCULATE LINKS FP HAS TO BE USING HTTP.

CONCLUSION - THIS IS NOT THE PROBLEM, AND NOT THE SOLUTION.
+++++++++++++++++++++++++++++++++++++++++++++

Can u tell me now what to do ?

Or Any one ?

Regards/-

It would be best to completely reset Frontpage and have the person upload the entire web site (not just changes).

I have a similar problem with Hostway in that Frontpage never finishes a web transfer but I have a mirror site at Dellhost that has never had the problem.

Unless you can find something on your end, expect the client to complain every time they want to upload web site changes.

Yes markcw

I tried to edit his site on the Fly from Front Page 2000 and i did it with ease, and i did not have a copy of his website on my HDD.
and no one else on my server except this client has this problem,

by resetting Frontpage you mean reinstalling it on my server or some thing else ?

Please advice

Regards/-

Altho this is not a solution, I used to see this a lot when the site was very big. Front Page can't handle large sites I forget the size limitation( you are, after all, pushing data thru port 80) If the site is large, have the client cut it down and try to republish... in addition, reseting the Front page extensions, never hurts (unless the customer is using custom extensions or themes).

I meant to reset Frontpage via WHM or cpanel for their website only and not a complete reinstall because then all your clients will have to republish.

I would also allow a longer timeout. If the web publish is on a modem and not cable it will be slow!


hmmm..

Actually the website I am having the problems with is close to 50 mb of web pages. so it is an issue with large web sites - i use frontpage with many other websites with zero issues on unix and windows.

It would be difficult to cut down the web pages in my case since, I would have to use a database to generate the pages and drag the server resources down.

Yet dellhost does not have this problem when I publish? However I believe they do have a very long timeout like 30 minutes or longer.

I can't stand vague answers... herte's what I got from
groups.google.com with a search for 'frontpage timeout large pages'

This is Microsoft article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q201803


Oh and to all those Hostway customers having the same problems as me with the timeout... A similar Hostway message from groups.google.com with the answer = change the timeout value.

Hostway told the client to break up the web into sub-webs... that would actually be worse!

hello again

The client's website is approx 80 mb, i am about to reset the FP extensions, lets see what happens, will keep posting !!!

Regards/-

I guess I don't understand what the user is trying to say. I was assuming before that I knew what he meant, but I was wrong.

I'd ask him for step by step instructions that you can use to duplicate the problem.