The cause of the problem was eventually found in two:
1, the use of the Jet database connection method problems: http://support.microsoft.com/?id=838306
Chinese version of patch file: Windowsserver2003-kb838306-x86-chs.exe
English version: Windowsserver2003-kb838306-x86-enu.exe
2. Change the Access database extension to ASP
Here are the error processes and solutions:
Search to find a lot of similar problems, that w3wp process is iis6.0 application pool, the online version of two, one is because the ASP or asp.net code contains a dead loop caused. But there are so many websites on the server, who knows that the site is out of the question. The second is because the above jet connected to the database method of the bug caused by the download 838306 patch, or upgrade to SP1 can solve the problem, but after this patch, some of the site's problems still exist.
To search again, it was said that each site should be established as a separate application pool, with the application pool's security account set as Local service. The method is as follows:
First create a new application pool:
Then point the application pool for the Web site to the application pool you just created:
After all application pools have been established, the properties of the application pool are uniformly modified:
To designate an application pool security account as a local service:
After setting these up, the problem persists, such a web site is not affecting other sites, but the site still takes up a lot of resources, causing other sites to respond slowly. However, the process of each application pool appears in Task Manager, so you can find the specific problem process.
Here's the process of looking for an error site: To find this site, you have to link the problematic process to the site's application pool. First set the Task Manager to view the way to add the PID display:
Then the command line runs IISAPP-A, and you can see the relationship between the PID and the application pool:
Then go to IIS to see the application pool corresponding to the site, the problem of the site is found, the rest is the site code in the problem.
In a Web site administrator's entanglement, I finally unbearable, help him find errors-countless times to configure IIS, the Web site program also changed, the upgrade also upgraded, the problem is still there, at the end, to download the site to see what is going on. When I tried to open his database, the problem came up:
His database is an. asp extension that you want to change to. mdb before it can be opened, but when I click to change my name, My computer doesn't respond! Looks like the problem is in this database.
After using the command line rename, open the database, fix it, there seems to be no problem, but change to. asp, there are just the problems. The original is. asp's extension is in mischief.
But I tried to change the other database to. asp, no problem. The root cause is unknown, hope the person informed.
Finally, an ISAPI is added to the MDB in IIS, causing the MDB to not execute, prevent downloading, and change all the. asp's database back to. mdb, problem solving.
