P
PJx
I didn't mean that kind of attitude problem. You say "but I see
no reason that FrontPage should not work wonderfully for large sites".
Eventually, reality will slap you hard in the face with that attitude.
That's what I meant by an attitude problem, but don't worry about it.
I'm happy with your enthusiasm. I agree with you that FrontPage is a
great package and recommend it myself 'for small to medium sites'.
I meant the event log on the web server. Is it IIS or Apache?
As to working on the server, I was assuming you have something like
PC Anywhere and can get into your Server configuration files. Or
maybe it is sitting beside your desk. That would be nice. In either
case you could work on one folder and then when finished, tell the
server to use that folder as your home directory. Presto - No
publishing required. You save the 20 to 30 hours and the only cost
is that some edits take 20 minutes.
Sound like a bargain to me.
PJ
no reason that FrontPage should not work wonderfully for large sites".
Eventually, reality will slap you hard in the face with that attitude.
That's what I meant by an attitude problem, but don't worry about it.
I'm happy with your enthusiasm. I agree with you that FrontPage is a
great package and recommend it myself 'for small to medium sites'.
I meant the event log on the web server. Is it IIS or Apache?
As to working on the server, I was assuming you have something like
PC Anywhere and can get into your Server configuration files. Or
maybe it is sitting beside your desk. That would be nice. In either
case you could work on one folder and then when finished, tell the
server to use that folder as your home directory. Presto - No
publishing required. You save the 20 to 30 hours and the only cost
is that some edits take 20 minutes.
Sound like a bargain to me.
PJ
PJx - thanks for your comments.
1) I have the frontpage event log turned on, and in the log file it has the
error "Server Unexpectedly Closed Connection".
2) I was mistaken in an earlier post in this thread, the server is a pentium
with 1 gig of memory.
3) I do not have any Norton product on my local computer. Had found that
various Norton products could create publish problems. I have no antivirus
programs installed on the machine. The XP firewall is running, but no
antivirus.
4) I routinely use the find and replace feature on the global web site. It
is not real fast but works OK . . . not sure what you are getting at with the
question.
5) I have tried having two copies of the site on the WEB server, working on
one, and then publishing to the other. The WEB site has gotten to a size
that things are too slow running in this mode. A number of simple functions
cause the system to go away and think for 10 or 15 minutues. Things work
fast when I work on a local copy.
6) I have responded to several posts in this thread, so am not sure
specifically what element of my question/responses represents an attitude
problem on my part . . . sorry if I have offended, that was not my intention.
I understand that other software packages are used for really large sites,
but I see no reason that fronpage should not work wonderfully for large
sites. It is working fine EXCEPT for the publish problem. I know that there
is a solution, because I had a shared hosting service that I could publish
the entire site to without ever getting a "server shut connection" error. It
could take 20-30 hours, and it would just keep going; I never had a sever
connection error with that provider (I would still be with them, except that
my BW demand outgrew their hosting plans). I know they had a windows 2003
operating system but dont know what the secret was to their configuration
that allowed very long publish without problems.
PJx said:You have an interesting problem. I think you probably have the
biggest web site ever that is still publishing with FrontPage. There
are bigger sites but they are being run with much more expensive
software. Software that costs thousands and is difficult to master
and expensive to maintain, but it does have the muscle to do large
sites.
So what does your event log say? You running antivirus software?
You have logging turned on? Have you turned the "do not publish" on
for all the folders you don't want changed? Are you a master at find
and replace? By the way, 3rd party software have super fast find and
replace features that can make changes to your whole computer.
Have you tried making a copy of your site and opening it with
Dreamweaver? You can sometimes pick up a legit copy on Ebay for
about $300. Lots of tutorials online and the program gets great
reviews for those moving UP from FrontPage.
Since you have the server under your control, you need to quit
publishing and work directly on your copy of your live site and then
just move it into production. You can have multiple partitions or
multiple disks.
There are solutions, but it requires an attitude adjustment on your
end.
PJ
PJ,
I think you are probably right. The exact same symptom occurs whether I am
publishing to a "shared" server with 1,000 WEB sites and lots of traffic, or
a dedicated server sitting idle, with no other traffic. I know that lots of
people have had this problem, and have seen lots of potential work arounds
suggested, but have never seen anyone post a server or frontpage
configuration that would keep the server from closing the connection in a
long publish. If you have any ideas, please let me know. It would be nice if
we could solve this once and for all. One of the raps people have with
frontpage is that it wont work for big sites. I think it would work fine, if
we could just get a real solution for the publish problem.
:
I'd be very careful believing the problem is with the celeron. It's
the last place I would look for a solution. The celeron and other
hardware you have is fine and can handle dozens of sites like yours.
What you have is a software problem.
PJ
On Tue, 8 Mar 2005 17:59:03 -0800, P. McWhorter
OK, thanks, I will look into that issue.
:
Ok, I would say your biggest issue is the Celeron processor, your RAM is fine, the mail server
shouldn't be to much of drain, depending on the amount of email being sent/received. The only other
issue would be if Index server is running.
The Celeron Processor is the worse processor to be used for anything other then a general purpose
home pc and is most likely the root cause of your timeouts, above all other issues because of the
size of the cache, which the maximum is 128K L2 for 400 Bus and 256K L2 for 'D' 533 Bus, whereas a
Pentium 4 is a minimum of 512k L2 (400/533 Bus) with a maximum of 1MB (800 Bus).
Suggest you talk to your host regarding a processor upgrade.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
Thomas,
Thank you for your help.
The dedicated server is a 2.4 GHz Celeron with 1024 MB RAM, 80 GB hardrive,
Windows 2003 (dont know if it is WEB or standard edition). The server has
Plesk 7.5 for windows CP, and is running a mail server.
It is the only WEB site running on the server.
Thanks
:
Forgot to ask, since this is a dedicated server the following:
1. What version of Windows 2003 Server (Web Edition, Standard)?
2. What processor is in the server (Celeron, P4 [400, 533 Bus])?
3. How much ram is installed (512, 1GB)?
4. What services are installed and running on the server (index server, mail services, etc.)?
The above item can and do impact the performance of the server.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
You might want to check with the Windows IIS newsgroup as well as look at the FP extensions
performance settings at:
http://www.microsoft.com/resources/documentation/sts/2001/all/proddocs/en-us/admindoc/owsf05.mspx
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
Teri,
Thanks for the posts and suggestions. Turns out the nightly backups are
prohibitively expensive. Also, if I edit live and try to back up to my
machine, same problem occurs . . . the server shuts the connection.
I am only using a 5% of my alocated bandwidth, so I would hope that the
bandwidth would be adequate to let me publish.
If I control the windows 2003 server, is there a server setting that would
prevent the "server shut down connection" error?
:
As a P.S.~
There are certainly settings to prevent the shutdown, BUT, what is available
to you depends on where you are being hosted. Your host will be juggling
total allowable bandwidth between you, other dedicated servers, and
non-dedicated hosting clients, so as not to run the bandwidth out the roof.
Face it - lines can only handle "so much" - and just because your server is
dedicated does not mean your line is dedicated.
My recommendation is to contact the host of the dedicated server and ask the
two questions:
1) (from my last post) - what type backup can he provide if you work
"live", and
2) how can he accommodate you if you require 8-10 straight hours upload time
Teri
:
My frontpage WEB site is about 600 Meg, and about 2500 pages. On a fast DSL
line it takes about 8 hours to publish. I am running frontpage 2003 on a new
computer, and have a dedicated Windows 2003 server running only this WEB site.
Of course, I only "publish changes", but every once in a while the local
copy gets out of sync with the live site, and frontpage insists on publishing
the entire site. The problem is that after about 15 minutes or so into the
publish I get a "server unexpectedly closed the connection" error. If I am
lucky, if I try and publish again, it starts where it left off. If I am not
lucky, it goes all the way back to square one. In any event every 10-30
minutes I get the "Server closed connection" error. In the end, it can take
several days (and nights) to finally get the entire site published.
I have read the previous posts on this topic, and see the primary
suggestions being to either go to a database (which I dont have the skill or
resources to do), or go to subsites, which would not work well for this site.
My question is whether there is any way to actually SOLVE the problem and
allow publishing of large sites. Are there settings or configurations on the
server that would prevent the server from closing the connection?
Before getting the dedicated server, I experimented with 5 or 6 WEB hosting
companies, and there was one that I could publish to, even if the publish
took 20 hours without a "server shut connection" error. Of course they would
not tell me the server configuration that allowed that to work, but I know
that it is possible on a windows 2003 server.
Any help on how to solve this problem would be appreciated.
