We help IT Professionals succeed at work.

Error 503 in a 2008 R2 web ser with IIS7.5

limmontreefree
limmontreefree asked
on
Hello sometimes, i obtain an error 503 from my IIS7.2 running in a 2008 R2.

The machine actually is for test porpouses so it haven't high stress, when the problem appear i have to reboot the server.

Where are the logs for IIS7.5?

Where I have to see?

thanks
Comment
Watch Question

Top Expert 2011

Commented:

Author

Commented:

thanks Sammy,

 I am new in IIS, I would like to know the logical steps for a first review of an IIS, find the logs,  ...

Your link looks very interesting though brainstorm  but I think that not is the most common way of looking for trouble for a newbie, rather, appears as "desperate" to "shoot everything".

Can you give me information on where are the log and guidelines to check that an IIS is working well, your work load etc ...

 Forgive my wrong English..

Thanks again for your interest.













Top Expert 2011

Commented:
Ok, according to that post, port 80 may used by another url.

If that's the case, then delete it by doing the following:

Or manually delete it.

Alternatively, you can create a new port, say port 82 so your url should look similar to:

http://servername:82/foldername/

netsh
http
delete urlacl url="http:+:80"

Commented:
503 are served by the http.sys module before it gets to IIS.

They have their own log file

look in the http.sys logs for more details of your 503 error message.

the default location of these is:

<windows dir>/system32/logfiles/httperr/<date>

Post these here for the relevant time.

That should give you most of the info you need to troubleshoot this.

Use this page:
http://support.microsoft.com/?id=820729
Section:Types of errors that the HTTP API logs
look up the reason and look at the explanation for more info on the http.sys 503 error.

====
Most common is the app pool is stopped and needs to be restrated.

Author

Commented:

this is the log

#Version: 1.0
#Date: 2011-12-01 19:58:37
#Fields: date time c-ip c-port s-ip s-port cs-version cs-method cs-uri sc-status s-siteid s-reason s-queuename
2011-12-01 19:58:37 64.246.165.50 37688 192.168.6.100 80 - - - - - Timer_MinBytesPerSecond -
2011-12-01 22:24:48 79.154.76.227 1596 192.168.6.100 80 HTTP/1.1 POST /Registro_Miembros.aspx - 3 Connection_Abandoned_By_ReqQueue DecoOutlet
2011-12-01 22:24:48 79.154.76.227 1578 192.168.6.100 80 HTTP/1.1 GET /Promocion.aspx?Id=0 - 3 Connection_Abandoned_By_ReqQueue DecoOutlet
2011-12-01 22:24:48 79.154.76.227 1585 192.168.6.100 80 HTTP/1.1 POST /ListadoBonos2.aspx - 3 Connection_Abandoned_By_ReqQueue DecoOutlet
2011-12-01 22:24:52 79.154.76.227 1597 192.168.6.100 80 HTTP/1.1 GET /Promocion.aspx?Id=0 - 3 Connection_Abandoned_By_ReqQueue DecoOutlet
2011-12-01 22:24:55 79.154.76.227 1598 192.168.6.100 80 HTTP/1.1 GET /Promocion.aspx?Id=0 - 3 Connection_Abandoned_By_ReqQueue DecoOutlet
2011-12-01 22:24:58 79.154.76.227 1601 192.168.6.100 80 HTTP/1.1 GET /Promocion.aspx?Id=0 - 3 Connection_Abandoned_By_ReqQueue DecoOutlet
2011-12-01 22:25:01 79.154.76.227 1602 192.168.6.100 80 HTTP/1.1 GET /Promocion.aspx?Id=0 - 3 Connection_Abandoned_By_ReqQueue DecoOutlet
2011-12-01 22:25:01 79.154.76.227 1606 192.168.6.100 80 HTTP/1.1 GET /Promocion.aspx?Id=0 503 3 AppOffline DecoOutlet
2011-12-01 22:25:06 79.154.76.227 1608 192.168.6.100 80 HTTP/1.1 GET /Default.aspx 503 3 AppOffline DecoOutlet
2011-12-01 22:25:09 79.154.76.227 1610 192.168.6.100 80 HTTP/1.1 GET /Default.aspx 503 3 AppOffline DecoOutlet
2011-12-01 22:25:14 79.154.76.227 1612 192.168.6.100 80 HTTP/1.1 GET /login.aspx 503 3 AppOffline DecoOutlet
2011-12-01 22:25:18 79.154.76.227 1614 192.168.6.100 80 HTTP/1.1 GET /default.aspx 503 3 AppOffline DecoOutlet
2011-12-01 22:25:27 79.154.76.227 1616 192.168.6.100 80 HTTP/1.1 GET / 503 3 AppOffline DecoOutlet
2011-12-01 22:25:48 79.154.76.227 1620 192.168.6.100 80 HTTP/1.1 GET / 503 3 AppOffline DecoOutlet
2011-12-01 22:26:18 79.154.76.227 1622 192.168.6.100 80 HTTP/1.1 GET / 503 3 AppOffline DecoOutlet
2011-12-01 22:27:30 79.154.76.227 1698 192.168.6.100 80 HTTP/1.1 GET / 503 3 AppOffline DecoOutlet

thanks

Commented:
The error is AppOffline that means that the application pool is offline or in other words, stopped.

Go into IIS manager select Application pools on the right and start DecoOutlet pool

Author

Commented:
Yes but Now the question is "why is stopped"

Thanks
Hi,

Due to heavy load are if it's a classic Application-pool some .Net file Error's having.

better Remove that and reconfigure Application-pool and each application-pool run only one website for better performance.  
Commented:
There are many reason an app pool can be stopped. Some coudl ahve manually stopped it (it happens!), you can configure the app pool to stop when you a x number of failures.

Have a look also in your event log to see what asp.net (or whatever technology you are using) errors there are.

Marry that timeline up with what is in the IIS logs (look for 500 errors, long running pages, etc) and the http.sys logs.

that will get you a picture of what is happening.

Author

Commented:
I have a "stop" instruction in  my visual basic code, If this "stop" instruction is executed can stop the app pool?

thanks
Commented:
I would say not. You can do things to restart (and stop) an app pool but it is specialist code.

Things like:
http://bytes.com/topic/c-sharp/answers/532974-how-stop-application-pool-iis-6-0-c

Author

Commented:
thanks