Have you ever noticed your WFE server crawling, and then ran Task Manager to find the Memory Usage of some of your w3wp.exe process through the roof. You need to know which process is tied to which application pool to begin troubleshooting. How do you get this information? OK, so this is nothing new, and definitely not specific to SharePoint. But it does come in handy, and I never seem to remember exactly how:

1. From Task Manager, select View > Select Columns

2. Put a check mark next to “PID (Process Identifier)” and click “OK”


3. Open the command prompt

4. Run the following command:

%systemroot%\system32\cscript.exe %systemroot%\system32\iisapp.vbs

The above should result in an output similar to the following:


Notice how each w3wp process is tied to a specific application pool. If you’ve properly labeled your Application Pools and are not using the same Application Pool for all of your IIS sites, this should give you a good place to start looking for problems. If responsiveness is severely hampered you may choose to recycle the the offending Application Pool without having to do an IIS Reset which would impact all of your other sites.

digg_url = “https://blog.rafelo.com/2009/04/so-whats-my-web-application-pool.html”;digg_title = “So what’s my Web Application Pool Process ID (in Windows Server 2003)”;digg_bgcolor = “#FFFFFF”;digg_skin = “compact”;digg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin = undefined;