For several months we’d have an issue from time to time where an IIS 6 Application Pool would go rogue and take over one of our web servers. Invariably we wouldn’t be able to determine which one it was, and would either terminate the process, or run an iisreset to clear up the problem. The biggest concern with this is that you don’t know which application is causing you the headaches.
Microsoft it would appear has already devised a solution to this problem in the form of the IIS admin scripts that ship with Windows. These scripts can do all sorts of things, but I’m going to focus on the one that will resolve the problem above.
The scripts are located in %WINDIR%\System32 and are in the format iis*.vbs. To get a look at which process is running for a given application pool try:
C:\WINDOWS\system32>cscript iisapp.vbs
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.W3WP.exe PID: 3492 AppPoolId: DefaultAppPoolC:\WINDOWS\system32>
Yes. It’s that easy. If you struggled with it as long as I did, I’m sure you’re feeling the same combination of mirth and frustration right about now.
0 responses so far ↓
There are no comments yet...Kick things off by filling out the form below.
Leave a Comment