Today we discuss the problem between the service unavailable and the program pool resource configuration on the IIS site.
Right-clicking on an IIS application pool, selecting Properties, pops up a Program Pool Properties dialog box with four tabs.
1, "Recycle" tab
The Recycle tab allows you to set the time interval for the recycle process pool, and all resources occupied by the process pool are released each time the process pool is reclaimed. This load on the server is a powerful mitigation!
In memory recycling, you can set the maximum amount of memory and virtual memory that the program pool can occupy, and if the limit is exceeded, the process pool will be terminated. The limitations of memory and virtual memory are based on specific sites, and it is generally recommended that the limits of memory and virtual memory be set at around 500M.
2, "Performance" tab
One important item in the Performance tab is "Enable CPU monitoring", which sets the process pool to shut down when the CPU usage of the program pool exceeds the specified percentage. The recommended tuning parameters are: Refresh CPU usage every 1 minutes, and perform a "close" operation when CPU usage is over 50%.
3, "Health" tab
There are also two important parameters in the Health tab: Startup time limit and shutdown time limit. For example, the previous set of hyper-memory and the super CPU will shut down the program pool, may be shutdown of the program pool failed, then what should be done this time?
If the pool is not closed for a specified period of time, IIS waits for shutdown time limit to force it to shut down a refresh CPU time. In this stop time, the website is unable to access, prompt "Service unavailable". Shutdown time and start interval settings: Set for a short period of time, such as 10 seconds, so that when your Web site program is heavily occupied with system resources, IIS automatically quickly reclaims the process and quickly start the process, your site can temporarily work on.
The two values are suggested to be set to 10 seconds.
4, "Identity" tab
The Identity tab, the master is used to set what account the current program pool runs on, not in the context of our discussion today.
The above four tabs are mentioned, below we go to the point to solve the service unavailable problem.
1. First, open IIS Manager. Check the application pool, and sure enough, "DefaultAppPool" went wrong. And not the usual stop icon.
2. Try to focus on the "DefaultAppPool" application pool, but it didn't take long for the program pool to go wrong again.
3. It's time to view the event log. The following types of logs were found
Event Type: Warning
Event Source: W3SVC
Event Type: None
Event id:1009
Date: 2008-6-24
Event: 16:12:33
Users: N/A
Computer: MAIL
Describe:
The process providing service for application pool ' DefaultAppPool ' terminated unexpectedly. The process ID is ' 3160 '. The process exit code is ' 0xFFFFFFFF '.
For more information, see the Help and Support Center in http://go.microsoft.com/fwlink/events.asp.
4. Will it be the default program pool problem? So, try creating a new pool of programs. Change the default Web site's program pool to new. But the problem remains. A similar log appears.
Event Type: Error
Event Source: W3SVC
Event Type: None
Event id:1002
Date: 2008-6-25
Event: 14:17:04
Users: N/A
Computer: MAIL
Describe:
The application pool ' AppPool #1 ' was automatically disabled because of a series of errors in the process that serviced the application pool.
For more information, see the Help and Support Center in http://go.microsoft.com/fwlink/events.asp.
5. Look up the event log another log caught my attention. As follows:
Event Type: Error
Event Source: DCOM
Event Type: None
Event id:10016
Date: 2008-6-24
Event: 16:12:33
User: NT authoritynetwork SERVICE
Computer: MAIL
Describe:
Application-specific permission settings do not include COM server applications (CLSID as
{a9e69610-b80d-11d0-b9b9-00a0c922e750}
The user NT authoritynetwork SERVICE SID (s-1-5-20) is granted the local activation permission. You can use the Component Services Administration tool to modify this security permission.
For more information, see the Help and Support Center in http://go.microsoft.com/fwlink/events.asp.
6. It's a bit of a play. See the CLSID for {a9e69610-b80d-11d0-b9b9-00a0c922e750} is what service first. Finally, find it in the following registry key:
HKEY_CLASSES_ROOTAPPID{A9E69610-B80D-11D0-B9B9-00A0C922E750}
7. The name happens to be "IIS Admin Service"
8. Well, find out what it is. To open Component Services from Administrative Tools, locate the IIS Admin service to compare the CLSID to the same
9. After confirming this, the next step is to increase the network service privileges for it.
A start and activate permissions, click "Custom".
B. Add "Network SERVICE" to the list of users,
C. and give local start and activate permissions, save exit.
To solve this problem.