Ready-to-Run Software, Inc

Ready-to-Run Software, Inc
 

Microsoft FrontPage
RTR FrontPage Server Extensions for:
Microsoft Windows Server 2008 R2
Microsoft Windows 7
Microsoft Windows Server 2012
Microsoft Windows 8
Microsoft Server 2012 R2

Providing Microsoft FrontPage Server Extensions for:
  • Microsoft Windows Server 2008 (Code Name "Longhorn")
  • Microsoft Windows Vista


FAQ -- Frequently Asked Questions

Windows 7, Windows Server 2008 R2 and the FrontPage Server Extensions for IIS7.5

Windows 8, Windows Server 2012 and the FrontPage Server Extensions for IIS8

Windows Server 2012 R2 and the FrontPage Server Extensions for IIS8.5

RTR FrontPage Server Extensions Release News
Back to FAQ

What users can install the FrontPage Server Extensions?

The FrontPage Server Extensions must be installed and executed using the native Administrator account, user name Administrator, on Windows Server 2008, Vista, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012 and Windows Server 2012 R2.

Back to FAQ

Which versions of Vista can run the FrontPage Server Extensions?

The FrontPage Server Extensions kit is intended to run on Vista Ultimate, Vista Business, Vista Enterprise and Vista Home Premium.

Back to FAQ

How do I fix the "_vti_bin" could not be accessed error?

      After installation, I tried to extend the web site but received an error saying ‘_vti_bin’ could not be accessed.

·         FrontPage Server Extensions is a legacy application that requires the user to be logged on as the native Administrator account, user name Administrator.

Back to FAQ

How do I fix Vista Ultimate "internal error"?

1.                          I tried to install on Vista Ultimate but the installation failed right away with ‘An internal error has occurred. (               ) Installation ended prematurely because of an error.’

·         There is a problem with some installations of Vista where vbscript.dll fails to be registered properly.  Please login as Administrator, open a cmd window, cd to where vbscript.dll lives (usually c:\windows\system32), and run the command: "regsvr32 vbscript.dll".  You should see a success message, then try installing FPSE again.

Back to FAQ

How do I fix the "unable to read configuration for Microsoft Internet Information service"?

After I installed the extensions, I got a message saying it installed successfully, but then a message saying: "unable to read configuration for Microsoft Internet Information service"

·         Log on as the native Administrator account, user name Administrator

·         Start a cmd.exe window

·         Cd C:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\50\bin

·         Enter the following commands in the cmd window:

  •  owsadm.exe -o setproperty -pn ValidateServicesCnf -pv fix

  •  owsadm.exe -o setproperty -pn CheckRolesConfig -pv fix

  •  owsadm.exe -o setproperty -pn TightenSecurity -pv fix

  •  owsadm.exe -o setproperty -pn CheckUserAccess -pv fix   

  •  owsadm.exe -o check

Another possible cause and solution submitted by a member of the FPSE community: (thank you)

It may be possible to get this error if no http bindings are configured. For example, the user had a site that only had https bindings. No matter what they tried, they could not get FPSE to extend it. But, once they added an http binding (any port), they were able to extend the site.

 

Back to FAQ

Where can I get support for FPSE?

            Support is available:

Back to FAQ

When I try to install the Server Extensions, I receive the message "Your system has updates that need to be applied during the next reboot.  Please reboot your system before installing ..." Rebooting doesn't help.  Can you help me?

  • The Windows Installer 4.0 property, MsiSystemRebootPending, which is not set by FPSE, is already set when the FPSE installer checks it.  The machine gets stuck in the state where it thinks a reboot is needed, but after rebooting doesn't clear this property.
  • From the original article: How to resolve Common "Windows Installer" Problems, http://support.microsoft.com/kb/555175

    • Method 11
       Check for pending installation/s:
       Warning: You should only edit these registry entries if you really know what you're doing. Back up your hard disk first.  
       

    • a. Empty "InProgress" Registry Key
      Check the following registry key:
      HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
      and clean any entries that you find.

    • b. Empty/Rename "PendingFileRenameOperations" Registry Key:
      Check the following registry key:
      HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
      and clean any entries that you find.

On a 64-bit computer, be sure to look at both the 32-bit and 64-bit paths identified in the article:

  • HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress

  • HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Installer\InProgress


     

Back to FAQ

How do I create a log file during installation so I can review it or send it to support for additional help?
  • Start the install of the FrontPage Server Extensions from a cmd line and create a log file.  To do this:  launch a cmd.exe window with "Run As Administrator" property set.  In that DOS window, type "<fpse_msi> /l*v logfile", where <fpse_msi> is replaced with the actual MSI name and logfile is the path and name of the log file to create. You will have to navigate to the location of the msi file or specify the full path in the cmd window.
