Article ID: 3717, created on Feb 8, 2008, last review on Apr 25, 2014

  • Applies to:
  • Helm 3


In Helm I try and install FrontPage Extensions on a site, and it says it has done so, but in actuality it hasn't.


Is the FrontPage Admin Account used in Helm an administrator account on the server? Try logging in with it using terminal service/remote desktop. (Only admins can login - so verify the username/password are correct and that the account is a admin account.) 

1. Make sure the port is correct. Verify the Microsoft SharePoint Administration port and the port in Helm is correct. It is easy to typo.
2. Also, under the Microsoft Sharepoint site in IIS, go to Properties, then to the Directory Security tab. Ensure that Windows Authentication and Basic Authentication is enabled.

3. Last, make sure the Microsoft Sharepoint Administration site is running and that the IP is either "All Unassigned" or the IP of the Helm Server (which is usually the main IP assigned to the server).
When trying to install FP extensions through Helm I get the error "Unable to install Frontpage Extensions". There is also a long error in the error log.

1.) Go to the web service (IIS) in Helm.
2.) Make sure that the port number entered for Frontpage is correct (details on how to check this can be found in the Quick Install guide).
3.) Make sure that the password you have entered into Helm for FP matches the password you are using to login to Sharepoint. If these are different then Helm will not be able to connect to Sharepoint and create the extensions.
4.) If none of the above tips work, go into Sharepoint and make sure you can create the extensions and the _fp user manually yourself. If you cannot do it, then Helm will not be able to. Frontpage is quite unstable and in this situation you may need to contact Microsoft.
If you have tried 1) - 3) with no success, and tip 4) lets you create the extensions and the _fp user, then raise a support ticket to WHA.

110556ad4b9f1c73a3682661cd1dca89 152090ff5e9a05ea7e1cf0c248449638 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF