What Windows process to kill to stop CGItask?

TS 6.5/SP3, Windows Server

I've got a misbehaving CGI task that hangs. I can click "cancel" to close the window but a task process continues to keep the IPL file open (so I can't fix the bug and save the file). Killing the "IW_CGI~1.CGI" process (and another similarly name process I forgot the name of) does not do the trick.

Short of rebooting, how would one completely eradicate all processes related to the CGI?

Thanks!

Find more posts tagged with

Comments

nipper

What is the CGI that you are running ? Is it a custom ipl that you wrote ? Custom app ?

LeggMan

It's a custom CGI that didn't hang until I put some debugging code in it.

The form displays properly but after I click the transition task button the thing just hangs... it doesn't eat up cycles, just sits there. Clicking the cancel button closes the window but some process still lives and keeps a handle on the IPL script of the CGI so I can't save a new version of the file over it.

I've opened a support case asking for the name(s) of the Windows process(es) I should kill to free up the IPL script. (This was much easier to figure out in Unix.)

nipper

It *may* be an instance of iwperl that you need to kill. Any one hanging out long ?

moonkhanna

It's a custom CGI that didn't hang until I put some debugging code in it.

I've opened a support case asking for the name(s) of the Windows process(es) I should kill to free up the IPL script. (This was much easier to figure out in Unix.)

If you use task manager, it is simple in windows as well :-)

LeggMan

It *may* be an instance of iwperl that you need to kill. Any one hanging out long ?

IWOV TSE Santosh Shamsundar correctly counseled me to restart the Web Daemon service so fastCGI would release the lock on my file... interesting that I could not simply identify and kill an iwperl or other process to do so.

Migrateduser

If you download process explorer from sysinternals.com (now part of Microsoft), you can inspect the arguments that were passed to any running process. I have found that useful for killing off errant external and cgi task scripts. Since you had to kill FastCGI, it may be that iw-webd is now running cgitasks in the context of the hosting apache process rather than forking a process. It's been a few years since I've had a misbehaving CGI task.

LeggMan

If you download process explorer from sysinternals.com (now part of Microsoft), you can inspect the arguments that were passed to any running process. I have found that useful for killing off errant external and cgi task scripts. Since you had to kill FastCGI, it may be that iw-webd is now running cgitasks in the context of the hosting apache process rather than forking a process. It's been a few years since I've had a misbehaving CGI task.

Thanks for the tip.