Jiwa

If you use System.Diagnostics.Debugger.Launch/Break within the code of a service(Plugin Scheduler or Jiwa API) you may find that the JIT won't launch if there are two users with Admin privileges logged in under windows, it appears the messages appear to whoever was logged in first, even changing the service to run as a specific user won't overcome the issue, I've just discovered this whilst working with a client to overcome some issues as soon as their IT manager logged out the problem disappeared and JIT would launch correctly.

This is posted in case someone else runs into the same problem.