FP2000: _vti_bin Virtual Directory Is Not Created When You Configure Server Extensions (276520)



The information in this article applies to:

  • Microsoft FrontPage 2000

This article was previously published under Q276520

SYMPTOMS

When you configure the FrontPage 2000 Server Extensions for a new virtual server, the Configuration Wizard fails to create the _vti_bin virtual directory. When you then try to connect to the root web, you receive the following error message:
The folder 'http://servername' isn't accessible. The folder may be located on an unavailable volume or protected with a password.

For details see c:\TEMP\wecerr.txt.
The contents of the Wecerr.txt file is
HTTP 405 Method not allowed

RESOLUTION

To resolve this issue, follow these steps:
  1. Click Start and then click Run.
  2. In the Open box, type mmc.exe.
  3. On the Console menu, click Add/Remove Snap-in.
  4. Click Add.
  5. Select Internet Information Services, click Add, and then click Close.
  6. Click OK.
  7. On the Console menu, click Save As, and save the file as the following:

    C:\WINNT\system32\inetsrv\iis.msc

    NOTE: This path is the default path for Microsoft Internet Information Services installations and may need to be modified, depending on the configuration of your server.
The next time that you attempt to configure the FrontPage Server Extensions, the _vti_bin directory will be created.

WORKAROUND

To work around this issue, use the server extensions command-line utility. Type the following:

"c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\40\bin\fpsrvadm.exe" -o install -p lm/w3svc/# -t msiis

where # is the meta-instance of the Web site on which you want to install extensions.

To determine the meta-instance number, follow these steps:
  1. Start the Microsoft Management Console for Internet Information Services.
  2. Right-click the name of the virtual server to which you want to install, and then click Properties.
  3. At the bottom of the property sheet, in the logging settings, click Properties, and note the name of the log file. The name of the log file is similar to "W3SVC6\exyymmdd.log"; in this case, the "6" in "W3SVC6" is the meta-instance.

Modification Type:MajorLast Reviewed:12/15/2000
Keywords:kbprb KB276520