Solution to service unavailable on the page

Symptom:
Visit the site. The application pool is automatically closed, and the message "Service unavailable" is displayed.

 

Solution Process:

There are a lot of information about Baidu and Google on the Internet for the following reasons and methods:

I. Restrictions on the number of connections set in IIS. The number of accesses to the website is too large. This is my own machine. This problem does not exist.

Solution: Increase the number of IIS connections

 

2. There is no restriction on IIS connection. The application pool account is a domain account and its password has expired. This problem does not exist according to my actual situation.

Solution:

Verify that the password used by the application pool account is correct. IIS does not automatically poll the password changes in the Active Directory Service. If the application pool account is a domain account whose password has expired, you must specify a new password for the account.

Follow these steps to verify that the password used by the application pool account is correct:

A. in the Internet Information Service (IIS) manager, expand "application pool ".
B. Right-click the application pool configured for the virtual server (for example, right-click "mssharepointportalapppool") and click "properties ".
C. Click the "ID" tab.
D. In the "password" box, type the password used by the application pool account listed in the "user name" box, and click "OK ".
E. In the "Confirm Password" dialog box, type the password again and click "OK ".

 

3. The application pool account is not a member of the iis_wpg group or sts_wpg group on the server. This problem does not exist in my actual situation.

Solution:

Select one of the following methods based on your situation.

A. When the SharePoint Portal Server is installed on the Member Server:

1. Click Start, point to administrative tools, and click computer management ".
2. Expand "local users and groups" and then expand "users ".
3. Right-click the account used by the application pool of the virtual server, and click "properties ".
4. Click the members tab.
Verify whether iis_wpg and sts_wpg both appear in the "member belongs" list. If either of them is not listed or both are not listed, add iis_wpg group, sts_wpg group, or these two groups to the list based on the actual situation.

B. When the SharePoint Portal Server is installed on the domain controller:

1. Start "Active Directory users and computers ".
2. Expand "user ".
3. Right-click the account used by the application pool of the virtual server, and click "properties ".
4. Click the members tab.

Verify that iis_wpg and sts_wpg both appear in the "member belongs" list. If either of them is not listed or both are not listed, add iis_wpg group, sts_wpg group, or these two groups to the list based on the actual situation.

 

Cause 4: Access Engine error, or too many program logic errors. I have no such problem.

Solution: modify the program code and restart IIS.

 

Cause 5: the permissions of the DCOM component are insufficient. At the beginning, I thought that my IIS was an error in this situation. I tried it later.

Solution:

When viewing event logs, the following message is displayed:
Event Type: Warning
Event Source: w3svc
Event Type: None
Event ID: 1009
Date: 2007-7-11
Event: 14:57:47
User: N/
COMPUTER: GHITR-61969D77E
Description:
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 authority/NETWORK SERVICE
COMPUTER: GHITR-61969D77E
Description:
Application-the COM server application (CLSID is
{A9E69610-B80D-11D0-B9B9-00A0C922E750}
The Local activation permission of grant the user nt authority/network service Sid (S-1-5-20 ). You can use the component service management tool to modify this security permission.

Processing Process: The main useful information is to remember the CLSID: {A9E69610-B80D-11D0-B9B9-00A0C922E750}, open the registry, search for this item, in this item a value named LocalService IISADMIN, it seems that this component has insufficient permissions. Open the management tool --- Component Service, right-click the properties on the Component Service -- computer -- my computer -- DCOM configuration -- IIS Admin Service, and click the edit button in the Enable and enable column of the security label, add the network service user, grant local start and Local activation permissions, and then restart IIS

 

Cause 6: The ISAPI filter is not loaded properly. At the end of the test, I realized that this was the fault because I tried a googlesitemap tool on the local machine a few days ago and then generated a googlesitemapgeneratorfilter filter in my IIS, later, I thought that googlesitemap was useless and deleted the entire file in the system disk. Then, it showed that "all ISAPI filters for sites/services cannot be loaded. ." . If the ISAPI filter is not loaded successfully, the Service unavailable will appear when any website is accessed.

Solution: Solve the Problem Based on the cause of loading failure, or delete the ISAPI filter. I will delete the ISAPI filter directly.

Step: IIS (6.0) Manager-website-properties-ISAPI filter-select the ISAPI filter to be deleted-delete