homepage Welcome to WebmasterWorld Guest from 54.166.110.247
register, free tools, login, search, pro membership, help, library, announcements, recent posts, open posts,
Become a Pro Member
Visit PubCon.com
Home / Forums Index / Code, Content, and Presentation / WYSIWYG and Text Code Editors
Forum Library, Charter, Moderator: open

WYSIWYG and Text Code Editors Forum

    
Cannot upload FrontPage website to apache/linux
help please
grayhair




msg:3892492
 10:50 pm on Apr 14, 2009 (gmt 0)

hi,

I have read through what I can find about uploading a FrontPage site both by ftp and through publlishing but can't find an answer.

I have installed the FrontPage extensions but when I try to publish I get an error message

"Unable to open ......
Server error: The Web server at ------ does not appear to have Windows SharePoint Services installed.
1. The web server may not have the FrontPage Server Extensions installed.
2. The web server may be temporarily out of service
3. If you are connecting through a proxy server, the proxy settings may be incorrect.
4. An error may have occurred in the web server.

I even uninstalled and reinstalled the FP extensions.

In reading through the instructions for setting up to upload via ftp it says you cannot do this unless the name servers have been changed to the new host and have propagated. But I tried anyway and got "the folder '/public_html' does not exist on the remote web location. Would you like a folder created at that location? answer yes. Then I get the error message "Could not find a web server at ---------. Please check to make sure that the web server name in 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'd really rather not upload via ftp.

I get the same two messages whether the FP and SharePoint settings are default or none.

I'm not sure what proxy settings the error message is talking about. I have checked and double-checked that the temporary web address I was given is typed in right.

I have posted to the host forum but have not had any answers. I am on deadlines and really need help with this.

thanks

 

bill




msg:3892717
 7:27 am on Apr 15, 2009 (gmt 0)

The last version of FrontPage was released in 2003. FrontPage has been discontinued. The replacement is Expression Web which is already well into its second release. Expression Web can work with the old FP extensions, but it is designed for a SharePoint server. FP extensions are no longer supported at many hosts as they are problematic.

That said, if you you still need to work with FP then you might be better off to simply open the host site with a standard FTP client to see if you can connect. Create the folders FP is asking for manually and see if that doesn't work.

If the site doesn't use components like form handlers and the few other things dependent on FP server extensions, then you could safely publish the site to your local machine, and then FTP the whole lot to the server.

SteveWh




msg:3892757
 8:36 am on Apr 15, 2009 (gmt 0)

1. Decide whether you really have to use the FP Extensions. You don't have to use them just because your site was created with FP. At [support.microsoft.com...] is a list of the FP features that require them. "File upload" means HTTP publishing. If you don't use any of those features, turn the FPE off and leave them off. Unless you absolutely must have them, the FPE are more trouble than they're worth.

Merely "wanting" to publish with HTTP publishing isn't good enough reason by itself to install the FPE. You can publish by FTP (instead of HTTP) from within FrontPage. It works just the same as HTTP publishing, with the same options available, but it uses FTP, and it works well.

But you cannot mix the two. Every time you publish with FTP, you corrupt the FPE, and must uninstall and reinstall them. After you corrupt the FPE, subsequent HTTP publishing attempts will always fail until you reinstall the FPE.

2. If you must have the FPE: uninstall them, "clean up old extensions", and reinstall them, and don't play around with FTP anymore.

3. Wait until your domain has propagated. It can take 72 hours, but my last one only took 15 minutes and was completely finished worldwide within 12 hours. You'll know it's propagated sufficiently when you type your domain name into your address bar and actually wind up at your site or whatever holding page your host puts there.

4. Search the site of your web host for FAQ and tutorials. Many hosts have detailed instructions about how to deal with their particular installations of the FPE. If your webhost doesn't have such a FAQ, you could also try the sites of other webhosts.

But basically, wait for the domain to propagate, and then use your real (not temporary) domain name, and if you choose HTTP publishing, don't ever use FTP.

In addition, when the FPE are installed, there are .htaccess commands that you cannot use. You cannot use mod_rewrite (RewriteRule), such as to redirect from www. to non-www or vice versa. If .htaccess contains any offending commands, HTTP publishing will fail.

