|
-
Apr 19th, 2004, 12:21 PM
#1
Thread Starter
New Member
Killing Process [constraint of timestamp]
I have a Class file deployed on Win2000 Server in form of a DLL which
generates Excel Report.
Many clients can generate the excel report concurrently. Sometimes one or two
of the Excel process gets hang up.
I need an application in VB(running on Win2000 Server) which only checks for
the process "Excel.Exe" (there may be many excel.exe running in the task
manager at the same time) and if the time-stamp of that is greater than 60 sec. ,
i need to kill that Excel.Exe process without disturbing other Excel.exe or other
processes.
Regards,
-
Apr 20th, 2004, 09:56 AM
#2
You shouldn't need to do any of this. How are you closing down your excel objects from memory from your code?
-
Apr 20th, 2004, 10:05 AM
#3
Thread Starter
New Member
Killing Process [Constraint is Time Stamp]
Its necessary to do that...
The problem is if 3 or 4 process of Excel hangs up at the Server they restrict all the others (reports) to be created.
So i need to kill only those which are hang up.
The time to generate the excel in worst condition is : 40 sec.
So if it takes more than that it means it is hang up.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|