Publishing Error - While Accessing FrontPage web files

[Mardon]

One of the websites that I maintain has developed an error that is
preventing me from using the FrontPage "Publish" command to create a local
mirror of the server-based website. I'm using MS FrontPage2000 v4.0.2.6625
My standard practice has always been to 'work live' on the server copy of my
web pages and then publish the changed pages back to my local PC. This has
always worked fine until last week, when it began to fail for my justus.ca
domain. I can still logon to my justus web and/or any of its subwebs and
work with them 'live' on the server using FrontPage2000 as my client.
However, when I try to publish the server-based justus.ca web, or any of its
subwebs, I get an error. The behavior is such that it begins publishing and
transfers several files. Then it displays the "Processing Web Updates"
dialogue way too soon (that is, before it has transferred of the all the
files that need to be transferred). Neither does the "Processing web
updates" dialogue window list the filename and path of the target file as it
is supposed to do. After about 20 seconds I get an error message that reads,
"An error occurred accessing your FrontPage web files. Authors - if
authoring against a web server, please contact the webmaster for this
server's site. Webmaster's - please see the server's system log for more
details." The isp that hosts my site can not see anything wrong from their
logs and I have not changed anything on my client PC since the time that I
last published the justus web successfully. I also can still successfully
publish another web that I maintain, theelectricutilitylist.com, however,
that web is hosted on a different server from the justus web. I have placed
some screen captures of a successful publish of theelectricutilitylist.com
web and the unsuccessful publish attempt for justus.ca at
http://www.justus.ca/error.jpg I'd appreciate if someone knowledgably would
have a look and give me an opinion of what has gone wrong and how to fix it.
Incidentally, I tired publishing to several different local hard drives and
that did not overcome the problem. Any ideas?

 

[Thomas A. Rowe]

Try publishing to a different location on your HD.

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

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

 

[Mardon]

I've already tried multiple locations and multiple hard drives. I guess you
missed the fact that I said that at the end of my original post. Thanks
anyway. Other ideas?

 

[Thomas A. Rowe]

Yes, I did overlook that bit of info.

Are you letting FP create the folder at the location during publishing or have you created the
folder beforehand?

Can you provide example of the URL / path you are entering for publishing to?

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

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

 

[Mardon]

I've tried both publishing to an existing folder and letting FP create a new
folder. Until I started getting this error message last week, I routinely
updated the website mirror that resides on my HD by publishing the changed
files on the server-based web to the mirrored folder on the HD. That no
longer works. I then tried publishing all files, not just the changed ones.
That does not work. I then tried letting FP create a new folder and publish
everything. That does not work either. The URL of the web that I am trying
to publish from is: justus.ca. It is the URL that I mentioned in my original
email, and the one that contains the screen captures, i.e.
http://www.justus.ca/error.jpg One of the local pathnames that I tried
using can be easily seen in the screen captures. I've also tried may others,
including locations other HDs, and they all fail with the same error.

Yes, I did overlook that bit of info.

Are you letting FP create the folder at the location during publishing or have you created the
folder beforehand?

Can you provide example of the URL / path you are entering for publishing

to?

 

[Thomas A. Rowe]

Mardon,

I was looking for the URL that you use to publish from your live site back to your local machine,
but I see that in your link to error.jpg.

Try publishing to:

M:\Data\JustUs

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

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

 

[Mardon]

It did not work. I tried publishing to M:\Data\JustUs and it behaved
exactly as it has since the failure started. It transferred a few files and
then quit with the same error message as described in my original post.
Frustrating.

 

[Thomas A. Rowe]

Have you install any new software, specify Anti-Virus or Firewall or MS Updates just prior to this
problem?

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

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

 

[Mardon]

No. As I said in my original post. "...I have not changed anything on my
client PC since the time that I
last published the justus web successfully."

Personally, I suspect it may be a server-side problem but I'm not technical
enough to know it that is true and the isp hasn't yet identified any
problem. Hopefully they will. They're still working on it. I just thought
I'd try posting here in case someone had encountered the problem before and
could point me to the solution. Thanks for trying.

 

