Re: Difficulty Publishing Large WEB site
From: Thomas A. Rowe (tarowe_at_mvps.org)
Date: 03/09/05
- Next message: Trevor L.: "Re: Microsoft MVPs"
- Previous message: Bob Lehmann: "Re: Difficulty Publishing Large WEB site"
- In reply to: Thomas A. Rowe: "Re: Difficulty Publishing Large WEB site"
- Next in thread: P. McWhorter: "Re: Difficulty Publishing Large WEB site"
- Reply: P. McWhorter: "Re: Difficulty Publishing Large WEB site"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 8 Mar 2005 19:29:34 -0500
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) http://www.ycoln-resources.com 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 A. Rowe" <tarowe@mvps.org> wrote in message news:OVhldpDJFHA.1360@TK2MSFTNGP10.phx.gbl... > 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) > http://www.ycoln-resources.com > 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 > > "P. McWhorter" <PMcWhorter@discussions.microsoft.com> wrote in message > news:95D4A316-1203-4A68-8F5D-2B54F52E60A0@microsoft.com... >> 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? >> >> >> "Teri Carnright" wrote: >> >>> 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 >>> :) >>> >>> >>> "P. McWhorter" wrote: >>> >>> > 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. >>> > >>> > >>> > -- >>> > P. McWhorter >>> > > >
- Next message: Trevor L.: "Re: Microsoft MVPs"
- Previous message: Bob Lehmann: "Re: Difficulty Publishing Large WEB site"
- In reply to: Thomas A. Rowe: "Re: Difficulty Publishing Large WEB site"
- Next in thread: P. McWhorter: "Re: Difficulty Publishing Large WEB site"
- Reply: P. McWhorter: "Re: Difficulty Publishing Large WEB site"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
