NOTICE: FrontPage 2002 Upgrade
Beginning Febuary 14th, 2002 we will be upgrading our servers to include the new Frontpage 2002 extensions. These extensions are backwards-compatible with older versions of FrontPage. Customers who are using older versions of FrontPage will still be able to edit and publish their web sites without any problems — with one possible exception:

Due to restrictions in the newer version of FrontPage, anyone with a username that begins with a number will need to receive a new username — FrontPage 2002 does not support usernames that begin with numeric characters. We will automatically assign new usernames to affected users. If you are affected by this restriction, please contact support on or after February 14 to request your new login information. Note that this change will affect FrontPage access only.

FrontPage 2002 includes a web-based administration panel, located at

http://yourdomain.com/_vti_bin/_vti_adm/fpadmcgi.exe

(where yourdomain.com is your domain name.) You can use this administration panel to manage subwebs and to add additional users to your FrontPage web. It can also be used to verify that FrontPage extensions are installed and working on your account — if the administration panel loads successfully, the extensions are installed and working.


Microsoft FrontPage is a WYSIWYG (what you see is what you get) web building program. If you use, or plan to use FrontPage to build and manage your website you must be sure to indicate this when opening your account. FrontPage requires special “extensions” installed on the server. If you do not have a FrontPage Account, you will need to contact us to have your account modified before your FrontPage Web will work.

A number of web-based tutorials are available to help you get acquainted with FrontPage usage and configuration, including those listed below. If you’re just getting started with FrontPage, we recommend that you take some time to familiarize yourself with its use. Please note that our FrontPage support is limited to installation/repair of FrontPage extensions on your account, and providing the correct configuration information below.

IMPORTANT NOTE: Substitute your actual domain name for yourdomain.com and your actual username for yourdomain in the instructions below. If the instructions below do not exactly match your particular version of FrontPage, review your FrontPage instructions for information on configuring your version using the configuration parameters below.

Configuration Parameters:

Destination Web Server1: www.yourdomain.com
Destination Web Name2: [leave this field blank in your configuration]
Username3: yourdomain
Password4: [your FrontPage password]

Configuration Notes:

  • This is your domain name preceded by www.. Use all lower-case letters. Some versions of FrontPage may ask you to “Specify the location to publish your web to” — this is your Destination Web Server.
  • The Destination Web Name must be left blank.
  • Your Username is your domain name without the TLD extension. If your domain name exceeds 25 characters, just use the first 25. Use all lower-case letters. Some versions of FrontPage ask for your “Name” instead of your “Username” — those fields are the same.
  • Your FrontPage password is independent of your other account passwords. If you requested FrontPage extensions when you ordered your account, your FrontPage password will match your original account password. If you requested FrontPage extensions after your account was set up, your FrontPage password may be different. Contact support if your password needs to be reset. Make sure the case matches the case of your password (i.e., if your password is a combination of upper-case and lower-case letters, be sure to enter the password using the appropriate combination.)

 

Publishing Your FrontPage Web

After you have created your web site on your computer, you will be ready to publish it to your account. Basically, this just means that you will upload them to our server. Once this is done, your pages will be viewable from the web. However, you must do this in the following manner. Most problems are caused by incorrect configuration settings — read this section carefully and follow the instructions, and your site should be published without problems.

Warning: FrontPage Account holders should never use FTP to transfer files as it can damage the FrontPage extensions.

    1. Launch FrontPage Explorer and open the web you?ve created on your computer.
    1. From the menu at the top of the window, select File, then Publish
    1. If this is the first time you publish to our server, select More Webs and enter the location you want to publish your FrontPage web to. (www.yourdomain.com). Hit Return (Enter) on your keyboard.
    1. If you have published to the server before, your Destination Web Server (www.yourdomain.com, where “yourdomain.com is your domain name — note the “www” in front.) will appear in the Publish window.
    1. IMPORTANT: Use www.yourdomain.com as the Destination Web Server to publish to our server. Leave the “Destination Web Name” blank.
    1. You will be asked for your USERNAME and PASSWORD. This is your domain’s User ID and your FrontPage Password (which may be different than your regular Telnet/FTP/POP password). If you’re not sure what it is or if you aren’t allowed past this point, you’ll need to contact support for a new FrontPage password.
  1. You can watch the progression of the upload by looking at the bottom left corner of FrontPage Explorer.

 

