Server 2003 JView Update and APC Power Chute software conflict

I wanted to bring attention to the JView update on Server 2003 (standard Ed)
running any APC PowerChute apps. We have encountered several of our
customers that run PowerChute and have updated with the JView Windows Update
then when applied and reboot the server, the OS will hang at applying setting
stage. After spending many hours on the phone with Microsoft support this
was found to be the error. If you uninstall the JView update or boot into
safe mode and disable any PowerChute (APC) services it will boot fine.
Anyone else see this yet? it happened with oen client then for the next two
days we received calls and had to do one of the following I just mentioned.
I wanted to alert anyone in the same situation so they will be aware.

dear psanborn:

i have had the same issue on windows 2000 server, after doing a windows
update on aug 1 that included the jview update and a couple other updates, my
server would hang when trying to open the windows update website, and no
other sites would hang, and a couple of other services would hang and not
function properly as well. my software vender for my Nextech software, which
was one of the services affected, found it was the APC software that was
interfering and he had me stop the APC in safe mode as you suggested, this
has cured our problem but now i am awaiting my hardware guy to come in to see
what we can do to still have the auto shut down in case of power failure.
anyway, thats my story, and i am sticking to it Maria

"psanborn" wrote:

> I wanted to bring attention to the JView update on Server 2003 (standard Ed)
> running any APC PowerChute apps. We have encountered several of our
> customers that run PowerChute and have updated with the JView Windows Update
> then when applied and reboot the server, the OS will hang at applying setting
> stage. After spending many hours on the phone with Microsoft support this
> was found to be the error. If you uninstall the JView update or boot into
> safe mode and disable any PowerChute (APC) services it will boot fine.
> Anyone else see this yet? it happened with oen client then for the next two
> days we received calls and had to do one of the following I just mentioned.
> I wanted to alert anyone in the same situation so they will be aware.

"psanborn" wrote:

> I wanted to bring attention to the JView update on Server 2003 (standard Ed)
> running any APC PowerChute apps. We have encountered several of our
> customers that run PowerChute and have updated with the JView Windows Update
> then when applied and reboot the server, the OS will hang at applying setting
> stage. After spending many hours on the phone with Microsoft support this
> was found to be the error. If you uninstall the JView update or boot into
> safe mode and disable any PowerChute (APC) services it will boot fine.
> Anyone else see this yet? it happened with oen client then for the next two
> days we received calls and had to do one of the following I just mentioned.
> I wanted to alert anyone in the same situation so they will be aware.

I just experienced this problem last night on 3 servers, all running the APC
power chute sofware. Thank you for your post otherwise I would have been
troubleshooting this for days. I am going to remove the jview update when
and if I able to log back into these servers. I am going to check APC to see
if they have released any sort of patch to fix this problem. I'll let you
know.

"psanborn" wrote:

> I wanted to bring attention to the JView update on Server 2003 (standard Ed)
> running any APC PowerChute apps. We have encountered several of our
> customers that run PowerChute and have updated with the JView Windows Update
> then when applied and reboot the server, the OS will hang at applying setting
> stage. After spending many hours on the phone with Microsoft support this
> was found to be the error. If you uninstall the JView update or boot into
> safe mode and disable any PowerChute (APC) services it will boot fine.
> Anyone else see this yet? it happened with oen client then for the next two
> days we received calls and had to do one of the following I just mentioned.
> I wanted to alert anyone in the same situation so they will be aware.