Error Message at end of publishing

After I publish a site from our staging to production environments, FrontPage hangs for a 'long' time 'processing web updates.'  After about half an hour, I finally get a response stating that FrontPage 'Could Not Find a Web Server at (xxxxx) on port 80 . . .'

Now, all of the files that needed to be pubished have been published, and the only rotten thing about this is that the next time I go to publish, FrontPage is confused about previously published files (it's not quite sure if the file that's being pushed is really the file that has been pushed from that location).  So, this is far from a critical error - but it's still annoying.  Anybody out there deal with this?

I'm publishing from Server 2003 (with Server Extensions 2002) to an identical box.
LVL 1
batzerjlAsked:
Who is Participating?
 
coreybryantCommented:
Try to clear out your FP temporary files:
1) Delete all FrontPage and Windows temp files
2) In Windows Explorer Find and delete all hidden *.web files
3)  In Windows Explorer Find and delete the file CMDUI.PRF (deleting this file will remove any customizations you have made with your toolbar..and it will be rebuilt using the default the next time you open FrontPage)
4) Disable or Uninstall any FP Addins (especially any recently added ones)

-Corey
0
 
coreybryantCommented:
I get this every so often myself.  Publishing to Windows 2003 / FP extensions 2002.  It is annoying because FP has not had a chance to update.  Usually I have noticed when I re-boot the server, things seem fine.   Windows is a memory hog but I notice when I do publish via FP, it does not consumer anything.  

-Corey
0
 
batzerjlAuthor Commented:
See, I've tried that, and I still get the same behavior.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.