 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / General / February 2008Unable to Debug because Integrated Windows Authentication is not Enabled
I've been having a problem debugging an ASP.NET 1.1 application on an existing Windows XP/Visual Studio 2003 workstation that I've inherited from somebody else. The application builds fine, but when I try to debug, it gives me the message: Error When Trying to Run Project: Unable to Start Debugging on the Web Server. Debugging failed because integrated Windows authentication is not enabled. Now, the obvious solution for this of course is to check the "Enable Integrated Windows Authentication" box in IIS under Anonymous Access and Authentication Control in the Directory Security Tab. The option is checked, yet the error message is still appearing. I've checked it for both the website itself and the virtual directory. I think this may be project-related, it is an MCMS application, and when I try to debug small test applications, they debug just fine, only this particular large project gives me the debugging error. Any ideas of what can cause this error, besides that checkbox being left empty? Are you sure that it's (Integrated Windows Authentication) checked for all folders/subfolders.... the easiest way is to check it at the root level and IIS management will ask if you want it to apply to subfolders... If it's checked already uncheck it hit apply then check it and hit apply. George. > I've been having a problem debugging an ASP.NET 1.1 application on an > existing Windows XP/Visual Studio 2003 workstation that I've inherited [quoted text clipped - 14 lines] > ideas of what can cause this error, besides that checkbox being left > empty? Thanks for the quick reply. I've unchecked the box, applied the changes to all subfolders, then checked it again and applied to all subfolders, and the error is still appearing: Error When Trying to Run Project:Unable to Start Debugging on the Web Server. Debugging failed because integrated Windows authentication is not enabled. Thank you for the suggestion though. Any other ideas? > Are you sure that it's (Integrated Windows Authentication) checked for all > folders/subfolders.... [quoted text clipped - 26 lines] > > ideas of what can cause this error, besides that checkbox being left > > empty? Well, try to uncheck Anonymous so only Integrated is checked there. Other than that try to Google this error cause I am out of suggestions.... PS: Is you project running without debugging? If you simply open it in the browser? George. > Thanks for the quick reply. I've unchecked the box, applied the > changes to all subfolders, then checked it again and applied to all [quoted text clipped - 36 lines] >> > ideas of what can cause this error, besides that checkbox being left >> > empty? Another suggestion.... Make sure that you have ASP.NET 1.1 version set for this application and not 2.0 It's in the IIS Management console (additional tab and it's there only if you have ASP.NET 2.0 installed) George. > Thanks for the quick reply. I've unchecked the box, applied the > changes to all subfolders, then checked it again and applied to all [quoted text clipped - 36 lines] >> > ideas of what can cause this error, besides that checkbox being left >> > empty? Thanks again for suggestions, but it is set to the correct ASP.NET version. The project runs perfectly well if you simply open it in the browser. > Another suggestion.... > Make sure that you have ASP.NET 1.1 version set for this application and not [quoted text clipped - 49 lines] > >> > ideas of what can cause this error, besides that checkbox being left > >> > empty? Open up the .csproj / .vbproj file in Notepad.exe and look at the url that is specified for the project. It may be wrong. -- Peter Site: http://www.eggheadcafe.com UnBlog: http://petesbloggerama.blogspot.com MetaFinder: http://www.blogmetafinder.com > Thanks again for suggestions, but it is set to the correct ASP.NET > version. The project runs perfectly well if you simply open it in the [quoted text clipped - 53 lines] > > >> > ideas of what can cause this error, besides that checkbox being left > > >> > empty? Another good idea, but the information in the CSPROJ file looks correct. I appreciate all the suggestions though, anybody else have any ideas? On Feb 12, 8:15 pm, Peter Bromberg [C# MVP] <pbromb...@yahoo.NoSpamMaam.com> wrote: > Open up the .csproj / .vbproj file in Notepad.exe and look at the url that > is specified for the project. It may be wrong. [quoted text clipped - 61 lines] > > > >> > ideas of what can cause this error, besides that checkbox being left > > > >> > empty? if you have an impersonation account in the web config, it must be a local admin and added to the debuggers users group. you can also try disabling anonymous. -- bruce (sqlwork.com) > I've been having a problem debugging an ASP.NET 1.1 application on an > existing Windows XP/Visual Studio 2003 workstation that I've inherited [quoted text clipped - 14 lines] > ideas of what can cause this error, besides that checkbox being left > empty? Haha I wish one of these times I could reply with better news. The web.config doesn't use impersonation, the user is a member of the debugger's group, and the problem persists whether or not anonymous access is checked. You can see why this is such an annoying problem. I hope the answer doesn't turn out to be anything too ridiculous. Any other ideas would be greatly appreciated. On Feb 13, 12:12 pm, bruce barker <brucebar...@discussions.microsoft.com> wrote: > if you have an impersonation account in the web config, it must be a local > admin and added to the debuggers users group. [quoted text clipped - 22 lines] > > ideas of what can cause this error, besides that checkbox being left > > empty? Haha I wish one of these times I could reply with better news. The web.config doesn't use impersonation, the user is a member of the debugger's group, and the problem persists whether or not anonymous access is checked. You can see why this is such an annoying problem. I hope the answer doesn't turn out to be anything too ridiculous. Any other ideas would be greatly appreciated. On Feb 13, 12:12 pm, bruce barker <brucebar...@discussions.microsoft.com> wrote: > if you have an impersonation account in the web config, it must be a local > admin and added to the debuggers users group. [quoted text clipped - 22 lines] > > ideas of what can cause this error, besides that checkbox being left > > empty? Haha I wish one of these times I could reply with better news. The web.config doesn't use impersonation, the user is a member of the debugger's group, and the problem persists whether or not anonymous access is checked. You can see why this is such an annoying problem. I hope the answer doesn't turn out to be anything too ridiculous. Any other ideas would be greatly appreciated. On Feb 13, 12:12 pm, bruce barker <brucebar...@discussions.microsoft.com> wrote: > if you have an impersonation account in the web config, it must be a local > admin and added to the debuggers users group. [quoted text clipped - 22 lines] > > ideas of what can cause this error, besides that checkbox being left > > empty? Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.