IIS application pool Auto stop/shutdown/Suspended animation network prompt Service unavailable solution

Problem phenomenon:

Visit the site. Causes the application pool to shut down automatically, prompting for service unavailable. The MMC is prompted for errors when you allow and disallow some Web service extensions.
Resolution process:
Initially assumed to be an issue with IIS. After reloading n times, the problem remains. Look at the event log with the following prompts:
Event Type: Warning
Event Source: W3SVC
Event Type: None
Event id:1009
Date: 2007-7-11
Event: 14:57:47
Users: N/A
Computer: ghitr-61969d77e
Describe:
Event type for application pool: Error
Event Source: DCOM
Event Type: None
Event id:10016
Date: 2007-7-11
Event: 14:57:47
User: NT authoritynetwork SERVICE
Computer: ghitr-61969d77e
Description:
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 [Url]http://go.microsoft.com/fwlink/events.asp[/url].
The main useful information is the letter clsid: {a9e69610-b80d-11d0-b9b9-00a0c922e750}, open the registry, search for this item, in which a value named LocalService is IISAdmin, It seems that this component has insufficient permissions. Then open the Admin tool---Component Services, in Component Services--computer--My Computer--dcom configure--iis ADMIN service on the right key attribute, the Edit button in the Security tab for the startup and activation bar, plus the Network service user, Give local start and local activation permissions, and then restart IIS, but not the best solution

Problem Analysis and Solutions

1: Did not hit SP1 patch will appear this IIS6.0 suspended animation problem, but now Microsoft is in the automatic update of the patch, usually you hit the latest patches will not appear this problem. (So the current IIS death is not very much the relationship)
2: Starting from IIS6.0 CPU resources are limited in the application pool, unlike the previous iis.5. So the death of the pool because the pool is pulled dead, you can not open the site to see one of your application pool is disabled, there is a red fork. Your right mouse button to start the site will automatically resume. This reason: probably the following factors caused.
(1): You limit the resources of the application pool, limited too small, such as: 50 this or a little more, this time if your site under the pool to occupy CPU too high, such as more than 50% then 5 minutes after he automatically died, the default set of application pool by default is more than resources do not operate.
The above situation is resolved: 1: Unlimited CPU resources, (this is not desirable, not limited resources, and some programs have bugs occupy resources are severe, the server will be pulled dead, you may not be able to operate the server.) 2: In excess of resources there is a choice to close, this shutdown defaults to 5 times, 90 seconds to restore, the general default can be. Web site can be automatically restored, this shutdown: not permanently closed, meaning that the resource is closed, and then the pool is automatically recovered within a certain time. Does not operate is not restores, this is many people's misunderstanding.
(2): Memory limit on the IIS6.0 application pool has virtual memory and maximum memory limit, if you set this. Then the Web site traffic will also appear suspended animation, so it is not recommended to set up here. Default is available.
3: The server itself is too small, the Web site to run, of course, need to use the memory, when the memory is not enough when the application pool will die to become disabled. Then the application pool can be restored only when all the memory is released. This happens: then you have to consider adding memory or checking that the program is consuming memory. For example, the MSSQL database, this is a large memory to eat ah, it is best not to and the Web server at the same time a server. Many people use 1G memory to do 2003 system, 2003NET structure is very occupied memory, so do server Select 2003 also have to add memory to 2G or more higher good. Not enough memory above 2 o'clock mentioned, there is no way to operate, and can not automatically recover.
4: The Access database is too large or too many queries, this will also appear to pull IIS dead, the solution, repair the Access database, or minimize the Access database to upgrade to the SQL Server database, or technical innovation, such as some of the current web systems, wind, Dynamic and so on Cms;pjblog, Zblog and other blog programs, support the generation of static functions.
5: Different sites with different application pool: According to your own actual situation, the site is the best independent of a pool of applications, limit his resources more than automatic recycling, see above (1), so that does not affect other sites. Medium site: Multiple sites share an application pool, such as 5 sites with a pool, set his resource time and so on. So that they do not even have resources to affect the other application pool sites.
6: Set the recovery time: Many people think that the shorter the collection pool, the better, in fact, is wrong, each recycling of course is the memory back, but increased the burden of a server, when the server is busy, it may lead to other application pool dead. So it is recommended to set a total of 1000 on the line. Other standalone pools can be set to 600 or more according to the traffic on his site, and the recommended settings for sharing are too short.
7: The site will not be long after the automatic exit and landing again: this situation is that you set the recovery time is too short, according to the 6-point set it. Do not set what 20 points, 30 points like this, so bad. Another reason is that the station's response to set the time, set a little longer.
8:windows 2003 System IIS6 access to the local site when prompted "Service unavailable";
View the application pool for IIS, which indicates that no error has been specified and that the application pool is automatically stopped;

Use Event Viewer to view the system error log and find the following prompt:

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.
Workaround, add the permissions to the network service to access the IIS services as follows:
Click "Start"-"Control Panel"-"Administrative Tools"-"Component Services"-"Computer"-"My Computer"-"DCOM" options,
Select "IIS ADMIN SERVICE" Under it, right-click Select "Properties", find "security", edit "Custom" in "Start and Activate Permissions", add account "Network SERVICE", give the account "local startup" and "Local activation" permission, After restarting IIS and then accessing the same site, everything is OK.

9: Restart the specific application pool command and automatic restart in IIS
In the case where the operating system is Windows Server 2003 sp1+, you can restart the IIS application pool with the following command section:
cscript.exe c:windowssystem32iisapp.vbs/a "DefaultAppPool"
where/a represents alternatively, and "DefaultAppPool" represents the instance name of the application pool
10: Website has cc attack

The solution to the problem of "unspecified errors"

Three scenarios found:
The first workaround is to fix the Db/global.asa using the Tools-> Database utility in MS Access-> compression and repair database. If the repair is still an error, please check the DB directory if there are global.dbl files, if you want to delete, if you can not delete the server w3wp.exe process (win2003) or Aspnet_wp.exe process (Win2000) and then delete.

The second solution:
Set up an application pool in Internet Information Services (IIS) Manager, change the site's pool properties, primarily performance settings, and other best defaults.

You can fix the problem after adjusting.
The third solution:
In fact, as long as a few simple steps:
Begin... Run... regsvr32 jscript.dll start ...
Run... regsvr32 vbscript.dll start ...
Run... IISReset

The fourth solution:
Hkey_local_machinesystemcurrentcontrolsetservicesw3svcparameters
Create a new DWORD entry with the name: Usesharedwpdesktop value 1 Restart IIS