Hi,
The reason for your issues is described here:
PowerChute Business Edition - Customers Using 6.x Must Upgrade to 7.x
due to Java Runtime Environment expiration
http://nam-en.apc.com/cgi-bin/nam_en...p?p_faqid=7202
It was the reboot after the SP1 for Win2k3 install that triggered
the issue, and not SP1 in itself.
If you still want to use PowerChute, upgrading PowerChute to 7.x
is what you need to do.
Regards,
Torgeir
Chew wrote:
> -- Hi Torgeir,
>
> I found the information. Hopefully it will work. Thanks a lot.
>
> For those who are facing the same problem. Please check your as asked
> by Torgier and visit APC website for more information.
>
> With regards,
> Chew
>
>
> "Chew" wrote:
>
>
>>Hi Torgeir,
>>
>> Thanks for responding. Yup... You are right. Three of them are installed
>>with PowerChute version 6.2. In fact, another two servers which I install SP1
>>successfully are without Powerchute. Are you suspecting this software were
>>causing the problem? Do you have any idea to overcome this?
>>
>> I will try to look for the solution. Thanks a lot. At least I have a
>>clue to search for solution.
>>
>>--
>>With regards,
>>Chew
>>
>>
>>"Torgeir Bakken (MVP)" wrote:
>>
>>
>>>Hi,
>>>
>>>You haven't by any chance PowerChute 6.x UPS software installed on the
>>>servers?
>>>
>>>Regards,
>>>Torgeir
>>>
>>>Chew wrote:
>>>
>>>
>>>>On Tuesday, My staff has installed SP1 on three of my servers but they start
>>>>giving problem when we restarted the server. All with W2k3 Enterprise
>>>>edition. 2 DC and one Exchange 2k3.
>>>>
>>>>First of all, the servers took more than an hour to restart after installed
>>>>sp1. My staff shut down the server and cold booted it. The server then
>>>>stopped at applying computer setting for more than an hour.
>>>>
>>>>Therefore, he shut down the exchange and another dc. He uninstall SP1 from
>>>>the DC with all FSMO roles and Global catalog from safe mode. After restarted
>>>>the server, the problem still persists.
>>>>
>>>>Therefore, I instructed him to start the remaining servers and check the
>>>>connectivity of each server. After that, I managed to connect to OWA to check
>>>>email and send email over Internet. We stop there because it took more time
>>>>to troubleshoot as the reboot time takes about 2 hours.
>>>>
>>>>On wednesday, I have tested the AD with DCdiag and AD seems working fine.
>>>>But, i realize that we can't stop or start an services without turnning off
>>>>the server(Can't shut down because it took too long to restart). Netdiag is
>>>>fine when I test one by one but it hangs if I didnt specify the test.
>>>>
>>>>Moreover, I can't access to network card properties through my network place
>>>>or control panel. The network card setting looks like being locked for all
>>>>servers(with or without SP1). But, i can disable the NIC from device manager.
>>>>I am sure the server was not like that before we installed SP1.
>>>>
>>>>We did uninstall SP1 from the second DC and the condition is same as the
>>>>first DC. I believe the problem is caused by Sp1 is locking the network card
>>>>for some reasons but unable to release the lock. This is because I did a test
>>>>on the Exchange 2k3 by disabling the NIC and restarted it after that. The
>>>>server can reboot to logon screen normally. But, once I enable the NIC and
>>>>restart, the same problem happens again.
>>>>
>>>>Therefore, I hope someone can share thier experience or solution as I can't
>>>>get anything from knowledge base nor send an email to Microsoft for help. $$.
>>>>Hopefully this will be seen by any Microsoft Engineer also. Thank you in
>>>>advance.
>>>>
>>>>
>>>
>>>
>>>--
>>>torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
>>>Administration scripting examples and an ONLINE version of
>>>the 1328 page Scripting Guide:
>>>http://www.microsoft.com/technet/scr...r/default.mspx
>>>
--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx