Click to Rate and Give Feedback
MSDN
MSDN Library
Visual Studio 2005
Visual Studio
 Error: The web server is not config...

  Switch on low bandwidth view
This page is specific to
Microsoft Visual Studio 2005/.NET Framework 2.0

Other versions are also available for the following:
Visual Studio Debugger
Error: The web server is not configured correctly

This error reads:

The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the debugger may provide further information.

Possible causes of this error include:

  • Trying to debug a .NET web application that was copied to a different machine, manually renamed, or moved.

  • Not having enough IIS connections. (See "Limiting Connections" in the IIS Operations Guide.)

If you are trying to debug an ASP.NET project

  • Check to see that the DEBUG verb is associated with .aspx. See How to: Associate DEBUG Verb with Extension for more information.

  • Check to see that the Web site has been configured as an Application in IIS.

    1. From the Start menu, choose Programs, then Administrative Tools, and click Internet Information Services.

    2. In the Internet Information Services dialog box, click the tree control for your machine, open the Web Sites folder, and find your web site.

    3. Right-click Web Site and choose Properties.

    4. In the Web Site Properties window, select the Directory tab.

    5. Under Application Settings, look for the Remove or Create button.

      If the button says Remove, your website is already configured as an application.

      If the button says Create, click the button to configure your website as an application.

    6. Click OK.

If you are trying to debug an ATL Web application

See Also

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Verify your web.config settings      rlarno   |   Edit   |   Show History

I stumbled on this error using VS2005 SP1. The reason for not being able to debug was the below debug setting in my web.config was set to false , make sure it is set to true .

   <system.web>
<!-- DYNAMIC DEBUG COMPILATION
Set compilation debug="true" to insert debugging symbols (.pdb information)
into the compiled page. Because this creates a larger file that executes
more slowly, you should set this value to true only when debugging and to
false at all other times.
-->
<compilation defaultLanguage="c#" debug="true" />
Tags What's this?: Add a tag
Flag as ContentBug
SSL settings      Luke Breuer   |   Edit   |   Show History
If all else fails, try disabling SSL. It's not optimal, but it worked for me. (I only disabled SSL on an internal-only development server, not the production server.)
Tags What's this?: Add a tag
Flag as ContentBug
verify the project file (ex: abc.csproj)      chaunguyen   |   Edit   |   Show History
verify the project file (ex: abc.csproj)
go to tag <IISUrl>http://localhost/web20</IISUrl> and make sure your url app the same this.
regards
Tags What's this?: Add a tag
Flag as ContentBug
Run aspnet_regiis      Jay Tipton ... kingmaruthu   |   Edit   |   Show History

SYMPTOMS

  • An error box appears with the following message, when running a Web application from within Visual Studio 2005:
    Unable to start debugging on the web server. The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the debugger may provide further information.

    - or -

  • An error Web page appears with the following message, when attempting to browse directly to a Web application:
    Failed to access IIS metabase

CAUSE

This issue started when I began using the .NET Framework 2.0 and Visual Studio 2005, in conjunction with IIS 6. Anytime I installed/updated IIS after the .NET Framework was already installed, I got the previously mentioned errors.

SOLUTION

NOTE: This is written for inexperienced developers, so please bear with the overly simplified description.

  1. Open an instance of the VS Command Prompt (in XP, Start > All Programs > Microsoft Visual Studio 2005 > Visual Studio Tools > Visual Studio 2005 Command Prompt).
  2. Change the location to your current .NET Framework directory by entering cd C:\WINDOWS\Microsoft.NET\Framework\vX.X.xxxxx and pressing <ENTER> (where the x's represent the version of the .NET Framework you have installed).
  3. Type aspnet_regiis -i and press <ENTER>.

The command prompt will show that some work is being done. Once it has completed, the problem should be fixed.

-----------------------------------------------Even the above doesn't work---------------------------------------------------------------------------------------------

what should be done., I use windows server 2003 R2 Standard edition / VS 2005 Team. / Do please help

Tags What's this?: Add a tag
Flag as ContentBug
iisReset      Amir The Ruler   |   Edit   |   Show History
not sure what fixed mine but it didn't take effect until I did an IISReset. so please do IISReset more often!
Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker