W3wp.exe frequently restart faulting application w3wp.exe

At some point in time, IIS sends a little nerve.

Symptom (s): Do not know what program is causing IIS to encounter a fatal problem causing IIS application pool to shut down automatically, today's innovation high Day died four times, (these errors can be found in the system event log)

Find a way on the Internet:

The solution is very simple, open the property page of the application pool, remove all the check boxes from the Recycle tab, and let. NET garbage collection manage the memory without getting IIS to intervene.

The process of servicing the application pool ' DefaultAppPool ' has been shut down longer than the limit when the server often generates the application pool ' defaultapppool ' service. The process ID is ' 2068 '. "Error, which causes IIS to be in suspended animation state, is known to be a setup issue for the IIS application pool. The workaround is as follows:

Internet Information Services (IIS) Manager-> Application pool->defaultapppool-> right-click Properties

First, recycling

1, recycling worker process (minutes): checked, the value is 1740

2, recycling worker process (number of requests): Not selected (originally set to 35000)

3, in the following time to recycle work process: not fill

4, consume too much memory when recycling worker process: all do not choose. (2, 3, 4 items may avoid server response problems that might be caused by a forced recycle process when the traffic is high, causing IIS to feign death without responding)

Second, performance

Select only idle timeout of 20 minutes. No other choice. The maximum number of worker processes in the Web garden is 1 (default). Note that the Web garden must remain the default, if you fill in more than 1 of the number will cause some Web site program background program can not open or refresh non-stop.

The original request queue is limited to 4000 and is now unrestricted.

III. Operational Status

The first two items are used, which is the original default setting. The start time limit is 90 seconds and the shutdown time limit is 180 seconds.

Start quick fail protection with hooks removed.

In order to avoid really encountering a lot of errors without prompting, you can not close, just the protection of the rapid protection of the scope of more, such as the failure of 50 times a period of 5 minutes to close the corresponding program.

"Closing time limit of 180 seconds" is a must, because the process shutdown time, originally a 90-second limit, is the default value, if the process shutdown time of more than 90 seconds, it is considered timeout, resulting in: Process shutdown time exceeded the limit log, so the appropriate extension of this time, you can avoid this error

The 2nd method:

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

Workaround:

1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC

2. Under the Parameters key to create a new DWORD entry, the name is: Usesharedwpdesktop value of 1 restart IIS

3rd Kind

The problem has been resolved, found that the database connection can not be released, do not know what the reason, the same code in the local is good, there are problems on the server side, and finally in the connection string to add the following statement to solve the problem.

Pooling=true; MAX Pool size=512; Min Pool size=50; Connection lifetime=30

4th Kind

Create a new application pool, and different Web sites refer to different program pools.

The process to service the application pool ' AppPool #1 ' has been closed for more than limited time. The process ID is ' 3000 '.

When the above situation occurs, the Web site for the application pool is very slow to access and is almost impossible to open.

This phenomenon is not IIS suspended animation.

The problem can be resolved by restarting the site.

It may be an application pool setup issue and I don't know exactly how to set it.

Please advise the master.

Program Code Solutions:

1 Set the process pool recycle time. In the process pool properties.

2 If your program is using ASP + ACC database. And the ACC database is larger than 30m. It is recommended that you replace the SQL database. The ACC database is larger than this value. 2003 system will cause IIS6 of frequent death. 2000 will cause Dllhost.exe to occupy a large amount of CPU and memory resources. The Web Access speed will be severely affected.

3 ASP programs exist dead loops.

4 You can use Microsoft Office compression to repair the ACC database, and you must back it up first.

Referencing content 2003 application pool common problems and solutions for suspended animation 2006-10-09 09:48 often see everyone talk about, 2003 application pool automatically died, can not recover, always appear Service unavailable common methods are as follows. 1: There is no SP1 before the patch will appear this IIS6. 0 suspended animation problem, but now Microsoft is in the automatic update of the patch, usually you play the latest patches will not appear this problem. (So now the IIS animation is not very much the relationship) 2: Starting from IIS6.0 CPU resources are limited in the application pool, unlike 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 resource limits 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. 　　　 Last time I wrote about this tutorial. (2): Memory limit in IIS6. 0 The 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, fix the method;Ccess the database, or use the Access database as little as possible. 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.