A way to resolve application pools being automatically disabled

It is also a problem with a client Exchange server. Exchange 2003 and DC are the same server. After installation, always cannot open the default Web site's homepage, display Service unavailable.

1. The first is to 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 logs have been 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? So, try creating a new program pool. Change the default Web site's program pool to new. But the problem remains. Similar logs appear.

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. Find 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. Look at the CLSID for {a9e69610-b80d-11d0-b9b9-00a0c922e750} 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. All right, find out what it is. Open Component Services from Administrative tools to find the IIS Admin Service compare the CLSID for consistency

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.