The server unexpectedly closed the connection (Full Version)

All Forums >> [Community] >> OutFront Discoveries



Message

ThomasCholipski -> The server unexpectedly closed the connection (11/2/2003 20:32:38)

For a long period of time I have been plagued by the "The server unexpectedly closed the connection" message when I try to publish a large web site with FP 2002.

I found the following fix helps to alleviate that problem. At least for those who use DSL.

Open Frontpage.
Click on Tools, then on Options.
Click Proxy Settings and Select the Advanced Tag.
Make sure "Use Passive FTP(for firewall and DSL modem compatibility) is
checked under Browsing.
Click OK.


Hope this helps some.

Tom



GolfMad -> RE: The server unexpectedly closed the connection (11/6/2003 11:16:29)

I used to get this all the time for two separate 100 page + sites, when updating. This then screwed up the shared borders and navigation. I had to remove the borders and navigation completely upload then add them to disk web again and upload. With my Microsoft certified hosts help, we went through clean installing the site on the server again, but during upload the 'server unexpectedly...' error popped up and we were never able to upload in one go; always resorting to me using the fix above.
This was worse when we were on 56K modem for the errors. Since we have been on ASDL, the errors occur less, the ADSL connection seems to wait longer for the web server to 'processing updates..' at the very end of the upload than compared to the old 56K modem. I know the Tech Manager at our hosts felt modem upload on large sites had something to do with it.
We use Win XP Pro and FP2002 all fully patched
I have enabled your fix and see what happens when next working on either of these webs.
Regards
Phil



tinaalice -> RE: The server unexpectedly closed the connection (11/6/2003 19:24:30)

Tip .. Always recalculate hyperlinks under Tools menu before publishing after editing.

This does help somewhat as frontpage does not have to take time looking for files that have been deleted etc, it just makes for a quicker publish.

Tina



SerenityNet -> RE: The server unexpectedly closed the connection (11/7/2003 21:02:56)

I will definitely try your suggestion.

But what I did to get around the problem was open localhost in one instance of FP and then open the web on a separate instance of FP (the two webs open in two windows). I then simply dragged-and-dropped a few folders at a time from the localhost to the web.



gb -> RE: The server unexpectedly closed the connection (6/25/2004 2:06:17)

I figured out what, at least for my web site, was causing the problem. Take a look at the Microsoft website http://support.microsoft.com/default.aspx?scid=kb;en-us;Q261139&ID=Q261139

Essentially I had installed a new proxy server (a couple of days ago) and this was introducing a sufficient additional delay so that neither the FrontPage client and (in my case the Cox.net) web server were not connecting correctly. I was using GhostSurf a try, and by turning it off, everything cleared up.

Hope this helps someone else as this problem is the pits........



jaybee -> RE: The server unexpectedly closed the connection (6/26/2004 7:04:25)

I get this regularly when uploading with FTP. I've tried all the Proxy settings to no avail. I'm now resigned to doing a few files at a time and then logging out and back in.

I've found it does help if I create new folders direct on the host and then put the files in rather than letting FTP create the folders for me.



jlojko -> RE: The server unexpectedly closed the connection (9/28/2004 14:37:58)

I recently started getting this message after upgrading to WinXP SP2. After reading this thread, the combination of all this firewall talk and the changes that SP2 introduced, pointed me to the new Windows Firewall.

I just went to the new windows security center and turned off the firewall. The problem went away. So now I just turn off the firewall before publishing through FrontPage and back on, after.

I felt compelled to post this simple resolution because it was such a frustrating problem.



Spooky -> RE: The server unexpectedly closed the connection (9/28/2004 16:06:28)

I would seriously look at getting a better firewall such as ZoneAlarm - its not a great idea to turn off the XP firewall while publishing.
Install and use ZA and then leave the XP firewall off.



Kurt Geer -> RE: The server unexpectedly closed the connection (10/16/2004 13:32:12)

I have read thru this post and tried some of the suggestions but to no avail. Here is what happens with FP2000

"The server unexpectdley closed the connection?
(Thursday Oct 14th)
I have been having this problem for a while and am getting no help from the hosting company, (HostBlade) so I don't know if it is them or me. I traded a domain name for a year of hosting and am finding out how wonderful they really are in customer support[;)]

