Server 2003 post SP2 update hangs at "applying computer settings"

  • Thread starter Thread starter Jason Knight
  • Start date Start date
J

Jason Knight

Guest
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 Microsoft's
support 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? Any
idea which update broke the server without having to rifle through close to
50 updates?
 
Re: Server 2003 post SP2 update hangs at "applying computer settings"

Can't you install both on different folders and make each using the good one
?
You can have many jre version on the same computer, just need the good
"java_home" for each application.


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Jason Knight" <Jason@legacyroofing.com> wrote in message
news:O$0QpZs$HHA.4568@TK2MSFTNGP02.phx.gbl...
> 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 Microsoft's support 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? Any idea which update broke the server without
> having to rifle through close to 50 updates?
>
 
Back
Top