G
Guest
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.
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.