Hi,
We have finalbuilder scripts which release our websites (ISAPI DLLs) into IIS 6.0. Most of the time the scripts run fine but 20% of the time they fail because the w3wp.exe process for a website has not stopped/closed gracefully (and can seen running via the task manager). The script needs this process to have gone so the rest of the script can do what it needs to do.
Has anybody got any ideas or things I could try to ensure the process closes or to kill the process off if it lingers around?
Below are the actions we use in our scripts to stop a website and associated application pool in IIS 6.0. They run in the order they are listed.
- [Prior actions]
- Stop Website (IIS 6) action
- WMI Run Process action which runs a vbscript which stops the application pool
- Unload IIS Application (IIS 6)
- Delay 10 seconds
- [Post Actions]
Thanks
Jeff