Default Document Named Incorrectly in FrontPage (203020)



The information in this article applies to:

  • Microsoft FrontPage 98 for Windows
  • Microsoft Internet Information Server 1.0
  • Microsoft Internet Information Server 2.0
  • Microsoft Internet Information Server 3.0

This article was previously published under Q203020

SYMPTOMS

When you create a default document in Microsoft FrontPage, the document is named incorrectly.

Example:

default.htm;default.html;index.htm

This example assumes that the file names match the Web server's list of default documents names.

CAUSE

Microsoft Internet Information Server (IIS) supports multiple default document names. However, FrontPage does not currently support this functionality. FrontPage uses only the first entry in the list. In IIS version 3.0 and earlier, multiple names are used with semi-colons, so FrontPage sees the entire string of default documents as one name.

WORKAROUND

To work around this problem, use only one default document name in the list of default documents for IIS 3.0 and earlier. To use this method, you must remove all additional default document names in IIS.

To remove the additional default document names in IIS, do the following:
  1. Click Start, point to Programs, and then point to Microsoft Internet Server (Common).
  2. Click Internet Service Manager.
  3. Right-click the WWW site and click Service Properties.
  4. Click the Directories tab.
  5. In the box labeled Default Document, erase all but one Default Document name.
  6. Click OK.
If you need to use more than one default document, use commas with no spaces to separate the document names.

Example:

default.htm,default.html,index.htm

Note: FrontPage will only use the first entry in the list.

For additional information, see the following article or articles in the Microsoft Knowledge Base:

202729 Publishing Web Renames Default Document Incorrectly

STATUS

Microsoft has confirmed this to be a problem in FrontPage 98.

Modification Type:MajorLast Reviewed:12/8/2003
Keywords:kbbug kbpending KB203020