locked
Error 503 RRS feed

  • Question

  • I cannot reconnect to a website though i continuously received email notification from them. Every time i try  ssl.myyearbook.com/token/24boc2ec/42298645 Service Temporarily Unavailable Error 503 saying " the server is temporarily unavailable to service your request due to maintenance downtime or capacity problem, pls. try again later" flashing on my monitor. What is the meaning of this and what should i do?
    Friday, May 11, 2012 7:43 AM

Answers

  • liding

    From my experience I have noticed that this error is usually related to the IIS. 

    Please check to see if the app pools are up and running and if the necessary services are up and running too.

    Here is a link with steps to do it:

    http://nassharepoint.wordpress.com/2009/01/13/sharepoint-site-error-service-unavailable-http-error-503-the-service-is-unavailable/

    Friday, May 11, 2012 12:33 PM
  • Hi,

    Quite a few things could cause this but you'll need to carry out further investigation particularly with IIS and Services.MSC in the farm.

    Check the state of IIS in particular the application pools and confirm they are running; in particular that SecurityTokenServiceApplicationPool is ok. Second, check the event IDs relevant to WAS (do you for example see 5021, 5057 and 5059).

    If you do see WAS errors, check whether there are any GPO changes that are preventing application pools from starting up - e.g. blocking certain permissions.

    Hope this helps

    Geoff

    Friday, May 11, 2012 12:38 PM

All replies

  • liding

    From my experience I have noticed that this error is usually related to the IIS. 

    Please check to see if the app pools are up and running and if the necessary services are up and running too.

    Here is a link with steps to do it:

    http://nassharepoint.wordpress.com/2009/01/13/sharepoint-site-error-service-unavailable-http-error-503-the-service-is-unavailable/

    Friday, May 11, 2012 12:33 PM
  • Hi,

    Quite a few things could cause this but you'll need to carry out further investigation particularly with IIS and Services.MSC in the farm.

    Check the state of IIS in particular the application pools and confirm they are running; in particular that SecurityTokenServiceApplicationPool is ok. Second, check the event IDs relevant to WAS (do you for example see 5021, 5057 and 5059).

    If you do see WAS errors, check whether there are any GPO changes that are preventing application pools from starting up - e.g. blocking certain permissions.

    Hope this helps

    Geoff

    Friday, May 11, 2012 12:38 PM