I keep getting hung on one particular file during down publishing (server to H/D). It is:

W3SVC162/ex0102.log

It usually takes only a few seconds to publish my updates, but now, after about 30 mins. I get the "Server Error: Client Closed Connection" error.

This sounds like a "stats" file to me, however it is not in the stats folder (it is a folder directly on the root, the W3SVC162, that is). I have contacted our host, webburner for assistance, but if they are like most web hosts, they have no clue of FP2000.

Any Suggestions? We are stuck as of right now.

(ps. This is an NT Server)

Thanks,

Dereck Willis
VP and Webmaster POTCE, LLC
POTCE.com

I just compared my H/D's FP files with the Server's FP files, and the looked the same. So, I took the chance to publish to the web, and it seems to have worked fine. I guess that particular file is not that important.

But I thought it was important for FP to complete "Processing web updates"? Oh well, any feedback would be appreciated.

--------

Dereck Willis
VP and Webmaster POTCE, LLC
POTCE.com

Webburner actually responded to my email within 2 hours and here's what they suggested:

"The problem is that the ex0103.log is always locked from any interference
since it is always in use by the web server creating logs. This .log file is
only used for the month of March and can be downloaded after March 2001. The
only way around this is to have us to stop logging in IIS. Just go to the
NT request control panel in the Members Area to request this. Then once you
publish it to your HD then go back and request to start logging. You may
also be able to exclude this log file from being downloaded."

Just wanted others to know, in case you have similar problems. Thanks again,

Dereck Willis
VP POTCE, LLC
POTCE.com