This documentation is archived and is not being maintained.

Unable to access the Web server with Server Extensions when creating a Web application

Visual Studio .NET 2003

The ability to use FrontPage Server Extensions can be affected by many factors. If you are unable to access your application files using server extensions, the cause of the problem can range from accidentally deleting or renaming essential files to accidentally deleting access control lists (ACLs). This can result in several types of error messages.

Note   Personal Web Services on Windows 98 and Windows Millennium Edition do not support remote FrontPage Server Extensions. If you are running one of those operating systems, you will get this error message.

To fix many design-time problems, you can use the Check Server Extensions command, which:

  • Checks read permissions.
  • Checks that Service.cnf and Service.lck are read/write.
  • Updates Postinfo.html and _vti_inf.htm.
  • Verifies that _vti_pvt, _vti_log, and _vti_bin are installed, and that _vti_bin is executable.
  • Determines whether roots or metabase settings are correct and up to date. The metabase is a facility within Internet Information Services (IIS) that stores your IIS settings. It stores settings much the same way as the Windows registry stores system settings.
  • Checks that the IUSR anonymous account does not have write access.
  • Warns you if you are running IIS on a FAT file system, which means that there is no way to secure your Web site.

To check and fix FrontPage Server Extensions

  1. Open the Start menu from the Taskbar and expand the Programs menu.
  2. Expand the Administrative Tools menu and open Internet Services Manager.
  3. In the IIS Console, right-click the server you want to check.
  4. On the shortcut menu, expand All Tasks and select Check Server Extensions.

See Also

Working with Web Projects | Web Access Failed Dialog Box | Troubleshooting Web Projects