I'm %$&%&^& tired of seeing "server unexpectedly closed the connection"

[Dave Satchell]

I have a fresh load of XP on my laptop with a fresh load of Office 2003
with all of the patches and updates installed.

When trying to publish a site with FP 2003 I keep getting the error
"server unexpectedly closed the connection" when I try to:

1. publish more than four files at a time
or
2. try to publish specific individual files

is there a way to get more detailed results as to what the failure is?
If not then is MS ever going to pull their head out and provide that
capability. I mean, come on, I see people having this problem all the
time. Would a little more detailed error message kill them?

Does anyone else have any suggestions?

Thanx, Dave.

 

[Thomas A. Rowe]

Have you contacted your host?

Are you publishing any one file that is 1 MB or larger?

If the server closes the connection, how is FP suppose to know the reason? In order for the server
to send the details about closing the connection, it would have to know that it was going to close
the connection, before it close the connection.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Jim Buyens]

Please try the suggestions in these articles:

Connection Times Out During Publish
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=1

FrontPage Publish Command Fails
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=24

If one of those doesn't resolve the problem, please post
again and mention:

o What type of Internet connection you have (LAN,
cable modem, DSL, satellite, modem...)
o The number and total size of the files in the
Web site.
o The number and total size of the files you're
trying to publish.
o The protocol (HTTP, FTP, ...)
o Whether or not you have Windows XP SP2 installed.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Dave Satchell]

Yes I am publishing a couple of PDF files that are larger than 1 meg.

It just seems that people have a lot of problems with publishing and it
would be nice if there was a setting in the Frontpage extensions on the
server that would cause a debug file to be dumped in the directory that
the publishing failed on.

Dave.

 

[Thomas A. Rowe]

Mark those files not to be published, then see if you can publish without any problems. If you can
then those files are the problem, you will need to use a FTP application just to upload those files,
then you will need to open the web in FP on the remote server and run Tools | Recalculate
Hyperlinks.

FP writes the last error message generated in the Windows Temp folder in a file called: we...txt
(Sorry, I don't have one currently to give the exact name), but it should be in the root of the temp
folder.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Andrew Murray]

try this knowledgebase article:

http://search.microsoft.com/search/...&qu=server+unexpectedly+closed+the+connection