"Unable to start debugging on the web server. The IIS worker process for the launched URL is not currently running"

Hi All,
I'm at the end of my tether, I have tried everything I can think of. File permissions, visual studio project settings but nothing I do allows me to debug from visual studio by hitting F5.

I can debug if I attach to the w3wp processes running, however this is truely a pain and I really miss hitting the F5 key.


Windows Authentication is enabled through the IIS console

Hitting F5 causes the above message to appear in a dialog and the Security Event Log has an entry "An account failed to log on." with the failure information "Status 0xc000006d, Sub Status: 0x0"

This is very likely to be a simple thing I have missed out, Can anyone offer some pointers for things I could try?

Thanks in advance,
David

(ping)

Please, can someone help?

Have you installed the SP1 package to VS 2008. If not try installing it and check to see if your problem has been corrected, if not check back and repost. Good luck!

 DKB

Hi, thanks for the response.

Yes, VS 2008 SP1 (and framework 3.5sp1 although that is unrelated) is installed. Installing this did not resolve the issue. I think that this is something to do with host headers, let me explain further.

The website in question has been configured under a custom host header name (such as dev.site.com) and the computer has an entry for that hostname in the hosts file, with the correct IP mappings etc. The web project has been configured to use Local IIS and the URL http://dev.site.com. The reason I think that there may be an issue with type of setup (which works elsewhere - just not on this PC) is that visual studio WILL debug a web project when it has been configured to use Local IIS and a URL akin to http://localhost:9999/.

Does this set off any alarms as to other aspects I could look into?

Thanks,

DC

David,

You can resolve this issue by changing your IIS 7 website bindings from a specific IP address (i.e., the IP in your hosts file) to a wildcard (all unbound addresses). In IIS under the SItes node, select your site --> Under the Actions section to the right, select the Bindings link. Your observations regarding localhost sent me down the right path to get this resolved. Thanks!

Regards,
Steve

This is a bug in SP1. And simply changing the binding to *, while it will work for one site, does not address the bigger problem. For example, lets say I have a single code base that is utilized for multiple web sites. So I set up 3 Sites in IIS 7 and I place 3 IPs on my network adapter and put 3 entries into my host file to mimic dns.

So the set up looks something like this: 

IIS Site1 - Bindings 10.1.1.1 http and https. I create a cert with self ssl for dev.Site1.com and the host entry is - 10.1.1.1 dev.Site1.com

IIS Site2 - Bindings 10.1.1.2 http and https. I create a cert with self ssl for dev.Site2.com and the host entry is - 10.1.1.2 dev.Site2.com

IIS Site3 - Bindings 10.1.1.3 http and https. I create a cert with self ssl for dev.Site3.com and the host entry is - 10.1.1.3 dev.Site3.com

Prior to SP1 this worked great. All I had to do in my project start options was switch between http://dev.Site1.com, http://dev.Site2.com, http://dev.Site3.com, as the custom server's base URL and I could debug the specific site application and site specific content.

However, now it seems I have to not only switch sites in my start options but also go enable disable the currently running site and enable the site I want to debug. This is because you cannot have two sites running with * as the bindings that use SSL. SSL requires static IPs! Is there a better way to do this now? Why did this change in SP1?