[Stefan B Rusynko]

Try using a top level folder M:\wwwTheElectricUtilityList\
Or an existing empty FP disc based web at that location
(create the above folder and use File Open Web and browse to it for FP to convert it to a web)
- make sure you are publishing w/ the All pages option

PS
Since you have had several publish failures
1) In Windows Explorer Find and delete all FP Temp Files
Usually in C:\WINDOWS\Temp and %USERPROFILE%\Local Settings\Temp
2) In Windows Explorer Find and delete all hidden *.web files
Usually in %USERPROFILE%\Application Data\Microsoft\Web Server Extensions\Cache
3) Run a Repair on IE
(see http://support.microsoft.com/default.aspx?scid=318378 )
4) Install all Service Packs for your OS, IE, MS Office and your Video card
(Windows Update and Office Update sites, plus your video card supplier site)
5) Open FP and Disable or Uninstall any FP Addins,
6) Open your online FP Web/Site and run a Tools Recalculate Hyperlinks





| No. As I said in my original post. "...I have not changed anything on my
| client PC since the time that I
| last published the justus web successfully."
|
| Personally, I suspect it may be a server-side problem but I'm not technical
| enough to know it that is true and the isp hasn't yet identified any
| problem. Hopefully they will. They're still working on it. I just thought
| I'd try posting here in case someone had encountered the problem before and
| could point me to the solution. Thanks for trying.
|
| |
| > Have you install any new software, specify Anti-Virus or Firewall or MS
| Updates just prior to this
| > problem?
|
|
| <*snip*>
|
| > ...I have not changed anything on my client PC since the time that I
| > last published the justus web successfully.
|
|

 

[Mardon]

I tried most of your suggestions to no avail. Then I decieded that I would
try doing the publish using an entirely different client PC. It turns out
that I get exactly the same error and the publish attempt failed in exactly
the same way as discussed in the previous posts in this thread. I guess this
'proves' that it must be a server side problem. Would you agree? If so, I
suppose it is still possible that it is either a web content issue or a
server configuration issue. Comments? Thanks for the help so far.

Try using a top level folder M:\wwwTheElectricUtilityList\
Or an existing empty FP disc based web at that location
(create the above folder and use File Open Web
and browse to it for FP to convert it to a web)
- make sure you are publishing w/ the All pages option

PS
Since you have had several publish failures

<*snip remainder*>

 

[Stefan B Rusynko]

Does you online site have any large files (>1MB) or files w/ "odd' extensions?




| I tried most of your suggestions to no avail. Then I decieded that I would
| try doing the publish using an entirely different client PC. It turns out
| that I get exactly the same error and the publish attempt failed in exactly
| the same way as discussed in the previous posts in this thread. I guess this
| 'proves' that it must be a server side problem. Would you agree? If so, I
| suppose it is still possible that it is either a web content issue or a
| server configuration issue. Comments? Thanks for the help so far.
|
| > Try using a top level folder M:\wwwTheElectricUtilityList\
| > Or an existing empty FP disc based web at that location
| > (create the above folder and use File Open Web
| > and browse to it for FP to convert it to a web)
| > - make sure you are publishing w/ the All pages option
| >
| > PS
| > Since you have had several publish failures
|
| <*snip remainder*>
|
|

 

[Mardon]

