Link to home
Start Free TrialLog in
Avatar of HiThere
HiThere

asked on

Stopping AxtiveX.exe from another application

I have written a ActiveX.exe that handles my ASP requests on the server.

Is there a possibility to stop the ActiveX.exe process from another programme (also from an ASP page) when it has hung up?

I have tried the EnumProcesses API to retrieve the process handle of the ActiveX.exe, but the handle does not appear in the list.

Any ideas ?
Avatar of CJ_S
CJ_S
Flag of Netherlands image

Wouldn't it be better to find the error in the ActiveX executable instead of working around the problem?

CJ
Avatar of HiThere
HiThere

ASKER

Thanks CJS,

I have checked that and I could not find a bug. I have even created an error-log to track errors of each routine in the programme to see what might be wrong. The programme works fine for several weeks and then, for unknown reasons, hangs up. On the development server I never had this problem.

I thought that it might be a bug in ASP server extensions on this server, as it does not even allow  Sever.CreateObject("ADODB.Connection").
I think something is really wrong. Try applying all latest hotfixes, security rollup packages and service packs. Look at http://www.microsoft.com/downloads/release.asp?releaseid=31154 to see what fixes you can use.

I don't think you can reach for the activex exe and shut it down. Since it already hangs you cannot send a new event to it.

Sometimes the data is the error. Are you sure that all data that goes through the application is valid? Have you checked every possibility? I myself had such a simple error. It was the backoffice of a site retrieval system. It ended up playing the MPEG's on the server which eventually hung. I think it's a good idea to check the data... especially if al goes fine on the development server.

CJ
Avatar of HiThere

ASKER

CJ S,

Thanks for the advice. I will check the data and the try  hotfixes. This might take a few days. I will keep you posted.

Regarding the remote termination of the process, I believe it shold be possible by identifying the process-handle of the activeX.exe and close it using API. Just like one terminates the process with the NT task-manager. I thought that this would temporarily solve my problem until I have checked all possible configuration and version errors.
ASKER CERTIFIED SOLUTION
Avatar of rkot2000
rkot2000

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
Avatar of HiThere

ASKER

Thanks rkot2000.

This gets me closer towards solving my problem. I will try to increase the threads in my ActiveX.exe and see if this solves the problem. Maybe I have an opportunity to move to WIN2000 server with ISS5. The article you referred to talks about the problem only in ISS4. If all this does not help, I will probably have to convert my programme into ActiveX.dll.

Thanks again.
TP