Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled

"Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled" error occurs when you try try to debug the application in Microsoft Visual Studio 2005 in Windows Vista Home Basic or in Windows Vista Home Premium using Internet Information Services (IIS) 7.0.

This problem occurs because Windows Vista Home Basic and Windows Vista Home Premium do not contain the Windows Authentication module for IIS. When the client tries to automatically attach the debugger in an ASP.NET 2.0 application, the client sends a HTTP request that contains the DEBUG verb. This HTTP request is used to verify that the process of the application is running and to select the correct process to attach. This HTTP request must be authenticated by using Windows Authentication. However, Windows Vista Home Basic and Windows Vista Home Premium do not contain the Windows Authentication module for IIS. Therefore, the problem occurs.

A supported hotfix is available from Microsoft. Apply this hotfix only to systems that are experiencing this specific problem.

To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:

http://code.msdn.microsoft.com/KB937523

You must have Visual Studio 2005 Service Pack 1 (SP1) installed to apply this hotfix.

Could not create Windows user token from the credentials specified in the config file

Error: "Could not create Windows user token from the credentials specified in the config file. Error from the operating system 'Logon failure: unknown user... "

This error usually is encountered when either the username / password is not valid for the selected user OR the selected user does not have necessary privilege.

You can add the privileges by following the below steps:

Run - Control Panel, Administrative Tools, Local Security Policy

Choose - Local Policies, User Rights Assignment from the tree

"Act as part of OS" should be the second entry on the right hand pane

Error reading configuration information from the registry

You will encounter this error if you are trying to read from the registry. This error specifies that some thing is wrong with the process account when reading the identity information from the registry.

Try the below steps to resolve the issue:

1. Open Regedt32.exe
2. Navigate to HKLM\SOFTWARE\SECURE_APP\identity (Replace SECURE_APP with the app name that you have entered from the aspnet_setreg.exe
3. Right click on key identity and select permissions



4. On the add permissions, click ADD and enter "NETWORK SERVICE"






5. Select Read Permission
6. If you are using Windows 2000 / IIS 5, you will need to add permission to MACHINE\ASPNET
7. This should resolve the access error.

ASP.net Error Both DataSource and DataSourceID are defined on dropdownlist

This is a very interesting Error. I had tried to find the solution using step by step approach. (Sounds funny for a user using Visual Studio.net)

Anyway if I create a control and bind it to a datasource from code behind, every thing is fine. The moment I rename the control and try the code after making necessary changes in code behind, all hell breaks loose. I get the error "Both DataSource and DataSourceID are defined on dropdownlist"


You should just delete the control, comment the code behind code, compile and then try putting the control again. This should work. ASP.net has made me lazy hence I do not want to spend my time looking for the reference causing this error.

"The page cannot be found" Error With ASP.NET On Windows Server 2003?

When you have installed ASP.NET on Windows Server 2003, you may receive the following 404 - Page Not Found error:

The normal html pages can be accessed normally but the aspx pages will give this error. Visual studio.net 2005 has inbuilt server hence you would normally not face this issue since you would not really be using IIS. But in case you deploy the application in IIS and try accessing the application using the localhost or 127.0.0.1, you are bound to find this error.

This error is caused as the IIS 6 disallows the ASP.NET 2.0 Web Service Extension. To fix this, follow these steps:

Open up the Internet Information Services (IIS) Manager (which you find under Administrative Tools)

Expand your server

Select Web Service Extensions

In the right hand pane, click ASP.NET v2.0.50727 (or a later version number) and then click the Allow button.