Whenever HTTP publishing fails, you get basically the same error screen as what you posted in your message. It's not specific enough to be very helpful, and it covers many possible error situations, including the ones I described above.

[edited by: SteveWh at 8:51 am (utc) on April 15, 2009]

grayhair




msg:3893342
 10:51 pm on Apr 15, 2009 (gmt 0)

Yes, I know FP is outdated (been using it since 1997 version) as is all the rest of my software/hardware but it's what I have to work with. It's not as easy for me to learn new software as it used to be (wish it was) and it is very important that I do the work instead of trying to learn how to do the work at this point in time. I would love to know how to hand code and how this stuff actually works but that ain't gonna happen.

Unfortunately, I'm not sure exactly what components have been used on the site over the years. It's been up since 2001 and I am still learning as I go. The site is not sophisticated but it looks and works ok and has ranked very high for several key phrases for several years. I know there is a form but it could be removed.

I read somewhere that if you use ftp you have to manually keep track of the files that change which would cause me a problem. Is that true?

I may have to just go ahead and take the downtime and change the nameservers and upload then, although this is a high traffic season for me. (High traffic being a relative term for a small niche site.)

thank you very much for your help

SteveWh




msg:3893409
 1:38 am on Apr 16, 2009 (gmt 0)

Do I gather correctly that you are moving the existing site to a new webhost?

Ask the new webhost if they can transfer the entire site for you. They use a server-to-server transfer feature that is available in cPanel. To use this feature, both servers must be using cPanel, but it's ok if the two are different versions.

If the new host isn't willing or able to do it, you can also do it yourself. Again, cPanel is required. On the old server, go to cPanel > Backups, bundle up a complete backup copy of the site, and then follow the instructions to send the backup directly from the current server to the new server using FTP (not from home; it's direct server-to-server).

It arrives on the new server as, I think, a .gz or .tar.gz file, which the new host can then unzip and thereby reconstruct the entire site, including all existing settings such as email addresses, filters, etc.

You can and should do the transfer by that method before you change the nameservers. Then the new site will be all set up by the time visitors start arriving. That will avoid any downtime. For a short period, it will be unpredictable which server each of your visitors gets sent to, but every visitor will get to one of the two functioning versions of the site.

-----

Using FTP publishing from within FrontPage is no different from using HTTP publishing. You can publish only changed files, and you don't have to keep track yourself. If you use a separate FTP program, outside FrontPage, then you might have to keep track.

[edited by: SteveWh at 1:40 am (utc) on April 16, 2009]

grayhair




msg:3893436
 2:46 am on Apr 16, 2009 (gmt 0)

yes, I am moving the existing site to a new webhost.

They do not move them for you. They partner with a company that will do it but it would cost me almost $300.00.

One of many reasons (don't get me started) I am moving is because my current host is in process of merging and I have not been able to login to cPanel for two or three weeks now. (error: "AdvAdmin.AccountAdmin.1 error '80004005' HostingController components are not allowed to response outside to their scope.")

They didn't even have the decency to let me know they were changing and didn't seem concerned with my problem. It doesn't look like they are in hurry at all to fix it, if they are even going to fix it.

I do have access to cPanel at the new host. I have already backed up a remote to local copy of the site to my computer, although I was going to delete a lot of files on the new upload but I could do that later.

Can I use cPanel at the new host to upload the backup from my computer or would I have to use cPanel at the current host and use the copy that is already uploaded there?

It is very frustrating.

Thank you so much for your help.

SteveWh




msg:3893483
 4:40 am on Apr 16, 2009 (gmt 0)

How big is the site in MB?

Do you have a forum or shopping cart or anything else that uses a MySQL database?

Do you have a large number of email addresses, forwarders, filters, etc?

I have already backed up a remote to local copy of the site to my computer

Was it...

1) an "official" backup in .tar.gz format generated from cPanel > Backups > "Download or Generate a Full Web Site Backup"

or

2) a backup you made by either
a) "Reverse publishing" from inside FrontPage or
b) copying all the website files manually by FTP or
c) some other similar method?

#1) will contain everything you need to recreate the website.
#2) will contain only the website document files, and you'll have to manually create all your email accounts, databases, etc. from scratch.

