We have just released patch 126.96.36.199:
Agent Update 188.8.131.52
The patches below require updating the agent version to 184.108.40.206 for Windows, Mac and Linux agents. (NINEFOURPT-368)
Virtual System Administrator™
Critical Issues For Customers To Patch Immediately
We broke our VSA with patch .18. Turned out we needed to update Java. Just a heads up to anyone else who might see issues - in our case two services wouldn't start on the VSA - KaseyaMobileGateway, and (I think) Kaseya Event Service.
We were still on Java 1.7 u 58 (from memory) and going to Java 1.8 u 131 fixed both immediately.
@Craig Hart so you went with the latest version of Java and it worked? I remember a previous version of Kaseya would not run on JRE 8 AND required JRE 7 well after 8 had become the only available download from Java.com . This is great news if Kaseya is finally updating to JRE 8! (I hate keeping outdated Java on a public facing system)
Kaseya 9.3.31 still requires java 7 and does not work on java 8.
Thanks Craig Hart for finding that out for us. It would be nice to hear some validation from Kaseya to reiterate/validate the change of supported Java version. Nicolas Ponce ?
I can confirm that 9.4 only uses JAVA for EMM (Mobility) for the Kaseya Directory Integration Service.
No other components should leverage java in 9.4.
This was addressed previously, as Craig Hart created a thread on this specific topic for 9.3:
I have not heard or seen any new issues from my side of things with Java.
However, I have seen java.exe processes not stopping/releasing connections which can cause similar issues to which Craig is describing, which are usually fixed by killing off any java.exe processes still running and then cycling services. If you run into a similar situation, I would review the Directory-webservice.log file in X:\Kaseya\Logs\Services directory prior to uninstalling or changing any configuration.
Nicolas Ponce - Excellent follow up! Thanks for the clarification!