(This was Friday the Oct15th)
I talked with the owner to see if he could reinstate or refesh the Front page extentions on his server for my domain and he said that he does not have FP extenstions on his server, which makes me wonder how I ever published the website in the first place while using FP. (I am not a techie, but not totally brain dead either) He was no help and offered no suggestions or solutions.
So I
Downloaded a copy of WS_FTP Pro from IPSwitch (30 day Trial) and got the same god blessed message. I am still at a loss and thinking it is them and not myself.

For another site I had I could create the website pages in FP and upload or ftp using WS_FTP so I know it can work this way.

Any suggestions before I change hosting companies?







nimrie -> RE: The server unexpectedly closed the connection (10/18/2004 15:25:37)

I had this problem. My configuration Windows XP, FP 2002.

For some time I had been experiencing "Server unexpectedly terminated connection" errors from Frontpage 2002 when try to publish .asp pages to my web host (Apache with FP Server Extentions).

In Norton Internet Security, by carefully adding Intrusion signatures to the excluded list I found the offending item:

HTTP_MS_SQL_XML_CrossS - I cant see the rest of it.

There was nothing in the Symantec knowledge base - but it sure worked.



cfilut -> RE: The server unexpectedly closed the connection (12/8/2004 16:48:07)

I have had this problem before and this is what was happening to me.

Some of my asp pages would not publish at all but all the htm pages would. In FP 2003, when publishing http, select under view, "files to publish", you will see the pages that have not syncronized with your website. Click on each one seperatley to selectivly publish it. By doing this seperatley rather than publishing all, you will weed out the page thats giving you trouble. If you dont have FP2003, skip to paragraph below.

Once every page is published, except the ones giving you trouble, click on publish your site and change the http://yourdomain.com to publish to ftp://yourdomain.com. Publishing ftp through FP has worked on these stubborn files for me. I have not run accross an instance where publishing ftp would mess up your FP extensions, but I guess it could happen, just not with my webhosts.

Also, are you using a wireless router? I was (laptop on couch in another room), and it turns out this is what was timing out and giving me the connection problems(even though wireless strength was great). I went around and around with my webhosts about the server timing out or closed connection unexpectantly, and it was on my end the entire time.

If you are using wireless, try changing channel in set up, in Lynksys wireless, there are 11 channels(change them up a little) see what works better, do you have 2.8ghz phones? this will affect also.

Im not on this forum much, but this problem erked me for months....I hope this helps someone. It seems to have cleared up my issues.




jaybee -> RE: The server unexpectedly closed the connection (12/9/2004 5:13:31)

I've discovered one fix to this issue.

If you're using an ftp client (not FP publish) make sure you've shut FP down completely before transferring then it's OK.

IF FP is still open then it's unreliable. If the page you're publishing is still open almost guaranteed to cause the error.



GetCalhoun -> RE: The server unexpectedly closed the connection (7/11/2005 18:39:08)

OutFront does it again!!! I was going bonkers with this problem. My friend's free server went belly up so I am faced with finding low cost homes for a whole pack of orphan websites. Unfortunately, the new place doesn't have FP extensions. I messed around all weekend wondering what was wrong with theirserver. I turned off the firewall and the thing uploaded like a bat from the bad place.
Super!!! Extraordinary! THANKS!



kddailey -> RE: The server unexpectedly closed the connection (10/15/2005 11:51:34)

I also had this problem on a large site using FP 2003, and tried all the above solutions to no avail. Even worse, I would get the problem when working directly on the remote site. I could transfer one page at a time using the arrows, but couldn't publish.

What finally worked: used the repair FP utility on the FP install disk, and also uninstalled and reinstalled the server extensions on my local machine - not the remote machine. Since I did these simultaneously, I'm not sure which fixed the problem.

Hope this helps someone with this terrible problem.

BTW - as a stopgap until I finally solved the problem, I marked all pages on the site as "do not publish" with a right click, then unmarked them about five at a time, published, and repeated. This got the two webs re-synced. If you only change a few pages at a time, this can get you caught up. Then you can publish just a few files at a time.



Uncle Meat -> RE: The server unexpectedly closed the connection (10/29/2005 14:13:55)

I've tried all the suggestions in this thread, at least all that apply to me and I'm still having this problem. I'm running XP Pro SP2 and FP 2002. Everything is patched up with the latest & greatest from Microsoft. At this rate it will take me a week to get all my files updated on the server.... My website has over 20,000 files and most of them have changes.[X(]

U.M.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.046875