We have seen this issue at several clients. If you look at the running processes on the iMan server you should see a large number of iMan *32 and once we clear these out the process starts again. There is a bug in the software that cuases this to occurr if a transform fails and then more keep running after the initial failure.. We have a script on sites that 'kills' the process after the transform runs to ensure they do not stack up

I did end up working this out for myself and found killing the Intengine process removed them all, it does not happen that often but was good to have it confirmed. Do you have a link to the script and will this be addressed in the next version of Iman?

This has started to happen more regularly on our system, can you supply a script that closes these down?

We just use 

<pre class="wps_code">taskkill /f /im "IntEngine.exe"

<pre class="wps_code">taskkill /f /im "IntEngine.exe"

That kills all the processes. Alternatively you can just right mouse click the process and chose End Process Tree as this sometime kills the whole lot!

Thanks Phil, we have been doing it the manual way which has been getting us out of trouble for now. I believe I have found the root cause for us which was an integration that was set for a only a single instance but on a 5 second timer, when the integration took longer than normal  and subsequent instances of the integration we called upon it would as you would expect these but quite quickly leave a number of open processes, hope this may help your customers.

Having this issue NOW too....started out of no where. Works a bit after restarting server then craps out again. Help! Stopping at restarting IMan services does not solve the issue.

Hi Ipage, you need to kill the Iman processes from process manager or alternatively upgrade to v3.2 to fix the issue

Ok great, thank you for the info Browndog!

So. After successfully updating to V3.2 I am still having this issue and having to kill the processes occasionally....any ideas?

^^bump^^  Support?