The information in this article applies to:
SYMPTOMSListing FrontPage Webs with FrontPage Explorer does not display the root Web <root web>. CAUSEIncorrect LIST permissions exist on the parent directory of the server[ASCII 146]s content directory <root web>. RESOLUTIONFrontPage 98 and FrontPage 97 authors and administrators require LIST permissions on the parent directory of the content root. If the Web site can be browsed publicly, then the Internet Guest Account (IUSR_<machine name>) will need LIST permissions to the parent directory of the content root. Examples for FrontPage 98 and 97:Method 1This method demonstrates how to add the required permissions for users and groups to the parent directory. The approach used in this example adds users or groups as they are needed; no blanket built-groups are used.
The above permissions will allow the System and the Administrators
to see the path to the Web content directory.
To allow a FrontPage Administrators or FrontPage Authors group to list the content directory, the chart changes to:
To allow anonymous users (IUSR_MACHINE NAME) and FrontPage Administrators
or FrontPage Authors to list (see) the content directory, the chart changes
to:
Method 2: Correct Content RootSet the content directory two sub-directories below the root directory. If the document root is only one subdirectory deep from the drive's root directory, the FrontPage installation program will not set the correct LIST permissions on the parent directory.c:\Inetpub\<content_root> Example: Incorrect Content Rootc:\<content_root>See Method 1 for permissions to the content parent directory. MORE INFORMATIONFor information on FrontPage permissions, see these Knowledge Base articles: Q173281 FP97: How to Reset Permissions for FrontPage 97Other resources: Microsoft FrontPage 98 Server Extensions Resource Kit (SERK): "Files and Permissions for Internet Information Server (IIS)" Additional query words: fpserver97 fpserver98
Keywords : fp97 fp98 |
Last Reviewed: August 11, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |