How To Troubleshoot Connectivity Issues in Visual InterDev 6.0 (272289)

MORE INFORMATION

Prior to Visual Studio 6.0 SP4, if the Web server specified in step 1 of the Web Project Wizard in Visual InterDev cannot be contacted, you may receive the following error message: Visual Studio 6.0 SP4 installs a new version of the Web Project Wizard for Visual InterDev. This new version provides more detailed error messages. These messages are presented below, along with the cause and resolution for each error.

1. 'servername' is not a valid host name or IP address.(Error code = 80004005)
   Your DNS server does not recognize the server name/IP address.
   
   Make sure that the spelling is correct, and that you can browse to the server name/IP address that you provided. To do this, open a Web browser, and in the Address bar, type http://servername or http://ipaddress.
   
   You can also use the TCPTest utility, which is installed with the FrontPage Server Extensions 2000, to check basic WinSock32 functionality. This utility is on your computer at Program Files\Common Files\Microsoft Shared\web server extensions\40\bin\tcptest.exe.
2. Error from proxy.(Error code = 80070005)
   The proxy settings are not set up correctly.
   
   To correct this, perform the following steps:
   1. In Visual InterDev, click Tools, and then click Options.
   2. In the Options dialog box, expand Projects/web proxy settings.
   3. Click to clear the "Use system settings" check box, and then click to select the "Do not use proxy settings for local (intranet) addresses" check box.
   4. Click OK, and then connect to your Web server again.
3. There is no server on port 80 at 'servername'.(Error code = 80004005)
   The Web server is not running. To test the basic Web server functionality, browse to a test HTML and ASP page.
   
   If the pages are not displayed correctly, troubleshoot the Microsoft Internet Information Server (IIS) or Microsoft Personal Web Server installation.
4. Server name cannot contain any protocol information. Please specify only server name.
   You entered http://servername or https://servername instead of servername.
   
   Delete http:// or https:// and enter only the server name in the Address bar.
5. Server Error or Method not allowed(Error code = 80070005)
   Your Web server does not have FrontPage Server Extensions installed, or the server extensions are not configured correctly.
   1. Verify that the FrontPage Server Extensions are installed.
      
      Browse to http://servername/_vti_bin/shtml.dll. You should see one of the following error messages.
      
      FrontPage 2000 Server Extensions:
      Cannot run the FrontPage Server Extensions' Smart HTML interpreter on this non-HTML page: ""
      -or-
      
      FrontPage 98 Server Extensions:
      FrontPage Error. User: please report details to this site's webmaster. Webmaster: please see the server's application event log for more details.
      If you do not receive one of these messages, the FrontPage Server Extensions have not been installed.
      
      You can download the latest version of the FrontPage Server Extensions from the following Microsoft Web site:

      http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservext/html/fpse02win.asp

   2. Verify the version of the FrontPage Server Extensions.
      
      Browse to http://servername/_vti_inf.html. You should see a page with the heading "FrontPage Configuration Information." View the source code of this page. The version of the FrontPage Server Extensions appears after FPVersion=.
      
      It is recommended that you use the FrontPage Server Extensions version 4.0.2.2717 or later.
      
      You can download the latest version of the FrontPage Server Extensions from the following Microsoft Web site:

      http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservext/html/fpse02win.asp

   3. Check that FrontPage Server Extensions are installed properly:

      FrontPage 2000 Server Extensions

      Open Internet Service Manager, right-click Default Web Site (or the appropriate Web site), and then select All Tasks.
      
      If you see the option Configure Server Extensions, the Web site does not have the server extensions enabled. Choose this option to start a wizard that will help you to enable the server extensions.
      
      If you see the option Check Server Extensions, the Web site has the server extensions installed. Choose this option to start a diagnostic program that analyzes the Web site and fixes common issues.
      
      If you do not see an All Tasks item when you right-click the Web site, the FrontPage 2000 server extensions either have not been installed on the computer, or the server extensions' snap-in to the Microsoft Management Console (MMC) was not enabled during setup.
      
      To enable the server extensions' snap-in, go to the Microsoft Internet Information Services (IIS) Manager, and then click Console.
      
      NOTE: If your computer is running Microsoft Windows 2000, close the IIS Manager, right-click the Internet Services Manager icon in the Administrators group, and then select Author to enable the Console menu. Click Add/Remove Snap-In menu item. On the Extensions tab, make sure that FrontPage Server Extensions box is checked. You should now be able to both configure and check the FrontPage Server Extensions.
      
      

      FrontPage 98 Extensions

      To check the FrontPage 98 Server Extensions:
      1. Click Start, point to Programs, point to Windows NT 4.0 Option Pack, point to Microsoft Internet Information Server, and then click FrontPage Server Administrator.
      2. Click Check and Fix.
   For all Knowledge Base articles on Visual InterDev and FrontPage Server Extensions, search on the keywords kbFrontPage and kbServer and kbVisID600.
   
   
