|
|
|
Providing Microsoft FrontPage Server Extensions for:
|
||
| ||||||
The FrontPage Server Extensions must be installed and executed using the native Administrator account, user name Administrator, on both Windows Server 2008 and Vista.
The FrontPage Server Extensions kit is intended to run on Vista Ultimate, Vista Business, Vista Enterprise and Vista Home Premium.
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.
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.
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\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
Support is available:
- On our FAQ.
- From various newsgroups
- http://forums.iis.net/1045.aspx- Ready-to-Run Software, Inc's FPSE Support Team
- 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.
- Please review this article: http://support.microsoft.com/kb/555175 with special attention to method 11.
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
How do I create a log file during installation so I can review it or send it to support for addition 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.
In 64 bit Operating System, 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.
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.
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.
Windows 7, Windows Server 2008 R2 and the FrontPage Server Extensions
Windows 7 and Windows Server 2008 R2 are NOT presently FrontPage Server Extension supported platforms. The FrontPage Server Extensions are intended for Windows Server 2008 and most Vista operating systems.
At this time Microsoft has no plan to support the FrontPage Server Extensions on the Windows 7 or Windows Server 2008 R2 operating system.
I receive a 401.1 error when I attempt to administer my site locally but I can administer the site remotely.
Suggested resolutions:
Since 1991 Ready-to-Run has been providing the marketplace with our porting expertise. We have been working with the Microsoft FrontPage Server Extensions for over ten years and are currently working with Microsoft to provide the server extensions for Windows Server 2008 and Windows Vista.
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.
Ready-to-Run Software, Inc Privacy Statement
Email addresses listed on this site may NOT be used for unsolicited commercial email.
|
® 1998 - 2010 Microsoft Corporation.
All rights reserved. Terms
of Use. © 1998 - 2010 Ready-to-Run Software, Inc. All rights reserved. |
