This really begs the question - why or where are you getting error messages? The point being, you should ** ALWAYS ** make your code do the work itself and never the client.

Can you post the code you have at this point?

With KiXtart 4.22, or better you could use the macro @PID to report back the PID of KIX32.EXE/WKIX32.EXE via scheduled task and notify you of any message boxes that have been running longer than say 30 minutes.. In you scheduled task, you script would be something like this {pseudocode} -

code:
IF machine-x and Flag exist
 Notify
ELSE
 If machine-x @PID at @TIME and @DATE = KIX32.EXE
  Set a FLAG
  ENDIF
ENDIF
Is this what you are looking for?

HTH,

Kent
_________________________
Utilize these resources:
UDFs (Full List)
KiXtart FAQ & How to's