Java conflict? (BES 4.1 and APC PowerChute 7.05)
843790Sep 21 2007 — edited Sep 25 2007First off, I'm not sure if this is the right place to be posting this, but I have some issues that I need addressed.
I've got a situation that requires some describing. We recently upgraded our BES server from W2K to W2K3 standard. All went well during and after the upgrade. We installed SP2, everything's fine. We install post-SP2 updates, and everything's not fine. Upon reboot, "applying computer settings" just hangs there eternally. Two minutes later I find a KB article on M$ site:
http://support.microsoft.com/kb/905716
It refers to using PowerChute version 6.x which had a packaged version of Java 1.2.1 that had a digital certificate that expired in 2005. We never had version 6.x on this machine, we started with Powerchute 7.04 and had no problems until post-SP2 installation. Unfortunately, we're not sure which update broke it either, there were a good number of them.
So, we upgraded from 7.04 to 7.05, which comes with the packages jre1.4_11. Apparently, PowerChute only works with it's packaged version and does not like Java Runtime 6 update 2! And BES MDS services won't start without jre1.6_02 installed! I tried editing the registry key for the MDS services to point to the jre1.4_11 in the PowerChute jre directories and no go! Also tried it the other way around, and edited the PowerChute registry keys to point to jre1.6_02's jvm.dll with a no go. I setup PowerChute the way it is on our other two servers, with NO OTHER jre installed whatsoever, and it works fine. What can I do to make BES and PowerChute live together?