Microsoft KB Archive/296583

= FP98: FrontPage Server Extensions Do Not Work As Expected =

Article ID: 296583

Article Last Modified on 1/7/2006

-

APPLIES TO


 * Microsoft FrontPage 98 Standard Edition, when used with:
 * Microsoft Windows NT 4.0

-



This article was previously published under Q296583



For a Microsoft FrontPage 2000 version of this article, see 296596.



SYMPTOMS
After you install Microsoft FrontPage Server Extensions on a Web, some or all of the following symptoms occur:  In Microsoft FrontPage, you are unable to list Webs from the Web server. When you attempt to browse the Web, you receive intermittent error messages similar to the following:

HTTP Error 405

405 Method Not Allowed.

The method specified in the Request Line is not allowed for the

resource identified by the request. Please ensure that you have the

proper MIME type set up for the resource you are requesting.

Please contact the server's administrator if this problem persists.

 When you view the Event log on the Web server, you notice Access violation events with an Event ID of 80002.



CAUSE
Some or all of these issues may occur when you install FrontPage Server Extensions on a Web whose root directory is &quot;nested&quot; within the content directory of another Web (nested content).

FrontPage Server Extensions (FPSE) installed on a site attempt to control all content in that site. When the directory structure of one FPSE-based Web is inside that of another, permission conflicts may arise as more than one installation of FPSE is applied to the nested Web site.

Each FPSE-based Web site that has been assigned a unique IP address must have its content directory at the same level as other uniquely assigned Web sites.



RESOLUTION
To resolve this issue, move all Web content folders to the same level in the directory tree. To do this, follow these steps:  Log on to the Web server as administrator. Start FrontPage Server Administrator.</li> Under Select server or port, click a server or port, click Uninstall, click OK to confirm the removal of the FPSE software from the selected server or port, and then click OK again.</li> Repeat step 3 for every server or port in the Select server or port list.</li> Click Close to quit FrontPage Server Administrator.</li> Start Internet Service Manager.</li> Under Console Root, expand Internet Information Server, and then expand * , where  is the name of the Web server.</li> Right-click a Web site (for example, Default Web Site), and then click Stop on the shortcut menu that appears.</li> Repeat step 8 for each Web site.</li> Click Start, point to Settings, and then click Control Panel.</li> In Control Panel, double-click Services.</li> In the Service dialog box, click World Wide Web Publishing Service in the Service list, click Stop, and then click Yes to confirm.</li> Click Close, and then quit Control Panel.</li> Start Windows Explorer, and then navigate to the location of your Web content, for example, C:\InetPub\wwwroot.

NOTE: Verify that you have a folder between the folders that contain Web content and the rest of the hard disk. This folder acts as a buffer between the Web content and the root of the hard disk.

Not having this &quot;buffer&quot; folder may result in permissions or security problems with your Web site. In the following directory configuration, the InetPub folder acts as the buffer between Web content stored in wwwroot and the hard disk C.

C:\InetPub\wwwroot

</li>  In Windows Explorer, move all nested Web content folders to the buffer folder. All folders containing Web content should now be at the same hierarchy in the directory tree. For example, using the following directory structure <pre class="fixed_text">C: |-InetPub |   |- wwwroot         contains Web site A         | |- Folder1    contains Web site B             | |- Folder2    contains Web site C move Folder1 and Folder2 to the InetPub folder.

