Web Access Failed Dialog Box

Visual Basic Reference: Error Messages

The topics in this section cover the various errors you may encounter when accessing or creating Web applications. The Web Access Failed dialog box can appear when you are attempting to access an existing Web application or while creating a new one. The errors are caused by settings in either the remote server or in the Web application itself. Generally, the first issue you may want to consider is your network connection. A simple inspection of your network cords or modem connection may avoid lengthy troubleshooting.

The first paragraph of the Web Access Failed dialog box contains general information about your Web access method and the location of the server you are attempting to access. The second paragraph is the specific error that was returned as the result of your action.

The following is a list of common errors that the server returns when attempting to access network files from a Web project.

Could not find a Web server at <servername>

Could not find a Web server at '<servername>'. Check to make sure that the Web server name is valid and your proxy settings are set correctly. If you are sure that everything is correct, the Web server may be temporarily out of service. For more information, see Unable to create a Web application on a LAN that uses a proxy server and Unable to use <server name> when creating a Web application.

Web server does not appear to have FrontPage Server Extensions

The Web server does not appear to have the FrontPage Server Extensions installed. If the FrontPage Server Extensions are installed, this error may occur because the _vti_bin virtual directory is not marked executable. To correct this problem, run the Internet Service Manager, select the Web server having the problem, and use the Check Server Extensions task. For more information, see Unable to access the Web server with Server Extensions when creating a Web application.

Web server does not appear to have authentication enabled

The Web server does not appear to have any authentication methods enabled. The server asked for user authentication, but did not send a WWW-Authenticate header. For more information, see Windows authentication does not respond properly when creating a Web application.

Unable to validate file path

Unable to validate the file path.

'C:\inetpub\wwwroot\<project name>' matches the URL path 'C:\inetpub\wwwroot\<project name>'. Access is denied.

For more information, see Unable to create Web project, server denies access to URL path.

Unable to create Web project <project name>. Server Error: Cannot create folder "Images"

For more information, see Unable to access the Web Server with Server Extensions when creating a Web application.

Unable to create Web project <project name>

An error occurred accessing your FrontPage Web files. The problem may be because of improperly configured FrontPage Server Extensions on the server. Authors: If authoring against a Web server, contact the Webmaster for this server's site. Webmasters: See the server's system log for more information. For more information, see Unable to Use <Server Name> When Creating a Web Application.

Unable to add <Filepath> to the project

Server error: The folder "WebApplication" is marked executable. You are not allowed to put files into an executable folder on this server. For more information, see Unable to put files in an executable folder.

Unable to use Secure Sockets Layer

There is no server on port 443 at <server name>. You have selected the Connect Using Secure Sockets Layer (SSL) option. This connection problem may indicate that the server does not support SSL communications, or that it uses SSL communications on a different port number. For more information, see Unable to communicate with a server using SSL.

Unable to validate the file path c:\inetpub\wwwroot\<project name>

Unable to create Web project '<project name>'. Unable to validate the file path 'c:\inetpub\wwwroot\<project name>'. For more information, see Unable to validate project path.

Unable to open or create Web projects after converting file system to NTFS

Unable to create Web project '<project name>' Server error: Cannot create folder "images". For more information, see Unable to open or create Web projects after converting to NTFS.

HTTP Error 404: Unable to create Web project <project name>

Unable to create Web project 'WebApplication'. The file path '<file path>' does not correspond to the URL 'http//localhost/<project name>'. The two need to map to the same server location. HTTP Error 404: Object Not Found. For more information, see Unable to Locate Object on Web Server.

HTTP Error 502: Proxy Error

HTTP Error 502: Proxy Error (The Uniform Resource Locator (URL) does not use a recognized protocol. Either the protocol is not supported or the request was not typed correctly. Confirm that a valid protocol is in use (for example, HTTP for a Web request.) For more information, see Unable to create a Web application on a LAN that uses a proxy server

The network path was not found

Unable to create Web project <project name>. Unable to create the Web location '\\<server name>\wwwroot$\<project name'. The network path was not found. For more information, see Unable to validate project path.

The UNC share does not exist or you do not have access

Unable to create Web project '<project name>'. The UNC share '\\<server name\wwwroot$\<project name>' does not exist or you do not have access. For more information, see Unable to create Web project, server denies access to URL path.

Unable to create Web project...Access is denied

Unable to create Web project '<project name>". Unable to create the Web location 'c:\inetpub\wwwroot$\<project name>'. Access is denied. For more information, see Access denied to Web server.

You are not authorized to perform the current operation

Unable to open Web project '<project name>'. You are not authorized to perform the current action. For more information, see Access denied to Web server.

Unable to open Web project '<projectname>'. You cannot open the Web '<projectname>' with file share authoring access. This is a FrontPage Web which is under source control."

This error occurs when a user with their system configured to use file share as the access method tries to open a source controlled Web project that was set up using FrontPage as its access method. The access method for a Web project is frozen at the time you add it to source control. After that point, everyone must open it using the same method.

To correct this error

Do one of the following:
- Click FrontPage in this dialog box.
  - or -
- Change your file-access method to FrontPage in the Access Mode dialog box. You can access that box by choosing Options from the Tools menu, selecting the Projects folder, and then selecting the Web Settings property page. For more information, see Web Access Methods.