Identifying Worker Process W3WP.exe PID
If you are debugging a ASP.NET web application which is hosted on IIS, you need to attach the particular worker process in Visual Studio to start debugging. To Attach a process we can go to Tools > Attach Process or use shortcut key Ctrl +P. The process window will show the worker process (w3wp.exe) which is currently running on IIS. You need to select the process and click on attach button to start the debugging.
Problem starts when you have multiple worker process running on IIS. If you have multiple sites hosted on IIS and each site having their own application pool then you will see the list of all worker process in the Process Attach window.
Problem starts when you have multiple worker process running on IIS. If you have multiple sites hosted on IIS and each site having their own application pool then you will see the list of all worker process in the Process Attach window.
Here you need to identify the particular worker process which is associated with your application pool.
Identify Worker Process in IIS 6.0
• Start > Run > Cmd
• Go To Windows > System32
• Run cscript iisapp.vbs• You will get the list of Running Worker ProcessID and the Application Pool Name.
• Start > Run > Cmd
• Go To Windows > System32
• Run cscript iisapp.vbs• You will get the list of Running Worker ProcessID and the Application Pool Name.
So, here is your list of all worker process with corresponding application pool name. From the Application pool name you can easily identify which worker process is related with your application.
Identify Worker Process in IIS 7.0
From IIS 7.0 you need you to run IIS Command Tool ( appcmd ) .
• Start > Run > Cmd
• Go To Windows > System32 > Inetsrv• Run appcmd list wp
• Start > Run > Cmd
• Go To Windows > System32 > Inetsrv• Run appcmd list wp
Comments
Post a Comment