Provides no clear indication that a version mismatch is the cause of the problem.
In a very similar (yet much more devious) turn of events, we, and Automic Support, invested several hours into debugging a strange Oracle error message.
Turned out this was related to me (shame on me) overlooking a certain combination of LD_LIBRARY_PATH load order, which led to a shared object from an Automic version being used foremost that was one minor(!) version older than the actual engine.
As I said, this kept several people busy for several hours with a very arcane error. Automic Support afterwards supported the idea that there should be some sort of versioning in the shared objects, which I strongly advocated.
It was ruled "works as designed" by product management IIRC, and at best can be requested as a new feature (which it won't, because nobody votes).
FOKUS: Versioning of the AE shared objects
Best regards,
Carsten