I began today by starting a different post about publishing an app to localhost. Things soon went sideways. That post will have to wait while I peel back this onion:
When I open up IIS, I can see that the Default Site and the DefaultAppPool are stopped. No problem, let’s start them.
You knew it wasn’t going to be that simple, right? From an admin command prompt:
|
1 2 3 4 5 6 7 8 9 |
C:\WINDOWS\system32>net start was The Windows Process Activation Service service is starting. The Windows Process Activation Service service could not be started. A system error has occurred. System error 2 has occurred. The system cannot find the file specified. |
Now, WAS and IIS are both installed, so I follow the recommendation from iis.net to go ahead and reinstall them, but save yourself the restart. That didn’t do it.
I’m not eager to Regedit based on a StackOverflow answer, but it’s simply removing a file and Scott Hanselman’s foray into PerfMon lead me to several errors, but they did not get me closer to a resolution. I’ve reinstalled WAS once, so I deleted NanoSetup.
|
1 2 3 |
C:\WINDOWS\system32>net start was The Windows Process Activation Service service is starting. The Windows Process Activation Service service was started successfully. |
Now the App Pool can be started, but we’re missing one last step to turn on the DefaultSite.
One more Admin Command Prompt later and we’re there.
|
1 2 3 |
C:\WINDOWS\system32>net start w3svc The World Wide Web Publishing Service service is starting. The World Wide Web Publishing Service service was started successfully. |
Now, we can navigate to localhost in the browser.
