Server error: The page ' '.htm has been modified by PHX3\'hostname

[Raj Kumar]

I've been receiving this error message every time I try to publish files to
the server:

Server error: The page ' '.htm has been modified by PHX3\'hostname' on
'today's date'

I first had this error with a web page that had the same name as a folder. I
moved the page and everything was published.

However, the next time I made a minor change and clicked 'Publish Files', I
got that error again but with just about every page, not just one that had
been changed. I get that error every time now, I can't update anything.

Anyone have any ideas?

Thank you.

 

[Stefan B Rusynko]

Try downloading, installing, and running the FPCleaner
- see http://www.95isalive.com/fixes/fpclean.htm
Use it to Clear the hidden Cache files (and Temp files)
Then open FP, run a Tool Recalculate Hyperlinks
Then try a Publish ALL, followed by a Publish Changed only
- set in Remote site properties

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


I've been receiving this error message every time I try to publish files to
the server:

Server error: The page ' '.htm has been modified by PHX3\'hostname' on
'today's date'

I first had this error with a web page that had the same name as a folder. I
moved the page and everything was published.

However, the next time I made a minor change and clicked 'Publish Files', I
got that error again but with just about every page, not just one that had
been changed. I get that error every time now, I can't update anything.

Anyone have any ideas?

Thank you.

 

[Raj Kumar]

Thank you so much! I don't think we would have been able to update the site
this week without this post.

The only thing is that 'Publish All' meant waiting 11 hours to complete (we
have a lot of audio on our site). I stopped that part of the way and did a
'Publish Changed Only' and it worked fine.

Thank you!

Maybe we should upgrade to Expression Web.

I think we had this problem because we were using the same file name under
many different folders.