6. The web server does not appear to have any authentication methods enabled. The server has asked for user authentication, but did not send a WWW-Authenticate header.(Error code = 80004005)
   Your Web server does not have any authentication methods enabled.
   
   Open your Internet Service Manager (MMC), right-click Default Web Site (or the appropriate Web site), and select Properties. Select the Directory Security tab, and then click the Edit button in Anonymous access and authentication control. In the Authentication methods dialog box, make sure that either the Basic Authentication or Windows Integrated authentication check box is selected.
   
   If Anonymous access is already selected and you still receive this error message, click the Edit button in the Authentication methods dialog box to bring up the Anonymous user account information. Verify that the user name specified is valid (by default this should be IUSR_machinename).
7. Unable to complete transaction - the server requested authentication information (userid/password) using an authentication scheme (digest) that is unsupported by FrontPage.(Error code = 80004005)
   Your Web server is only using digest authentication, but does not fulfill all the requirements to be able to use digest authentication. See item 6 in this article for information on how to change authentication methods.For additional information on how to set up digest authentication for IIS 5.0, click the article number below to view the article in the Microsoft Knowledge Base:

   222028 Setting Up Digest Authentication for Use with Internet Information Services 5.0

8. Proxy Error ( Bad or unassigned address )(Error code = 80070005)
   The IP address that you provided as the server name is not a valid IP address. Be sure that you entered the IP address correctly, and that it is a valid IP address. To do this, type ping ipaddress from a command line.
9. Unable to connect to a server at 'servername' on port 443 (socket code 13101)(Error code = 80004005)
   The Connect using Secure Sockets Layer check box in step 1 of the Web Project Wizard is checked, but your Web server does not have a properly configured Secure Sockets Layer (SSL) certificate.
   
   Click to clear the check box and try connecting again, or verify that SSL is properly set up and configured on the Web site.
   
   Visual InterDev can connect to the Web server using SSL, but it is limited to 40-bit encryption (128-bit encryption is not supported). If the Web server is set to require 128-bit encryption, the connection fails. Also, Visual InterDev recognizes server certificates from the following certificate authorities only:
   
   - Verisign-Secure Server Certification Authority
   - RSA Data Security, Inc.
   - AT&T-Certificate Services
   - AT&T-Directory Services For additional information, see the following article in the Microsoft Knowledge Base:

   238662 INFO: Using Visual InterDev and Secure Sockets Layer

10. An unexpected error occurred accessing your FrontPage web files. Authors - if authoring against a web server, please contact the webmaster for this server's site. WebMasters - please see the server's system log for more details.(Error code = 80004005)
    The Connect using Secure Sockets Layer check box in step 1 of the Web Project Wizard is selected, but your Web server does not have a properly configured Secure Sockets Layer (SSL) certificate.
    
    This is the same problem as in item 9 of this article, but this error message appears when you supply an IP address instead of a server name.
    
    Click to clear the check box and try connecting again, or verify that SSL is properly set up and configured on the Web site.
    
    Although the error message states that a system log will be generated on the Web server computer, no system log is generated for this particular problem.
    
    NOTE: The following error messages look similar to the first error message listed in this item (above), but the resolution is different:
    An unexpected error occurred accessing your FrontPage web files. Authors - if authoring against a web server, please contact the webmaster for this server's site. WebMasters - please see the server's system log for more details.

    -or-

    An error occurred accessing your FrontPage web files. Authors - if authoring against a web server, please contact the webmaster for this server's site. WebMasters - please see the server's system log for more details.
    The resolution to these errors is found in the following Microsoft Knowledge Base article:

    260159 Errors When Viewing Permissions in FrontPage

11. Web Extender Client interfaces not correctly installed.(Error code = 80040154)
    A dynamic-link library (DLL) that is used by Visual InterDev may have become unregistered.
    
    Click Start, click Run, and then type the following command:

    Regsvr32 C:\YourWindowsFolder\System\FP30wec.dll

    You should see a confirmation that the file was registered successfully.
    
    Start Visual InterDev and create a project. For additional information, see the following article in the Microsoft Knowledge Base:

    218167 PRB: Visual InterDev Is Not Installed Correctly on This Computer

12. Access Forbidden (Error Code = 80070005)
    You may have moved the default Web site to a different folder, and the permissions are not set. Open Internet Service Manager and right-click Default Web Site, and click All Tasks/Permission Wizard. Follow the steps in the Permission Wizard to set the permissions.
    
    NOTE: This will uncheck Integrated security for the Default Web Site. You may receive the following error when you browse to a page on the Web server or start a new project in Visual InterDev:
    "The web server does not appear to have any authentication methods enabled. The server has asked for user authentication, but did not send a WWW-Authenticate header.(Error code = 80004005)"
    See item 6 in this article for the resolution.
13. Server error. You must use a secure connection SSL to author against this server. Error code: 80004005.
    This error occurs because IIS is requiring SSL for authors. To change this, follow these steps:
    1. In the Internet Services Manager, right-click Computer Name.
    2. Click Properties, and then click the Server Extensions tab.
    3. Click to clear the check box for Require SSL for Authoring. Also, verify this setting at the Default Web Site level.