The "go" IIS resolves an application pool * * Service-Provider process that unexpectedly terminates the process ID is * *. Process exit code is ' 0x80 '

transferred from: http://blog.sina.com.cn/s/blog_56a68d5501013xdd.htmlthe red-and-black interconnection of our company is experiencing this problem

Event Type: Warning
Event Source: W3SVC
Event Type: None
Event id:1009
Date: Event: XX:XX:XX
User: XX
Computer: XXXX
Describe:
The process servicing the application pool XXXXX terminated unexpectedly. The process ID is XXXX. The process exit code is 0x80.
For more information, see the Help and Support Center in ASP >http://go.microsoft.com/fwlink/events.asp.
Reason:
Cause
Together with all worker process that IIS creates under a separate identity, the system creates a new desktop object by a Llocating memory from the configured desktop heap. This issue occurs because, when the heap has been exhausted, the IIS cannot create more worker processes. Clients then receive the ' Service Unavailable ' error message in their Web browsers when they try to visit Web sites that T Hose Application Pools host.
The memory heap constricted of the standalone process is exhausted, and IIS cannot create more process workspaces to handle
Workaround:
Warning: The registry of the server needs to be modified, please modify the pre-backup phase key value
Add the Usesharedwpdesktop registry key to your computer, which is running IIS. This registry key permits all worker processes to run in one shared desktop, regardless of their worker process identities .
To add the Usesharedwpdesktop registry key:

1. Hkey_local_machinesystemcurrentcontrolsetservicesw3svc
2. Create a new DWORD entry under the Parameters key named: Usesharedwpdesktop with a value of 1 restart IIS
Ms about this key value description:
Usesharedwpdesktop
Registry path: Hkey_local_machinesystemcurrentcontrolsetservicesw3svcparameters
Data type: REG_DWORD
Default value: 0
Range: 0-1
If you are setting up an application pool with a unique identity, the upper limit of approximately 60 application pools will be reached based on the application and memory resources on the server. Some restrictions exist for system resources that are assigned a single new logon session. This indicates that there can be 60 processes running at the same time as different accounts. IIS 6.0 supports running these processes on a single shared workstation and desktop in a single package that shares a single user session across all parties. To scale up to 60 application pools and share a single desktop, you can change the usesharedwpdesktop to a DWORD value of 1. After you change this registry key, you should be able to scale to hundreds of application pools and hundreds of concurrently running worker processes.

Description :

The process servicing the application pool ' XXXXX ' terminated unexpectedly. The process ID is ' XXXX '. The process exit code is ' 0x80 '. For more information, see the Help and Support Center in http://go.microsoft.com/fwlink/events.asp.

reason :

The memory heap constricted of the standalone process is exhausted, and IIS cannot create more process workspaces to handle

Workaround :

1. Open Registry Editor.

2. Find HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC

3. Create a new DWORD entry under the Parameters key with the name: Usesharedwpdesktop value of 1, restart the server.

The "go" IIS resolves an application pool * * Service-Provider process that unexpectedly terminates the process ID is * *. Process exit code is ' 0x80 '