Microsoft Knowledge Base Email Alertz

KBAlertz.com: (327492) - When you use the Internet Services Manager to administer your Web server that is running Internet Information Server (IIS) 4.0 and Internet Information Services (IIS) 5.0, there is no option to install the FrontPage 2002 Server Extensions on a...

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 327492 - Last Review: February 21, 2007 - Revision: 4.1

FP2002: The Option to Install the FrontPage Server Extensions Does Not Appear

This article was previously published under Q327492

SYMPTOMS

When you use the Internet Services Manager to administer your Web server that is running Internet Information Server (IIS) 4.0 and Internet Information Services (IIS) 5.0, there is no option to install the FrontPage 2002 Server Extensions on a specific Web site. However, all other Web sites function as you expect.

CAUSE

This behavior can occur when you try to install the FrontPage Server Extensions on the second Web site instance of an IIS Web server. By default, this Web site instance is used for the IIS Hypertext Markup Language (HTML) Administration Web site. Therefore, the option to install the FrontPage Server Extensions does not appear on the first Web site that is created after you remove the HTML Administration Web site, or on the second Web site that is created on a server that does not have the HTML Administration Web site.

WORKAROUND

To work around this behavior, remove the affected Web site and create another Web site in Internet Services Manager. This new Web site has the Web site number of the previously used Administration Web site (W3SVC/2). After you complete the new Web site creation, you can re-create the affected Web site, and then install the FrontPage Server Extensions.

If you do not want to host another Web site, you can create a placeholder Web site to permit the sequential numbering of Web sites in IIS. To do this, follow these steps.

NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
  1. Start Microsoft Windows Explorer, and then create a folder named Placeholder in the InetPub folder.
  2. Use the following steps to start the Internet Services Manager:
    1. Click Start, and then point to Programs.
    2. Click Administrative Tools, and then click Internet Services Manager.
  3. Right-click your computer name, click New, and then click Web Site.
  4. When the Web Site Creation Wizard starts, click Next.
  5. On the Web Site Description page, type PLACEHOLDER in the Description box, and then click Next.
  6. On the IP Address and Port Settings page, type 127.0.0.1 in IP Address box, type PLACEHOLDER in the Host Header box, and then click Next.
  7. Type or locate the path for the Placeholder folder that you created in step 1, and then click Next.
  8. Under Web Site Access Permissions, click to clear all of the check boxes, and then click Next.
  9. Click Finish to close the wizard.
  10. In the Internet Services Manager, right-click the Placeholder Web site that you just created, and then click Stop.
The new Web site is created. However, you cannot the new Web site from Web clients.

MORE INFORMATION

IIS 4.0 and 5.0 numbers Web sites as the Web sites are created in the metabase, which is a private database of IIS settings. For additional information about the IIS metabase, click the article number below to view the article in the Microsoft Knowledge Base:
240941  (http://kbalertz.com/Feedback.aspx?kbNumber=240941/EN-US/ ) An Introduction to the IIS Metabase
By default, IIS Web sites are numbered sequentially as they are created, for example:
  • W3SVC/1: the Default Web Site.
  • W3SVC/2: typically the HTML Administration Web site.
  • W3SVC/3: typically the first user-created Web site.
When the administration Web site is removed, the sites are no longer numbered sequentially, for example:
  • W3SVC/1: the Default Web site.
  • W3SVC/3: the first user-created Web site.
When a new site is created, the site is numbered with the first available instance number, which is W3SVC/2, for example:
  • W3SVC/1: the Default Web site.
  • W3SVC/2: the second user-created Web site.
  • W3SVC/3: the first user-created Web site.
Although the new Web site can be used for hosting Web sites that are not FrontPage-enabled, the option to install the Server Extensions does not appear in the Internet Services Manager.

NOTE: Some of the security tools that have been released by Microsoft, such as the IIS Security Toolkit and IIS LockDown, remove the HTML Administration Web Site as a security measure, which can cause this behavior to occur.

APPLIES TO
  • Microsoft FrontPage 2002 Server Extensions
  • Microsoft Internet Information Server 4.0
  • Microsoft Internet Information Services 5.0
Keywords: 
kbprb KB327492
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please