NOTE: If you have many nested folders and only one &quot;nesting&quot; Web site folder, it may be easier to move the higher-level folder further downward in the directory tree. For example, using the same example directory structure, create a new folder (named Folder), and then move the Web site A content from wwwroot into the newly created folder. The new folder listing would appear similar to the following: <pre class="fixed_text">C: |-InetPub |   |- wwwroot |       |- Folder      contains Web site A        | |- Folder1    contains Web site B             | |- Folder2    contains Web site C                        </li> In Internet Service Manager, right-click the Web site whose content you moved in step 15 and then click Properties on the shortcut menu that appears.</li> On the Home Directory tab, in the Local Path box, type the new local path to the Web content. For example, C:\InetPub\Folder1. Click Apply, and then click OK.</li> <li>Repeat steps 16 through 17 for every Web site whose content folder you moved.</li> <li>Restart the World Wide Web Publishing service: <ol style="list-style-type: lower-alpha;"> <li>Click Start, point to Settings, and then click Control Panel.</li> <li>In Control Panel, double-click Services.</li> <li>In the Service dialog box, click World Wide Web Publishing Service in the Service list, and then click Start.</li> <li>Click Close, and then quit Control Panel.</li></ol> </li> <li>Restart the virtual servers that you stopped in step 8. To do this, in Internet Service Manager, right-click the Web site that you want and then on the shortcut menu that appears, click Start.</li> <li>Start FrontPage Server Administrator.</li> <li>In the FrontPage Server Administrator dialog box, click Install.</li> <li>In the Configure Server Type dialog box, click Microsoft Internet Information Server in the Server type list, and then click OK.</li> <li>In the Multihosted Servers dialog box, select the virtual servers that you want, and then click OK.</li> <li>In the Confirmation Dialog, click OK.</li> <li>In the Administrator Setup for  dialog box, (where   is the name of the Web site that you selected, in the Name box, type the account name that you want (for example, Administrator ), and then click OK.</li> <li>Repeat steps 25 through 26 for each Web site on which the FrontPage Server Extensions are to be installed.</li> <li>On the Install completed successfully message that appears after FrontPage Server Extensions are installed on all of the virtual servers that you selected, click OK.</li> <li>Click Close to quit FrontPage Server Administrator.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
Nested content occurs when the root directory of one virtual site is located inside (nested in) the content directory of another virtual site.

FrontPage Server Extensions (FPSE) installed on a site attempt to control all content in that site. When the directory structure of one FPSE-based Web is inside that of another, permission conflicts may arise as more than one installation of FPSE is effectively installed on that nested Web site.

Each FPSE-based Web site that has been assigned a unique IP address must have its content directory at the same hierarchical level as other uniquely assigned Web sites.

Consider the following directory structure. <pre class="fixed_text">C: |-InetPub |   |- wwwroot         contains Web site A           | |- Folder1    contains Web site B            | |- Folder2    contains Web site C If you create a Web in Folder1, the content of that Web will be &quot;nested&quot; within a Web that you create in wwwroot.

If, in the above example, you install FrontPage Server Extensions on a Web created in wwwroot, they will attempt control all content within wwwroot including Webs created in Folder1 and Folder2. This may create conflicting permissions with FrontPage Server Extensions installed on Webs whose content is stored in these folders.

The following example directory structure is better suited to multiple Web sites with unique IP addresses: <pre class="fixed_text">C: |-InetPub |   |- wwwroot     contains Web site A       | |- Folder1    contains Web site B        | |- Folder2    contains Web site C In this example, when you create a FPSE-based Web in wwwroot, the server extensions will not conflict with other FPSE-based Webs created in Folder1 or Folder2.

For additional information about troubleshooting FrontPage Server Extensions permission issues, click the article numbers below to view the articles in the Microsoft Knowledge Base:

198431 Users Cannot Author, Permissions Are Set Correctly in FrontPage

183777 FP: Server Extensions Do Not Support Nested Virtual Roots

173307 PRB: Nested Virtual Roots Can Lose Session State

224985 FP98: How to Reset Permissions on Multiple Virtual Servers with FrontPage 98 Server Extensions

224147 How to Reset Permissions Using FrontPage 98 Server Extensions

162144 FP97: Minimum NTFS File Permission Requirements

194475 FP98: Server Extensions Do Not Support Nested Virtual Roots

Additional query words: front page

Keywords: kbprb KB296583

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.