Solved IIS Running But Cannot Connect
-
@JaredBusch said:
@Reid-Cooper said:
Wait 2.0? Did you properly configure the pool? Gimme a minute and I can log into a Server 2012 R2 with IIS running.
This is the application pool. You may also need to select classic pipeline mode.
-
@JaredBusch said:
Are you certain there are no logs?
No, only certain that I didn't find anything logged
I'll check again. -
@JaredBusch said:
@Reid-Cooper said:
Wait 2.0? Did you properly configure the pool? Gimme a minute and I can log into a Server 2012 R2 with IIS running.
Yes, very old. And I "did" have it configured properly, it was running fine before the reboot. So at least at some point it was working as it should.
-
@JaredBusch ah ha, there we go! The 2.0 pool had "stopped" for some reason. I started it and the site came up. Thanks!
-
There were two application pools, one for 2.0 Integrated that was running, and one for 2.0 Classic which had stopped. Classic was the one that was needed.
-
@Reid-Cooper said:
There were two application pools, one for 2.0 Integrated that was running, and one for 2.0 Classic which had stopped. Classic was the one that was needed.
If you click on Basic Settings for your application it tells you which pool it is using.
-
Well I thought that we were good. I started the pool and the site came up. Went to refresh the page and it is down again with the same 503 error again.
-
Here is the error that I get...
-
That is the error that I get if I attempt to recycle the 2.0 Classic Pool.
-
Okay I have no experience with this but Googling around I found someone suggesting that you just make a new pool and move the application to that. Maybe that would work.
-
@scottalanmiller said:
Okay I have no experience with this but Googling around I found someone suggesting that you just make a new pool and move the application to that. Maybe that would work.
Tried that. For the moment, it came back up. Fingers crossed.
-
@scottalanmiller said:
Okay I have no experience with this but Googling around I found someone suggesting that you just make a new pool and move the application to that. Maybe that would work.
This is the route I would take. Every time I have an issue related to a pool, I have just made a new one. Never bothered to learn root cause. just moved on. It has only happened a time or two for me. We do not have a lot of IIS stuff out there (not counting azure websites).
-
Makes sense. Although I am a little worried that the new pool just died all by itself. I wonder why that would happen. Will see if it happens again.