Back to FAQ

In 64-bit Operating Systems, why do I get the error: FPSE 2002 on Win 2008 server --> Service Unavailable and the AppPool shuts down?

  • Please refer to this thread from the IIS7.NET Forum for additional information.
Back to FAQ
When I try to download the Server Extensions via FTP using Internet Explorer, I get the 'cannot display the webpage' message.  Can you help?

  • From the main Internet Explorer menu, select the Tools button and then select Internet Options from the drop down menu.

    In the Internet Options window, click on the Advanced tab.  In the Advanced tab window, scroll down in the Settings window to the Browsing section.

    Under the Browsing header, look for the checkbox rule stating: Use Passive FTP (for firewall and DSL modem compatibility). 

    Verify that the checkbox is NOT checked.  Uncheck it if necessary.

    Click on the Internet Options window Apply button to save the configuration.

    Click on the Internet Options window OK button to close the dialog.

    You should now be able to successfully download the FrontPage Server Extensions via FTP using Internet Explorer.

Back to FAQ

When I try and install the FPSE02_win2008_vista_rtm_ENG.msi on a 64-bit Vista machine, I get the error message "An internal error has occurred.

  • Perform regsvr32 on c:\windows\sysWow64\vbscript.dll, NOT the c:\windows\system32\vbscript.dll.  You may re-register the original file after the installation has completed.

Back to FAQ

I receive a 401.1 error when I attempt to administer my site locally but I can administer the site remotely.

  • This error is caused by using Windows authentication and an interaction between IIS and Internet Explorer and not the FrontPage Server Extensions.
  • When Windows authentication is used with a fully qualified domain name (or a name with a '.' in it), attempts to administer the site will fail because the browser thinks it needs to go through a proxy server, even though the site is on the local machine.
  • Windows authentication should not be used when authentication is done over the internet.

Suggested resolutions:

  • In Internet Explorer, if a proxy server is being used, the site name should be added to its list of sites to bypass.
  • In Internet Explorer, if a proxy server is not being used, a proxy server should be configured and then the site should be added to its list of sites to bypass.
  • Use Basic authentication with SSL.
  • Disable Loop Back (KB896861)
  • One user reported success with this method  http://support.microsoft.com/default.aspx?scid=kb;en-us;896861
Back to FAQ
 

The RTR FPSE download only shows weird text in the browser window

  • Add fpse.rtr.com to your trusted sites
Back to FAQ

Where (and what) is the _vti_bin directory?

  • The _vti_bin is a virtual directory used by the FrontPage Server Extensions that points to the C:\Program Files (x86)\Common Files\microsoft shared\Web Server Extensions\50\isapi folder and is viewable in the IIS Manager.
Back to FAQ

I cannot logon to the FPSE, even using the administrator account.
Back to FAQ

Can't open web in MS FrontPage 2003 (XP), getting the following error message that reads: "The folder [the URL of the web] isn't accessible. The folder may be located in an unavailable location, protected with a password, or the file name contains a / or \."

  • Find the MS FrontPage shortcut, starting the program. Right-click on it and open Property. Choose Compatibility. Select "Run this program in compatibility mode for". Choose "Windows XP (Service Pack 3)" This should solve the problem.
Back to FAQ
 

Who is Ready-to-Run Software, Inc.?

Since 1991 Ready-to-Run has been providing the marketplace with our porting expertise.  We have been working with the Microsoft and the FrontPage Server Extensions for over twenty three years and currently provide the server extensions for Windows Server 2008 R2, Windows 7, Windows Server 2012, Windows 8 and Windows Server 2012 R2.

Our porting expertise has been utilized by such firms as O'Reilly and Associates, Bantam, Random House, and Prentice Hall, GTE, 3M, Exxon and many others. Out of these experiences grew our Porting Center. The Porting Center offers 15 different UNIX platforms and many Windows platforms. Our experts are available to assist you. If you have neither the time nor the man power we can do the porting for you.

Back to FAQ

 
Microsoft, FrontPage, Windows Server 2008, Vista, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012 and Windows Server 2012 R2 are either registered trademarks or trademarks of Microsoft Corporation in the U. S. A. and/or other Countries. Other product and company names mentioned herein may be the trademarks of their respective owners.

Questions or problems regarding this web site should be directed to .

Ready-to-Run Software, Inc Privacy Statement

Email addresses listed on this site may  NOT be used for unsolicited commercial email.

® 1998 - 2016 Microsoft Corporation.   All rights reserved.  Terms of Use.

© 1998 - 2016 Ready-to-Run Software, Inc.  All rights reserved.