User 0261d34ad7
23-01-2012 09:40:14
Hi,
I'm bouncing this topic - I replied to a previous post but I think the question I was asking may have been missed....
https://www.chemaxon.com/forum/ftopic8622.html
We've hit the same exception in 5.7.0 (when connecting remotely), and the only way we could solve the problem was by copying chemaxon-status.jar from 5.8.0.
It would be great to know if there is a better solution we can adopt...
Jim