Update details
FrontPage 2002 Server Extensions are now available for Microsoft Windows x64 editions. This release of FrontPage 2002 Server Extensions is inclusive of all currently released security updates and other hotfixes as of January 31, 2005.
Note This release of FrontPage 2002 Server Extensions for Windows x64 editions is supported only on the Windows x64 editions that are listed in the "Applies to" section.
Installation details
How to obtain and to install the update
FrontPage 2002 Server Extensions for Windows x64 editions are located at the Microsoft Download Center. To download this update from the Microsoft Download Center, visit the following Microsoft Web site:
How to determine whether the update is installed
This release of FrontPage 2002 Server Extensions for Windows x64 editions is version 5.0.2.6738.
To determine the version of FrontPage Server Extensions that is installed on your Web server, follow these steps:
- Start FrontPage, and then open a Web site on your Web server.
- On the Tools menu, click Site Settings.
- On the General tab, locate the version number of the FrontPage Server Extensions from Microsoft.
You do not have to install this update if you have a later version of FrontPage Server Extensions already installed.
How to configure 32-bit emulation mode
To run FrontPage 2002 Server Extensions for Windows x64 editions, Microsoft Internet Information Services (IIS) must be configured to run in 32-bit emulation mode. To configure IIS for 32-bit emulation mode, follow these steps:
- Click Start, click Run, type cmd in the Open box, and then click OK.
- Change to the following directory:
\\%homedrive%:\Inetpub\Adminscripts
- In the Adminscripts folder, type the following command, and then press ENTER:
adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
- Type iisreset, and then press ENTER.
Note If your Web server is configured for x64 mode and if you did not correctly enable 32-bit emulation mode, you receive the following error message when you browse the Microsoft SharePoint Administrator:
The page cannot be displayed.
HTTP 500 - Internal server error.
If you remove FrontPage Server Extensions from the Web server, and therefore you have to reconfigure IIS to run in x64 mode, follow these steps:
- Click Start, click Run, type cmd in the Open box, and then click OK.
- Change to the following directory:
\\%homedrive%:\Inetpub\Adminscripts
- In the Adminscripts folder, type the following command, and then press ENTER.
adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 0
- Type iisreset, and then press ENTER.
How to configure the usage analysis, server health, and Integrated Indexing Server search features
The Help files that are included in FrontPage 2002 Server Extensions for Windows x64 editions contain incorrect information about configuring both scheduled usage analysis and the server health feature. This release of FrontPage 2002 Server Extensions for Windows x64 editions does not include the Microsoft SharePoint Timer service that would ordinarily process scheduled jobs.
This release of FrontPage 2002 Server Extensions for Windows x64 editions includes the same features as the original released versions of Microsoft Windows Server 2003, 32-bit editions.
The Wide Area Information Service (WAIS) Full Text Search and the SharePoint Timer Service, the utility used for scheduling usage analysis, are not included in FrontPage Server Extensions for Windows x64 editions. To configure the new Integrated Indexing Server Search that replaces WAIS, see the "Searching SharePoint Team Web Sites and FrontPage-Based Web Sites" topic that is located on the following Microsoft Web site:
If you must make administrative changes for FrontPage Server Extensions in the registry on Windows x64-bit editions, make your changes in the following location:
HKEY_LOCAL_MACHINE\Software\wow6432node\Microsoft\Shared Tools\Web Server Extensions
Note On 32-bit servers, the
Administrator's Guide to SharePoint Team Services and FrontPage Server Extensions 2002 currently lists the 32-bit server registry location as the following:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions
Because the SharePoint Timer Service is not included in this release of FrontPage 2002 Server Extensions for Windows x64 editions, scheduled features such as the processing usage analysis feature are not enabled by default.
For additional information about how to create a scheduled task for usage analysis, click the following article number to view the article in the Microsoft Knowledge Base:
889363
Usage analysis for Office XP Web Services does not automatically occur on a server that is running Windows Server 2003
Additional information
Microsoft Index Server processes are started if they were not previously running. These processes are required for searches to work on your Web server.
After you install FrontPage 2002 Server Extensions for Windows x64 editions, the following issue may occur:
- You have to open port 80 in the Windows Firewall. Port 80 must be opened for FrontPage clients to connect to the site and to author or to publish on the site.
Note By default, Windows Firewall port 80 is closed in Windows Server 2003 Service Pack 1 (SP1).
To open port 80, follow these steps:- Click Start, click Run, type ncpa.cpl in the Open box, and then click OK.
- In the Network Connections window, right-click the local area connection that is used to externally connect to the server, and then click Properties.
- On the Advanced tab, click Settings under Windows Firewall.
- On the Exceptions tab, click Add Port.
- In the Add a Port dialog box, type a name for the port in the Name box, type 80 in the Port number box, and then click OK.
- Click OK to close the Windows Firewall dialog box.
- Click OK to close the Local Area Connection Properties dialog box.
Note If you have to remotely administer FrontPage 2002 Server Extensions from Microsoft, you also must open the port that is used by the Microsoft SharePoint Services administrator.
Technical support for Windows x64 editions
Your hardware manufacturer provides technical support and assistance for Microsoft Windows x64 editions. Your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.
For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:
For product information about Microsoft Windows Server 2003 x64 editions, visit the following Microsoft Web site: