You may receive an error message after you install FrontPage Server Extensions on a Web site (296596)



The information in this article applies to:

  • Microsoft FrontPage 2000
  • FrontPage 2000 Server Extensions from Microsoft

This article was previously published under Q296596

For a Microsoft FrontPage 98 version of this article, see 296583.

SYMPTOMS

After you install FrontPage Server Extensions on a Web, you experience some or all of the following symptoms:
  • In Microsoft FrontPage, you are unable to open 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 see Access violation events with an Event ID of 80002.

CAUSE

Some or all of these issues can occur when you install FrontPage Server Extensions on a Web, the root folder of which is nested in the content folder of another Web (nested content).

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

For each Web site that has a unique IP address, you need to place its content folder at the same hierarchical level as other uniquely assigned Web sites.

RESOLUTION

To resolve this issue, move all Web content folders to the same level in the directory structure. To do this, follow these steps.

NOTE: The following steps assume that the following Microsoft Windows software is installed on your computer:
  • Microsoft Windows NT 4.0 Server, Service Pack 6, with Microsoft Windows NT Option Pack and Microsoft Internet Information Server 4.0
  • Microsoft Windows 2000 Server or Microsoft Windows 2000 Professional with Microsoft Internet Information Services 5.0
  • Microsoft Windows XP Professional with Microsoft Internet Information Services 5.1
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. Log on to the Web server as administrator.
  2. Start Internet Services Manager. To do this, follow the steps for your version of IIS:
    • For IIS 5.1:
      1. Open Control Panel.
      2. Double-click Administrative Tools.
      3. Double-click Internet Information Services.
  3. For IIS 5.0:
    1. On the Windows Start menu, point to Programs, and then click Administrative Tools.
    2. Click Internet Services Manager.
  4. For IIS 4.0:
    1. On the Windows Start menu, point to Programs, and then click Windows NT 4.0 Option Pack.
    2. Click Microsoft Internet Information Server.
    3. Click Internet Service Manager.
  5. Remove the server extensions from your Web sites. To do this, follow these steps:
    1. Right-click a Web site (for example, right-click Default Web Site), point to Task on the shortcut menu, and then click Remove Server Extensions.
    2. In the Remove Server Extensions dialog box that appears, click to select the Preserve Web meta-information for a later upgrade or reinstall of the FrontPage Server Extensions check box, if necessary, and then click OK.
    3. Right-click the same Web site (for example, right-click Default Web Site), and then click Stop on the shortcut menu.
    4. Repeat steps a through c for each Web site on which FrontPage Server Extensions are installed.
  6. Stop the World Wide Web Publishing Service. To do this, follow these steps:
    1. Click Start, point to Settings, and then click Control Panel.
    2. In Control Panel, double-click Services.
    3. In the Service dialog box, click World Wide Web Publishing Service in the Service list, click Stop, and then click Yes to confirm that you want to stop this service.
    4. Click Close.
  7. Move the content folders to remove the nested configuration. To do this, follow these steps:
    1. In Windows Explorer, locate your Web content. For example, if you used the default path for IIS Web content, locate the following folder:

      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 folder of the hard disk. If you do not have this buffer folder, permissions or security problems with your Web site can occur. By default, the C:\InetPub folder acts as the buffer between Web content stored in Wwwroot and the root folder of your C: drive.
    2. In Windows Explorer, move all nested Web content folders to the "buffer" folder. For example, if you have the following directory structure

      C:
       |-InetPub
          |
          |- Wwwroot         (contains the Default Web Site)
              |
              |- FolderA     (contains Web site A)
              |
              |- FolderB     (contains Web site B)
      								

      then you would move FolderA and FolderB to the C:\InetPub folder. When this is completed, all folders containing Web content will be at the same level in the directory structure.
    3. Repeat the steps a through b for each Web site that has nested content folders.

      NOTE: If you have many nested folders, it is easier to move the higher-level folder further downward in the directory structure. For example, you can create a new folder under the Wwwroot folder and then move the Default Web Site content from Wwwroot into the newly created folder. The new folder listing should look similar to this:

      C:
       |-InetPub
          |
          |- Wwwroot
              |
              |- NewFolder   (this folder now contains the Default Web Site)
              |
              |- FolderA     (contains Web site A)
              |
              |- FolderB     (contains Web site B)
      								

      Although this approach can reduce the number of folders that you need to move, it does not take into account any content folders under Wwwroot that are not nested Web site content folders. Therefore, you need to move these folders also.
  8. Point your Web sites to the new content locations. To do this, follow these steps:
    1. In Internet Service Manager, right-click the Web site whose content you moved, and then click Properties on the shortcut menu.
    2. On the Home Directory tab, click Browse to locate the new path for the Web content. Or, type the path in the Local Path box. For example, type C:\InetPub\FolderA.
    3. Click Apply to accept the changes.
    4. Click OK to close the Web site's Properties dialog box.
    5. Repeat steps a through d on each Web site where you moved the content folder.
  9. Restart the World Wide Web Publishing service. To do this, follow these steps:
    1. Click Start, point to Settings, and then click Control Panel.
    2. In Control Panel, double-click Services.
    3. In the Service dialog box, click World Wide Web Publishing Service in the Service list, and then click Start.
    4. Click Close to close Control Panel.
  10. Restart each virtual server that you stopped. To do this, right-click the Web site in Internet Service Manager and then click Start on the shortcut menu.
  11. Reinstall FrontPage Server Extensions on each virtual server on which you want to allow FrontPage authoring. To do this, follow these steps:
    1. In Internet Service Manager, right-click the Web site that you want, point to Task on the shortcut menu, and then click Configure Server Extensions.
    2. In the Server Extensions Configuration Wizard, click Next.
    3. Click OK.
    4. Repeat steps a through c to configure FrontPage Server Extensions on each additional Web site.

MORE INFORMATION

Nested content occurs when the root folder of one virtual site is located (nested) inside the content folder of another virtual site.

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

Consider the following directory structure:

C:
 |-InetPub
    |
    |- Wwwroot         (contains the Default Web Site)
        |
        |- FolderA     (contains Web site A)
        |
        |- FolderB     (contains Web site B)
					

If you create a Web in FolderA, the content of that Web is "nested" within the Default Web Site in Wwwroot. If you then install FrontPage Server Extensions on a Web created in Wwwroot, FrontPage Server Extensions attempt to control all content in Wwwroot, including Webs created in FolderA and FolderB. This can result in permissions that conflict 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:

C:             
 |-InetPub
    |
    |- Wwwroot     (contains the Default Web Site)
    |
    |- FolderA     (contains Web site A)
    |
    |- FolderB     (contains Web site B)
					

In this example, when you create a FrontPage Server Extensions-based Web in Wwwroot, the server extensions do not conflict with other FrontPage Server Extensions-based Webs created in FolderA or FolderB.

REFERENCES

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

201522 FP: Error Message: Unable to Create Web for the URL "/"

194475 FP98: Server Extensions Do Not Support Nested Virtual Roots

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


Modification Type:MinorLast Reviewed:1/7/2006
Keywords:kberrmsg kbsetup kbEventLog kbbrowsing kbWebServer kbopenfile kbprb KB296596