Identify Worker Process

This post is directly from  Abhijit Jana’s blog

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.


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

Failure adding assembly to the cache: Cannot create a file when that file already exists

So trying to add a Timer Job to the GAC causes:

“Failure adding assembly to the cache: Cannot create a file when that file already exists”

How do you get around it? well, try these things

1. if you have any dos windows/windows explorer windows in the assembly folder (or deeper) then move out of those folders (or close the windows down)

2. if you have Visual Studio open, and your project has a reference to your assembly, then you will need to close this down. Give it a while tho, even once your VS 200x has disappeared it is still unloading in the back ground

3. GacUtil /cdl – clears the assembly cache

4. do a IIS reset, if you have used the assembly in any web applications

5. reboot :'(

Thanks to Victor