We just got a new Windows 2008 Server setup and are installing our ASP.NET application running under IIS 7.0.
The install seems to work fine including our calls using AppCMD to change default settings. E.g. "AppCmd.exe set apppool /apppool.name:MyAppPool /processModel.identityType:NetworkService /enable32BitAppOnWin64:true /recycling.periodicRestart.time:00:00:00 /processModel.idleTimeout:00:00:00"
However, we have some code at the end of our install script (a Power Shell script) that simply makes sure the AppPool and Site are started.
AppCmd.exe start apppool /apppool.name:MyAppPool
Trying to start the apppool gives us the error "ERROR ( message:The WAS service is not available - try starting the service first. )"
We can start the apppool from the Server Manager UI just fine. I've also checked and the WAS service (i.e. Windows Process Activation Service) is running.
We see a similar error when trying to start the site.
AppCmd.exe start site /site.name:MySite
This gives us the error "ERROR ( message:The W3SVC service is not available - try starting the service first. )"
As with the pool, we can start the site from the Server Manager UI just fine. I've also checked and the W3SVC service (i.e. World Wide Web Publishing Service) is running.
Also, when we list out the apppools or site, the state is Uknown. We're thinking this is also related.
APPPOOL "DefaultAppPool" (MgdVersion:v2.0,MgdMode:Integrated,state:Unknown)
APPPOOL "Classic .NET AppPool" (MgdVersion:v2.0,MgdMode:Classic,state:Unknown)
APPPOOL "MyAppPool" (MgdVersion:v2.0,MgdMode:Integrated,state:Unknown)
Any ideas why we are getting this behavior using AppCMD but not from the Server Manager UI?