Obviously #1 is preferable. If you used that, you should be able to turn off the FP Extensions, upload the .tar.gz file to public_html, and your new host can unzip it and do whatever other actions are required to recreate the site as it was, in its entirety, IF they're willing to do even that much.

If they are not willing to do it, I can't offer any assistance because I don't know the methods involved. It could simply involve unzipping the file, but I suspect there is more to it. Hopefully someone else can help on that.

Continuing on... if the host won't unzip the .gz, and if you can't find out how to do it yourself, the last resort is to...

Turn off the FPE. Publish the entire site from within FrontPage, using FTP publishing. That will at least put the files in their places.
Manually set up all your email accounts, databases (if necessary), and any other parts of the site that weren't transferred by the FTP publish.
Now try going to your site by typing into your address bar the temporary URL your new host provided. Browse around. If your themes, navigation link bars, forms, and other features are, or look, broken, it's a sign you probably need the FrontPage Extensions.
So try turning them on, and browse through the site again.
Everything working?
After you turn on the FPE, never use FTP publishing again.

I have found 3 sources saying that you cannot use FrontPage HTTP publishing until your domain has propagated, so at this point you must change the nameservers. Don't try to publish with HTTP until that is done. If you do and it fails, you'll need to reinstall the FPE, and every time you do that, there are parts of your site that get deleted on the server, and you must republish them.

After propagation is complete, browse your site again to ensure it's working.
Try HTTP publishing to publish a single page.
If it doesn't work, post in your new host's forum or file a support ticket.

[edited by: SteveWh at 4:57 am (utc) on April 16, 2009]

grayhair




msg:3894187
 11:44 pm on Apr 16, 2009 (gmt 0)

The site is 95 MB

I had a forum but deleted it although there may be some stray files that I don't know about.

There is no shopping cart or anything else that uses a database except a small survey form that can be deleted.

There are only a few email addresses, no forwarders I remember but I did have a lot of spam filters. I've already recreated the email addresses at the new host and will use their filters and reconstruct my manual ones as needed.

Unfortunately, the backup was done with reverse publishing. I still cannot get into cPanel on current host so option #1 won't work.

I did retry ftp but neither FP or ws_ftp could find the temporary ftp site. I'm wondering if it has anything to do with both http and ftp are temporary addressess. I may have to just change the nameservers and do the downtime.

I have sent a help ticket to the new host. I hope they can help before I have to use last resorts.

sigh

SteveWh




msg:3894338
 5:29 am on Apr 17, 2009 (gmt 0)

The site is 95 MB

Ok, even if you're on dial-up, a full FTP upload from home should only take 6-10 hours. It's a long time, but at least it's not impossible.

I had a forum but deleted it although there may be some stray files that I don't know about. There is no shopping cart or anything else that uses a database except a small survey form that can be deleted.

It sounds like there was no database, or if there was, it didn't have anything important in it. So, there's no loss there.


There are only a few email addresses, no forwarders I remember but I did have a lot of spam filters. I've already recreated the email addresses at the new host and will use their filters and reconstruct my manual ones as needed.

At least that's taken care of.

I did retry ftp but neither FP or ws_ftp could find the temporary ftp site.

As a temporary address, did they provide you with an IP address? Try using that for FTP. One to try would be ftp://nnn.nnn.nnn.nnn/.


I'm wondering if it has anything to do with both http and ftp are temporary addressess. I may have to just change the nameservers and do the downtime.

I'd recommend waiting for their reply to your help ticket AND getting the temporary address thing figured out before making any nameserver changes. You don't want to change the nameservers and then discover that their system is messed up. Then you'd be suffering downtime for no good reason. This is a test of their ability and their willingness to assist. If they fall down on this, you can take their money-back guarantee if they offer one, or just abandon this effort and go shopping for a new-new host.

Global Options:
 top home search open messages active posts  
 

Home / Forums Index / Code, Content, and Presentation / WYSIWYG and Text Code Editors
rss feed

All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
Home ¦ Free Tools ¦ Terms of Service ¦ Privacy Policy ¦ Report Problem ¦ About ¦ Library ¦ Newsletter
WebmasterWorld is a Developer Shed Community owned by Jim Boykin.
© Webmaster World 1996-2014 all rights reserved