A. If you do not HAVE to have FP Extensions on your site then do NOT install them on your site.

FrontPage Extensions are used by some development environments to deploy your files to the server. They may also be required for some component you are using, especially if you developed your site with FrontPage.

FrontPage Extensions alter the permissions of your files, and can cause some issues with locking files. Do not install them unless you really need them.

A. To login using FrontPage extensions, you are required to use the our local domain ( "jgl\") name with your username. The format is:
Username : JGL\YourUserName
Password : YourPassword

A.

1. Login to the Control Panel
2. Go to the FrontPage Extensions page
3. Select the domain from the drop down list.
4. Click the install button, and wait a few seconds for the confirmation.

A. Frontpage extensions puts hidden files in your folders that can cause this. Try deleting the contents of the folder, then deleting the folder. If that does not work. You may just have to wait a day, or a week, to be able to delete the folder because it is corrupt. You can just ignore the folder and work around it, or you can use it, but you cannot delete it.

A. Visual Studio uploads will not work with the temporary address. You will need to use FTP to upload your files until your domain name propagates. Then use the permanent web address to upload your files.

To be clear, it is not possible to use the FrontPage Extensions upload feature with the temporary address. It can only be done with your permanent URL.

A. You probably deleted some of the files or folders required by FrontPage Extensions.

1. Login to the control panel
2. Go to the FrontPage Extensions page.
3. Select the domain from the drop down list
4. Click install to reinstall your extensions.

A. This happens when some of the FrontPage Extensions files (or folders) are missing from your domain folder. It is very common that you have deleted some files and accidentally deleted some of the files belonging to FP extensions.

1. Login to the Control Panel.
2. Go to the FrontPage Extensions Page.
3. Select the domain from the drop down list.
4. Click "Install".

This will install or re-install the extensions and correct the problem.

A. Your domain name must have propagated to our servers before you can reach the FrontPage Extensions Admin pages.

After installing FrontPage Extensions, you will be able to access your FrontPage Extensions Administration pages with the following URL, but substitute your domain where it says "myDomain".

Example:
http://myDomain.com/_vti_bin/_vti_adm/fpadmdll.dll?page=webadmin.htm

You will then need to provide your UserName prefixed with "JGL\" as follows

Example:
UserName = JGL\myAquestUserName
UserName = myPassword

Please note that you do not have the permissions to add users.

A. Contact Aquest Hosting support to have them setup your Indexing service catalog.

A. This is because the ASP.dll handles asp pages and prevents the FrontPage Isapi dll from handling the request.

Also, if you change to a HTML page, you will still need to have Aquest Support Staff create an Indexing catalog for your site before the search component will work correctly. Please create a Trouble Ticket to request having an Index catalog created.

A. After considerable head-scratching, I found that if I used an Access Query within the FrontPage Data Results Wizard (DRW), it won't work.

HOWEVER, in the FrontPage DRW, if I select a "Custom Query", and insert the SAME Access Query, everything works fine. There is a problem with what FrontPage is trying to do. The first time you open the "Custom Query" dialog, you can see that FrontPage is putting quotes (") around the Access query name. This won't work. But if you replace the quotes (" ")) with brackets ([ ]), FrontPage DRW now works!

Example:
What FrontPage tries to do: SELECT * FROM "My Query"
What is needed to work : SELECT * from [My Query]

I don't know why FrontPage is messing up the queries, but the "messed up" queries work with IIS 5.0. But they don't work with IIS 6.0!

A. The FP2003 code has changed slightly. To see the true error, open the hidden folder /_fpclass/ and edit the fpdbrgn1.inc file

At about line 19, change :
fp_DEBUG = False
to :
fp_DEBUG = True