Re: Windows 2008 SBS - Intermittent Server Lockup / Non-Responsive

Sounds good. My fingers will be crossed for you.

If yours behaves anything like ours, you may run into some 'aftershocks' after a week or two (possibly a month - hard to remember). In our case, the various updates and hotfixes that I installed initially seemed to clear up the problem, but then it reared its ugly head again just about when I was ready to call it 'fixed'. That led me to install the rest of the hotfixes and updates I listed, which *knock on wood* seems to have cleared up the issue (it hasn't happened again since early April), but I don't think I'm going to consider it 100% fixed until SP2 gets installed (just in case there are any new revisions to the hotfixes and/or other fixes in the SP).

Speaking of which - does anyone have any firm date for Vista/2008 SP2's availability? I've read 1/2 a dozen articles that say it's RTM now, but I called Microsoft to ask and the person I spoke to said it was still in Beta... Did it get 'un-RTM' for some reason?

-d


"Nick_CHIPS" <NickCHIPS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4571528F-9C03-4635-B604-E93D734BC502@xxxxxxxxxxxxxxxx
Ran the following Hot Fix:
951116
Installed all waiting Windows and Microsoft Updates
Installed all Office updates

System has been running smoothly since then - It has been about 1 week

Will continue to monitor the issue

"David Levine" wrote:

HP ILO is their "Integrated Lights Out" management functionality. You can
connect 'out-of-band' (i.e. it has its own ethernet port/IP address etc.)
when the server's locked up to reboot and/or remote-control the server. It's
been very handy in situations where Windows locked up and/or RDP wasn't
responsive, but it's got its own hooks into the hardware that apparently can
sometimes cause the OS to be unhappy.

Definitely let me know how it goes - I'll help if I can...

-d

"Nick_CHIPS" <NickCHIPS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:41318325-4869-4A33-B76E-33CB4211989A@xxxxxxxxxxxxxxxx
> David,
>
> This sounds similar to the issue we are having.
> The server will continue to function correctly if a workstation does > not
> log
> out. Once a workstation disconnects from the server or the network it > is
> not
> able to reconnect to Exchange or shared resources or even log in.
>
> I will check the drivers and firmware on the box -
>
> What does the HP ILO do?
>
> I will also check the HotFixes and let you know how it went!
>
>
> "David Levine" wrote:
>
>> We had something similar happening at our site - unfortunately several
>> different things were thrown at the server to try and iron the problem
>> out,
>> so I'm not sure which (if any) might apply to you. In our case it >> seemed
>> almost 1/2 operational - Exchange and MMC stopped responding, new >> network
>> connections coulnd't be established, but existing ones continued >> working
>> okay.
>>
>> First stop was updating all of the HP firmware & drivers. Our affected
>> box
>> was an HP Proliant ML370G5. HP ILO in particular has been known to >> cause
>> weird hangs when its version is not happy with the OS version.
>>
>> Second stop was about a dozen released/unreleased updates & hotfixes >> from
>> MS:
>>
>> 949700, 950927, 951116, 951246, 951720-v2, 952178, 952664-v3, 952709,
>> 953153, 953186-v2, 956519, and 959489. Some are the
>> 'unreleased/unsupported'
>> hotfixes that probably won't be blessed until SP2 is final, but I >> haven't
>> seen any issues from them yet here - several address performance >> issues.
>>
>> That seemed to clear it up for the most part, until recently when our
>> SBSMonitoring SQL database decided to become a resource hog and start
>> monopolizing on all disk access, which in-turn ground the network to a
>> halt.
>> I'm still working on trying to figure out what's behind that issue, >> but
>> we've been able to stay up and available as long as I've got the >> instance
>> stopped/disabled. We just don't have any access to the reporting >> features
>> in
>> the meantime.
>>
>> HTH,
>> -d
>>
>>
>> "Nick_CHIPS" <Nick_CHIPS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:009DB7D4-6265-48E8-A99C-5D74353FEABD@xxxxxxxxxxxxxxxx
>> >I have 2 Servers at different locations:
>> > Both are Windows 2008 SBS / Exchange is used /
>> > 1 is a physical install / 1 is a virtual install
>> >
>> > Both servers will stop allowing access to shares, email and logins
>> > intermittently.
>> > The servers are monitored 24/7 and all services and connections >> > report
>> > in
>> > normally.
>> >
>> > The mouse and keyboard stop responding and a remote connection into >> > the
>> > system is not allowed.
>> > The only way to correct the issue is to hard reboot the system.
>> >
>> > I have not seen any events logged in the event viewer that provides >> > any
>> > detailed information.
>> >
>> > Has anyone ran into this before?
>> >
>>


.

Relevant Pages

  • Re: FYI for eTrust AV 7.x Users
    ... When I just had my little incident with the redistribution settings on the SBS, my clients were logging successful checks for updates, and the logs indicated that no updates were found. ... That turned out to be because I had not gone back and checked the redistribution server box for 8.x after reinstalling the redistribution server. ... installed the new remote install utility which works the same as v7 did - just edited the .ICF file the way I wanted it and ran the client upgrades from the server. ... I can't remember if it's a separate install, or if you have to click a box when you do the Agent install, but redistribution server is not installed by default. ...
    (microsoft.public.windows.server.sbs)
  • Re: SUS
    ... > I have setup a SUS Server on win2k. ... 0-2.reg will not configure your machine to automatically download updates from ... critical updates or service packs that your machine needs. ... It will also ask you if you want to install them, ...
    (microsoft.public.windows.server.general)
  • Re: Disaster Restore SBS2003
    ... If you had the server set to download updates automatically (never ... then install any service packs to return the server to the same service pack ... have the correct version of NTBackup prior to the restore. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
Loading