Getting error—"Root Web Busy"
FTP or Telnet to your site and remove the "service.lck" file in /www/_vti_pvt. This usually happens when an FP session is interrupted before completion.
Server timing out when publishing large sites.
This difficulty arises when the uploading link times out in the process of copying the Web to our server. The only suggestion Microsoft has offered so far is to break the main Web into a group of sub-Webs on your PC, then upload these individually. If this problem persists, please contact us.
Getting error—"FrontPage 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. Also, realize that you may use your Web Control Panel to re-install/repait the FrontPage extensions.
NOTE: The extensions are easily corrupted. Please use only FP Explorer to update your FrontPage-based Web site on the server, not 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, FP 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 where it should be.
My counter, bbs, guestbook, etc. aren't working.
These problems are generally due to incorrect permissions on either the directory, files or CGI scripts 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 in your HTML script 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: FTP 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 either contact us to have the FP extensions installed/repaired, or you may do so yourself via your Web Control Panel.
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 may damage the extensions. Stick with one or the other at all times.
