Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: open
I currently use Frontpage 2003 & have been using a form of frontpage for the last 5 years. I'm a novice with limited coding knowledge.
Here's what's happening:
When I attempt to publish, I get an error that states:
"Could not find a webserver at 'www.example.com' on port 80. Please check to make sure that the Web server name is valid and your proxy settings are set correctly. If you are sure that everything is correct, the Web server may be temporarily out of service."
I click "ok", and then after a few minutes another & final error box pops up that says:
"Server <root web> is busy, please try again later"
The strange thing is that FP will behave as though it's publishing...it will connect, list files, show changed files it's publishing, delete anything I've deleted...and then just as it shows the text "Processing web updates" the error box comes up.
Basically, it is publishing all of my text, very small changes, and sometimes a small image, but it will not publish my large images. I can right click & force a publish on a large image *sometimes*, but usually I get the same error message.
Other comments ~ when I first began creating my site years ago, I did not understand good basic web design such as putting my pages & images into files, so there are many images and pages in the root web. I also have very large images - something that is integral to my business. I have gone through and deleted as many as I can - perhaps at least half of my original images, but that's all I can delete.
I have spoken multiple times with my ISP and my proxy settings are correct, and port 80 (as well as all the ports) is free & clear.
I have talked with my web hosting company for hours on this - and they believe it is because I have too many images/pages in the root web. They say it is a flaw in the Frontpage product that it cannot handle this. They said I should move all of these images & pages into files. My problem with this (other than the unimaginable amount of work this would involve) is that my customers rely on the links to my pages, so if I were to move them, much would be lost. Just this week I tried moving a few pages I thought would be easy to move, and I received so many emails asking where these pages were. :(
I have spoken with people who know a lot about FP and they say the organization of my files shouldn't make a difference. I think this too - that I should be able to publish regardless of what's in what file. I've googled port 80 error messages, but none of the discussion I've found seems applicable to my situation.
I have plenty of space on my webhosting - I am using only a fraction of it. Additionally, I have installed & reinstalled my FP extensions so many times my head is spinning. This issue has been taken to the engineer level of my webhosting company & nothing is working.
I am desperate for a resolution. I can't update my site properly & I need to to stay in business. If anyone at all has any info for me, I would greatly appreciate it.
I'd also like to hear what anyone thinks of switching to Dreamweaver. My worry is that I could have the same issue, and go through a long learning curve & increased expense. Though it would be worth it to me if it would resolve my issue.
My thanks in advance. :)
[edited by: pageoneresults at 8:39 pm (utc) on June 2, 2007]
[edit reason] Examplified URI Reference [/edit]
After I write this I will be sending you a Sticky Mail. I may have a solution to your problem, but I don't think the specifics can be discussed in an open forum. I am aware of a quirk when publishing which has to do with the connection.
There is one thing you can try - use the FP feature of publishing one file at a time. Right-click the file in the Folders View and select Publish Selected File. You can do several at once by holding down the control key when selecting.
Yes, I've been able to force a publish via right click...about 50% of the time, the other 50% I do get the same error message. This is how I've been getting by & continuing to do business...but I still feel I should be able to publish & update my site normally.