While debugging webparts , event handlers etc. in sharepoint we may need to attach the w3wp.exe. But the real problem is that to identify which w3wp.exe is for the sharepoint webpage we are trying to debug?, there may be two more w3wp.exe processes. In that time we can attach the two w3wp.exe processes it will work. But it slow down the server performance.

Today I got a solution for this, Microsoft is providing some script files to identify which w3wp.exe process belongs to the sharepoint application pool.

To get the details Go to Command Prompt. Change directory to SystemRoot/System32. Use command cscript.exe iisapp.vbs. <enter> will give you all the application process, with the w3wp process Ids.

W3WP.exe PID: 3848 AppPoolId: SharePoint – 80
W3WP.exe PID: 6044 AppPoolId: SharePoint Central Administration v3

From my machine.

For more details

Which-w3wp.exe-process-belongs-to-which-App-Pool-in-IIS6.aspx