Article ID: 234261
Article Last Modified on 2/22/2007
APPLIES TO
- Microsoft FrontPage 2000 Server Extensions
This article was previously published under Q234261
SYMPTOMS
When you click Configure Server Extensions from the Task menu in the IIS Microsoft Management Console (MMC), the Server Extensions Configuration Wizard never starts and you are unable to install the FrontPage Server Extensions. The problem occurs for any virtual server where you attempt to install the Server Extensions.
CAUSE
This behavior occurs if there is no local path specified on the Home Directory tab of the default Web site.
RESOLUTION
To resolve the problem, do the following:
- Click Start, point to Programs, point to Windows NT 4.0 Option Pack, point to Microsoft Internet Information server, and click Internet Service Manager. This will open the MMC.
- Click the plus sign ( + ) next to the Computer Name and click Default Web Site.
- Right-click Default Web Site and click Properties.
- Click the Home Directory tab.
- For Local Path, click the Browse button and point to the content directory location for this Virtual Server. IIS sets the default location to C:\inetpub\wwwroot during the install of IIS. Your content directory for the Default Web Site may be different.
- Click Apply and click OK.
MORE INFORMATION
To install the FrontPage 2000 Server Extensions using the Server Extensions Configuration Wizard, the Server Extensions require that the IIS instance /LM/W3SVC/1, usually associated with Default Web Site, be configured with a Local Path and be in working order.
If the Default Web Site was renamed and you are unsure which site it is, you can use the steps in the article listed below to locate the instance /LM/W3SVC/1.
For additional information, see the following article or articles in the Microsoft Knowledge Base:
214515 How to Determine which Virtual Server or Multihosted Web Site References [Port /LM/W3SVC/#:]
Additional query words: front page
Keywords: kbprb KB234261