Paisleymll
MIS
Hello -
I'm curious if anyone has seen this type of issue or might have a suggestion on where to look.
I am initiating macros via a Command line. (EG. EBrun.exe Macro.ebm) The macro will open the session to the host and close the session at the end. At this point, when the macro is completed EbMngr.exe and Ebrun.exe processes close themselves. But I'm finding cases where this isn't happening, and after the macro finishes, EbMngr.exe creates a constant load on the CPU until the process is terminated. From my output files I can trace the macros progress to the 2nd to last line. I'm stumped on how to isolate this occurence and either kill the process or preferably prevent it.
I'm curious if anyone has seen this type of issue or might have a suggestion on where to look.
I am initiating macros via a Command line. (EG. EBrun.exe Macro.ebm) The macro will open the session to the host and close the session at the end. At this point, when the macro is completed EbMngr.exe and Ebrun.exe processes close themselves. But I'm finding cases where this isn't happening, and after the macro finishes, EbMngr.exe creates a constant load on the CPU until the process is terminated. From my output files I can trace the macros progress to the 2nd to last line. I'm stumped on how to isolate this occurence and either kill the process or preferably prevent it.
