One of the developers was looking to debug the solution package on a web application from a server which wasn’t hosting the web application as it had visual studio on it.
Started the Web Application service and it stuck at starting
IISRESET didn’t come to rescue; I had to run the stsadm command by changing the command prompt path to the 14 hives to resolve the service stuck at starting .
stsadm -o provisionservice -action start -servicetype spwebservice
Note: this has to run from the server where you intend to host the web application
And then IISRESET / NOFORCE
There is a KB Article which talks at great length why this happens and how to overcome this:
Wow! At last I got a web site from where I can genuinely obtain helpful facts
ReplyDeleteconcerning my study and knowledge.
Feel free to surf my web-site - furnace filter air conditioner filters
Thank you, this was very helpful!
ReplyDeleteThanks it helped me out. Regards, Waqas
ReplyDeleteThanks, it worked!
ReplyDeleteThis worked for me as well, thank you! Note two things: 1) I needed to run this as a SharePoint account that can write to SQL. 2) I needed to run this on my Web Application Server. I know you mentioned something about this above, but to me, that meant ANY SharePoint server.
ReplyDeleteTHIS WORKS THANKS A LOT :D
ReplyDeleteWorked!
ReplyDeletethanks
ReplyDeletedoes this work on sharepoint 2013?
ReplyDelete$service = $(Get-SPServiceInstance |where {$_.TypeName -match “Microsoft SharePoint Foundation Web Application” } |where {$_.Server -match “SPServer Name=SERVERNAME”})
ReplyDelete$service.provision()