Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Service Unavaiable - ApplicationPool won't start

I have a WCF Web Service which is kept under an Application Pool on IIS.

Lately I've been getting "Service Unavaiable" when I'm trying to make calls to this Web Service. The first thing I tried to do was restarting the Application Pool. I did it and after a couple of seconds, it crashed and stopped.

Looking at the Event Viewer, I found these messages, which by the moment couldn't help me to find where the problem is.

A process serving application pool 'X' reported a failure. The process id was '11616'. The data field contains the error number.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

After getting a couple of these, I got this one:

Application pool 'X' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I've already checked permissions and Application Pool configurations but everything seems to be OK.

Have anyone been through this?

Thanks in advance.

like image 939
born to hula Avatar asked May 14 '10 20:05

born to hula


People also ask

Why application pool is getting stopped?

You should still investigate why the app pool has been stopped. Typically this means that the worker process has crashed a number of times in a short period of time. The Event Log, under the "System" category, should have info on when the faults were detected by the WAS service.

How do you know if an application pool has stopped?

In Event Viewer, expand the "Application and Services Logs" section. Then expand "Microsoft, then "Windows". Then expand "IIS-Configuration, right-click on "Operational", and choose "Enable Log". Now this log will receive events whenever an application pool is stopped or started via the IIS Management GUI.

How do I fix HTTP error 503 service is unavailable Windows 10?

A simple resolution for HTTP Error 503 is to start the application pool corresponding to your website. If you get an application pool identity-related error or warning, make sure the username and password for the identity are correct. If a custom username is used, make sure its password is not expired.


1 Answers

Take a look at the identity that the Application Pool is running under. If you have it configured to run under a domain account, (and this is on an IIS 6.0 server) be sure that the domain account is a member of the local security group "IIS_WPG", for membership in the IIS_WPG group is needed to run the w3wp.exe worker process.

like image 194
kcb263 Avatar answered Oct 20 '22 04:10

kcb263