Skip to main content

List Process IDs (PIDs) for your IIS Application Pools

One of our production servers started to send out alerts because the memory consumption was too high. A first look at the server showed us that one of the w3wp processes was consuming most of the available resources on the server.

 


Sidenote: Web applications running within Microsoft’s Internet Information Services (IIS) utilize what is known as IIS worker processes. These worker processes run as w3wp.exe, and there are typically multiple per server.

So we knew that one of our web applications was causing trouble. The question of course now is which one?

As the resource manager only showed us the process id, we couldn’t immediately give the answer. But with some extra command line magic we got the answer.

To get the information we need we used the appcmd utility. This tool allows; among other things; to list the IIS worker processes.

We executed appcmd list wps and got the the list of worker processes with their PIDs.

c:\Windows\System32\inetsrv>appcmd list wps

WP "46848" (applicationPool:BerichtenBox Services)

WP "23640" (applicationPool:ird3graphql)

WP "35632" (applicationPool:VervoerSvc)

WP "28616" (applicationPool:MailService)

WP "46452" (applicationPool:DefaultAppPool)

WP "12612" (applicationPool:arno)

WP "29144" (applicationPool:BIG)

WP "15388" (applicationPool:Toa)

WP "46208" (applicationPool:DocumentStorageServices)

WP "35716" (applicationPool:auth3services)

Now it was easy to map the process id to the correct application pool. Next step is to further investigate why this application was causing such high memory usage but that is maybe for another post…

More information

What is w3wp.exe? - IIS Worker Process Explained (stackify.com)

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more