Unable to start debugging on the web server

Question

if i careate new website with filesystem,anything is ok,but when i create new website with iis,When I attempt to run and debug I get the error:

Unable to start debugging on the web server. The type initializer for 'System.Net.DigestClinet' threw an exception.

what can i do?

Answer 1

Hi,

First thing to check is whether IIS is configure to use the correct version of ASP.NET. Assuming you are using VS2005 and ASP.NET 2.0, go to the Default Web Site's Properties under IIS Manager and on the ASP.NET page please make sure that the 2.0 version is selected (resetting IIS is needed after you change this setting).

If you are already using the correct version, maybe the web.config file associated w/ your project contains an error (or maybe there is a web.config file in your wwwroot directory that takes precedence). Look for a section like this:

<configuration>
  <system.net>
    <authenticationModules>
      <add type="System.Net.DigestClient" />
    </authenticationModules>
  </system.net>
</configuration>

and see if something looks odd (like some incorrect values for Version for the System.Net.DigestClient authentication module.

If your web.config does not contain such a section and there is not web.config that contains it in any parent v-dir, check the machine.config file under <system drive>:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG.

Hope this helps,

Monica Boris

Visual Studio Debugger Team

Answer 2

There may be a project with the name of "Security", change the name and try it again. 

Answer 3

 

I had exactly the problem like yours. Searching over internet gives 2 main reasons :

+ A Security.dll Assembly, which is conflict with system security.dll

+ Upgrade from 2003 to 2005.

 

However those are not my case, because I just create a website from scratch in VS2005.

 

I uninstall IIS completely. Reinstall IIS.

launch cmd window and run :

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiss -u

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiss -i

 

Those steps resolved my debugging problem