Link to home
Start Free TrialLog in
Avatar of rustyrpage
rustyrpage

asked on

Kill process if it is older than 30 seconds

We have a shipping application that our ERP vendor has written that has a bug in it when it interfaces with a third party USPS module.  Basically, the ERP system passes off an XML file to the third party USPS application, which runs, prints the label & then closes out.  The problem is that if there is any error, it will just lock up the whole application & someone with server access has to go in & kill the EXE.  So, I have two options to fix this:

1) Make a scrip that checks to see if dazzle.exe has been running for more than 30 seconds & if so, kill it.  (how intensive would this be from a resource standpoint?)

2) Make a shortcut that our shipping folks can click on that would kill dazzle.exe on the server (keeping in mind that they obviously are not admins on the server, so I would have to determine a secure way to get around that)

Any help would be greatly appreciated.
Avatar of gtworek
gtworek
Flag of Poland image

The first one is relatively easy with powershell. Is powershell solution acceptable for you?
Avatar of rustyrpage
rustyrpage

ASKER

What are the cons/downsides?  How much of a performance hit is there?
Powershell takes some resources and has to be installed on 2003.
You an use simple script checking start time for your process and killing it. This script has to be launched periodically.
How would you like to launch your solution? Maybe Task Scheduler is an option? If so - entire solution has acceptable performance impact.
ASKER CERTIFIED SOLUTION
Avatar of oBdA
oBdA

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial