Task Manager kill vs. VB killProcess(pgm)

Me_again · Post by **Me_again** » Sat Jan 20, 2007 5:13 am

I wrote someone a simple utilty that runs regularly to kill processes left behind by an application that runs at intervals but often crashes. (I know, I know, the guy should try and get the real problem fixed but...)

If the processes are killed from task manager they just go away, but killing them with the killProcess(pgm) vbscript subroutine generates an error message popup:

quote:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 1/19/2007
Time: 9:37:02 AM
User: N/A
Computer: DELL
Description:
Application popup: Layered Hidden Window: badapp.exe - Application Error : The instruction at "0x10005c38" referenced memory at "0x00000ba0". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program
unquote:

Any suggestions how I can avoid this?

JRL · Post by **JRL** » Mon Jan 22, 2007 6:52 pm

Have you tried or thought about using DOS taskkill?

Me_again · Post by **Me_again** » Mon Jan 22, 2007 8:10 pm

No, I hadn't, I'll look into it, thanks!

I used to use sysinternals pskill but that means delivering a separate app with the (compiled) macro so the vbscript version is more convenient. Seems only the latest version of the problem application causes that hidden error popup, so this just gets weirder.