Open Your Published Web

Once your FrontPage Web is published and online, you will need to access it to make updates and changes. Be sure that you are connected to the internet before attempting to open your web on our server.

    1. Open FrontPage Explorer and choose File, then Open FrontPage Web.
    1. You can now choose to open a previously created web on your PC or your web on our server.
    1. Highlight the appropriate web or type in the web address (www.yourdomain.com) and click OK.
    1. Enter your Username and FrontPage Password if required.
  1. Make modifications and recalculate links if needed. (See your FrontPage Manual for info on when it’s necessary to recalculate links.)

 

What are FrontPage Extensions?

FrontPage Extensions are CGI programs which provide the server side implementation of FrontPage. The extensions allow your local computer to properly communicate with your domain through the http protocol using (RPC). We’re currently installing FrontPage 2000 extensions, which are fully backward-compatible with previous versions of FrontPage.

FrontPage Extensions and the Secure Server

You will not be able to call your FrontPage forms through the secure server. The best solution, if you need secure forms, is to convert your forms to useFormMail or CGIEmail, which are already installed on your account.

 

Troubleshooting Common Problems with Microsoft FrontPage

The following are common problems and solutions encountered with using Microsoft FrontPage. If you are having a problem not listed here, please feel free to contact support for help.

 

Internal Server Error when Publishing

There are a number of reasons why this error might occur. Usually a re-installation of the extensions will solve the problem. You should contact support when this occurs.

Error – “Root Web Busy”

FTP or Telnet to your site and remove the service.lck file in the /www/_vti_pvt directory. This usually happens when a FrontPage session is interrupted before completion.


Server timing out when publishing large sites.

There are a number of reasons why FrontPage hangs, but the biggest reason is related to the amount of data in your WWW directory, both in file size and in the number of files/directories. The more files/directories and size of data, the longer it will take FrontPage to log in. Large amounts of data (> 50MB) or a large number of files or directories ( > 500) can cause FrontPage to severely hang and even timeout. If there are connectivity problems between your ISP and our servers, then this can also lead to FrontPage hanging or even timing out. When you experience this problem, we recommend creating a number of smaller subwebs (or child webs) to break your web site up so it does not take FrontPage as long to run through its configuration or recalculate links.


Error – “Front Page Extensions not Installed”

We often see this error being reported even when the extensions have been installed. If you get this error, please contact support and we’ll make sure the extensions are installed and repair them if necessary.

NOTE: The extensions are easily corrupted. Please use only FrontPage Explorer to update your web site on the server. Never use FTP.


I published but my web’s not there!

This will happen when the “Destination Web Name” is filled in when publishing to our server. This box should be left blank. If you put any other name in this box it will create a subdirectory off of your root web and copy all of your files into it. Your site will exist under a subdirectory instead of at the top level www directory where it should be.


My counter, bbs, guestbook, etc isn’t working.

These problems are generally due to incorrect permissions on either the directory, file(s) or cgi script(s) that are associated with them. Please don’t change the permissions of your files or directories unless you have a specific reason for doing so and you know what effect it will have on your site.


My forms won’t work through the Secure Server.

The call to a CGI script using the Secure Server must not be within a webbot. Use a normal CGI call (e.g., FormMail or CGIEmail) in your HTML code for Secure Server calls.


My search bot doesn’t return any results.

The www directory must be world readable AND you need to recalculate links BEFORE publishing (or after editing directly on the server). If it still doesn’t work: Telnet to the server and go to the /www/_vti_txt/default.wti directory. Delete any files that begin with "ALL". Don't delete any other files. Then using Windows Explorer, do the same thing on your PC. Recalculate links, test locally with your browser and publish.


FP starts the Web Publishing Wizard when I try to publish.

Cancel the operation and contact support to have the FP extensions installed/repaired.


Why is my page renamed on the server when I publish?

The “Default Document” of your web is automatically renamed by the server to what is required by the configuration of the server. For example, if you’ve named the main page index.html, it may be renamed default.html. Just check the links to your main page to make sure they refer to it the same way.

NOTE: If you are using FrontPage, you should NEVER use regular FTP to upload your files. This will damage the extensions. Stick with one or the other all the time.