« Previous Next »

Thread: The Service is unavailable, to one site but available to others in same app pool

Last post 04-22-2009 3:54 PM by glaze. 3 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (4 items)

Sort Posts:

  • 04-21-2009, 11:21 PM

    • glaze
    • Not Ranked
    • Joined on 02-12-2009, 6:14 PM
    • Posts 5

    The Service is unavailable, to one site but available to others in same app pool

    Ok, so I have 7 web sites running through the same application pool. 6 of which are working just fine the other is not. I have 1 other website running the same model of site as the one that is not working.

    www.glazedproductions.com - is working DefaultAppPool

    www.ricestreetmusic.com - is not working same application pool

    I have tried to recycle the application pool to no avail, and almost thought this could be a php issue, but thats not it either, becuase both sites use php, and one is working and the other is not.

    I have no errors in my log files but I do have this 1 information event...

    Log Name:      System
    Source:        Microsoft-Windows-WAS
    Date:          4/21/2009 7:47:59 PM
    Event ID:      5186
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      glaze.glazedproductions.com
    Description:
    A worker process with process id of '4708' serving application pool 'DefaultAppPool' was shutdown due to inactivity.  Application Pool timeout configuration was set to 20 minutes.  A new worker process will be started when needed.

    Thats all I have to go on... if anyone can help me out it would truly appreciated. This is a client site that is not functional right now, and I have been all over google looking for answers but nothing I come across seems to work.

  • 04-22-2009, 11:07 AM In reply to

    Re: The Service is unavailable, to one site but available to others in same app pool

    Can you get to any pages or just the home page? What errors are you getting in the IIS logs?

    It might be an idea to separate the problem site into a separate app poll for the moment at least so you can restart the pool if needed.

    The eventvwr message is normal behaviour and nothing to worry about.

    Does this help:

    http://mvolo.com/blogs/serverside/archive/2007/05/19/Troubleshooting-IIS7-503-_2200_Service-unavailable_2200_-errors-with-startup-debugging.aspx

     

  • 04-22-2009, 11:28 AM In reply to

    • glaze
    • Not Ranked
    • Joined on 02-12-2009, 6:14 PM
    • Posts 5

    Re: The Service is unavailable, to one site but available to others in same app pool

    Last night I was not able to get to any of the pages, tried Win XP with IE8 and FF3, also tried Win2K8 with IE8 on the non-working site, However today I am able to access child pages via Win XP and IE6. (i.e. www.ricestreetmusic.com/index.php?q=user )

    The error that is produced when I open the homepage now is a 503: The service is unavailable. However, I have no errors in my event logs that are dealing with WAS, or W3SVC or anything like that. I have tried, recycling, restarting and all sorts of other things to the application pool with no luck.

    I will try some of these debugging steps in your post when I get home, hopefully there is something in there that I missed.

    I am having trouble believing it is the application pool at this time, because the application pool is serving 6 other websites are up and running and fully functional. Could it possibly be related to PHP running as FastCGI? I didn't think that would matter either, becuase it was working fine until I upgraded the machine to a DC a few weeks ago. I hadnt realized the site was down until I checked it one day, and started getting the error. Could something have gotten botched when I upgraded to the DC?

     Thanks for your help.

  • 04-22-2009, 3:54 PM In reply to

    • glaze
    • Not Ranked
    • Joined on 02-12-2009, 6:14 PM
    • Posts 5

    Re: The Service is unavailable, to one site but available to others in same app pool

    Ok, so as it turns out it was none of these and it wasn't IIS either. It was a user error, and my bad memory... I had put the site into offline mode, so that the client could gather his inventory and put it online without any orders being taken before he was ready. However, instead of producing the nice layout that should have been displayed, it was giving me the ugly "service not available" message. Which was leading me to believe that it was an IIS error. There is probably still an underlying issue here, but I am not that worried about it. I have tested bringing the site back into online mode as a anonymous user and things work perfectly still. So I apologize for wasting eveyone who might have been thinking about this's time.

Page 1 of 1 (4 items)
Microsoft Communities