I have Windows 7 professional 32-bit with IIS 7.5 installed and configured. I installed the SP1 for Win 7 and since then the IIS is no more working. Even for simple queries like localhost/a.htm (where a.htm is a html file inside under c:\\inetpub\\wwwroot) leads me to the error:
HTTP Error 503. The service is unavailable.
The IIS worked fine up to SP1 (I have a lot of ASP.NET2/.NET 4 applications on it). I uninstalled the SP1, the same happens. What should I do?
Thanks.
I had this issue and it turned out to be that SP1 causes the "Load User Profile" setting on your Application Pools to be set to "True" causing IIS to use a Temp User Profile that doesn't have sufficient permissions.
To fix it I took the following steps:
The solution is provided here by squillman.
Sounds like your app pool(s) is/are not starting. Open IIS Manager and click on Application Pools, then check the Status column and make sure the all say Started (or at least your DefaultAppPool says Started). If it's not started, right-click on the app pool and choose Start. If you get an error let us know what it is.
At the command line, run (you might need to be administrator)
netsh http show urlacl
If any of those conflict with your IIS bindings, delete them with netsh http delete urlacl
.
Just had the same problem after Win7 SP1 got installed. The problem in my case was Skype: that was listening in on ports 80 and 443 and thus blocking IIS. Told Skype not to do that (there is a checkbox for that in Settings | Advanced | Connection) and my sites worked again.
What the relation is between Skype forgetting that setting and the installation of SP1 (other than it happening at the same time) I don't know.
I just googled the eventlog message for you and got this as a posible solution:
The solution provided by andyvidual did not help. I realized that the default application pool had stopped. When I started it the error went away and I could display the issstart.htm. Then I checked the default app pool settings and noted that the Load User Profile was 'TRUE'. I changed it to 'FALSE' but the 503 error did not come back. I guess it is the stopped pool that was responsible.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.