My total website includes a number of subwebs. Some of these subwebs
contain no files over 1MB and no 'unusual' filename extensions. Even if I
try to publish only one of these 'easy' subwebs, rather than the entire
site, I still get the same error as previously described. (i.e.
http://www.justus.ca/error.jpg )

Looking at the entire web, there are 6 files over 1MB but none over 3MB.
The following filename extensions are in use: zip, mdb, wmv, pdf, ico,
class, asp, asa, gif, png, cer, jpg, txt, doc and, of course, htm.

Does you online site have any large files (>1MB) or files w/ "odd'

extensions?

 

[Stefan B Rusynko]

My best guess is the last error in your image indicates a filesize or file type error
- your files over 1 MB are a problem due to a recent IE or security patch
(move them all to a folder and convert to a subweb - do not publish that subweb, use FTP)
- also believe mdbs usually can not be published by FP




| My total website includes a number of subwebs. Some of these subwebs
| contain no files over 1MB and no 'unusual' filename extensions. Even if I
| try to publish only one of these 'easy' subwebs, rather than the entire
| site, I still get the same error as previously described. (i.e.
| http://www.justus.ca/error.jpg )
|
| Looking at the entire web, there are 6 files over 1MB but none over 3MB.
| The following filename extensions are in use: zip, mdb, wmv, pdf, ico,
| class, asp, asa, gif, png, cer, jpg, txt, doc and, of course, htm.
|
|
|
| > Does you online site have any large files (>1MB) or files w/ "odd'
| extensions?
|
|

 

[Mardon]

Thank you! It was the files over 1MB that were causing the problem. In a
previous post I said that I had unsuccessfully tried publishing a web with
no files over 1MB but that was incorrect. I had overlooked one. I double
checked everything again and found a large file that I hadn't realized was
there. Anyway, I wound up moving all the files over 1MB to their own subweb
off the top level. The top-level web and all the other subwebs now contain
no files over 1MB. Everything now publishes fine, except the single
subweb that contains the large files. As you suggested, I'm now using FTP
for that subweb only. The database files (mdb) publish fine. No problem
there.



I really didn't think that I had installed any patches on my PC since the
last successful publish, but obviously I must have. What I don't understand
is how MS can issue a patch for their software that will so mess up another
piece of their software and then not even have anything in their
knowledgebase about it? I've scoured their KB for a solution to this
problem and came up empty. I sure appreciate your help. I never would have
solved this on my own. Since these large files had always published fine in
the past, it would have never occurred to me that they were the source of
the problem. Or perhaps I should say that the large files in combination
with a problematic MS software was the problem. Is this an issue for the
newest version of FrontPage also or only for my old FrontPage2000? Is it
likely that MS will produce another patch that will correct this problem?
I'd really prefer to have the files where they 'belong' and be able to
publish the entire web without the need for a workaround.



In any event, many thanks again Stefan!! Mardon

 

[Stefan B Rusynko]

The patch is believed to be a Windows OS or IE security patch affecting many users and versions of FP
- the FP dev team is aware of it and trying to track down which one it was so they hopefully find a work around

Glad you are back in business



| Thank you! It was the files over 1MB that were causing the problem. In a
| previous post I said that I had unsuccessfully tried publishing a web with
| no files over 1MB but that was incorrect. I had overlooked one. I double
| checked everything again and found a large file that I hadn't realized was
| there. Anyway, I wound up moving all the files over 1MB to their own subweb
| off the top level. The top-level web and all the other subwebs now contain
| no files over 1MB. Everything now publishes fine, except the single
| subweb that contains the large files. As you suggested, I'm now using FTP
| for that subweb only. The database files (mdb) publish fine. No problem
| there.
|
|
|
| I really didn't think that I had installed any patches on my PC since the
| last successful publish, but obviously I must have. What I don't understand
| is how MS can issue a patch for their software that will so mess up another
| piece of their software and then not even have anything in their
| knowledgebase about it? I've scoured their KB for a solution to this
| problem and came up empty. I sure appreciate your help. I never would have
| solved this on my own. Since these large files had always published fine in
| the past, it would have never occurred to me that they were the source of
| the problem. Or perhaps I should say that the large files in combination
| with a problematic MS software was the problem. Is this an issue for the
| newest version of FrontPage also or only for my old FrontPage2000? Is it
| likely that MS will produce another patch that will correct this problem?
| I'd really prefer to have the files where they 'belong' and be able to
| publish the entire web without the need for a workaround.
|
|
|
| In any event, many thanks again Stefan!! Mardon
|
|
|
|
| > My best guess is the last error in your image indicates a filesize or file
| type error
| > - your files over 1 MB are a problem due to a recent IE or security patch
| > (move them all to a folder and convert to a subweb - do not publish that
| subweb, use FTP)
| > - also believe mdbs usually can not be published by FP
|
|