Re: Server stops responding

Well, the sorts of things that could cause this in hardware include
overheating, RAM problems, etc. One obvious thing to do is open up the case,
re-seat every board, DIMM and cable, and carefully remove all the dust in
the case. And you might want to run a RAM tester and/or a utility that will
report the various temperatures...

--
Charlie.
http://msmvps.com/xperts64


"Bill Glidden" <billyg1943@xxxxxxxxxxx> wrote in message
news:OOnneKeQHHA.1908@xxxxxxxxxxxxxxxxxxxxxxx
Hi Charlie,
No RAID on this box, but it sure looks like hardware as you suggest. This
is a couple year old Compaq Evo D51S with zero fault tolerance. I guess I
have been lucky to have gotten away with running my business on this box
for so long ;-) Time to upgrade, I fear.
Cheers,
Bill

"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1BF56836-38B1-421B-9ED2-D9C7D9882807@xxxxxxxxxxxxxxxx
One other thing to look at, IF you've got a matching scenario. There are
known issues with low end onboard RAID controllers that do mirroring.
They can cause complete system lockups exactly as you're describing, with
nothing in the event logs to indicate the problem (since it's actually a
hardware problem.) I have one client with this scenario who has learned
to reboot his SBS server twice a week. If he waits >5 days, he's hitting
the power button. We've discussed replacing it with a standalone RAID
card, but he's considering a whole new server anyway and is holding off.

--
Charlie.
http://msmvps.com/xperts64


"Bill Glidden" <billyg1943@xxxxxxxxxxx> wrote in message
news:%238PGU1bQHHA.2252@xxxxxxxxxxxxxxxxxxxxxxx
Thanks, Anna!
You have given me more than enough stuff to be going on with, but all
makes sense to me. I'm not used to SBS doing bad things and not telling
me why it is doing it. This box has been reliable as one could wish
since it was built over a year ago. I have to 'fess up and tell you
that it is an under-speced PC with not enough RAM that I run my office
on. I would never do this to one of my clients! Does show however that
SBS will run OK on almost anything if you don't make too many demands of
it.
Cheers,
Bill

"Anna Clark" <anna.clark(remove this)@verizon.net> wrote in message
news:u0vkZvbQHHA.496@xxxxxxxxxxxxxxxxxxxxxxx
Hi Bill:

Start with the knowledge that such behavior is not what most of us
would
expect from a Windows 2003 server, and not what we would expect from a
SBS
2003 Server. The usual causes of faulting of a Windows server result
in a
BSOD, not a lockup. BSODs causes include such things as corrupted
drivers
and errant programs or drivers stepping on each others space in RAM.

Now, what could be causing your lockups? There are so many
possibilities
that to list them here would take many contributors and lots of posts.
Since there are so many possibilities, how to sort them?

Not necessarily in any order, I will add them as I think of them:

- I would run msconfig and stop any and all services that I could live
without for a few days. If the problem goes away, restart the services
according to the 50-50 rule.

- I would uninstall any programs and Windows components that I could
live
without

- I would consider if the power supply was adequate for the load on the
system.

- I would consider replacing the RAM

- I would verify that there was at least 25% free space on each
partition.

- I would run chkdsk /r on all volumes.

- I would search for all BIOS updates and all driver updates for the
hardware in that system and apply them.

- I would migrate to new hardware... identical if possible/practical,
otherwise see www.sbsmigration.com

- I would get some eye of newt, some wing of bat, some dragons breath,
and
some hair of Bill
(oh, wait, that is for my ex)

- I would consider if the timing of the lockup was significant...

- I would investigate creating performance monitors to see if I could
find a
pattern.

- I would solicit advice from others in this forum which, by necessity,
will
be more focused than the above.

--
Regards:

Anna Clark
-----
Please do post the conclusion or solution
to your issue so that others may benefit.


"Bill Glidden" <billyg1943@xxxxxxxxxxx> wrote in message
news:%23hJkocaQHHA.3592@xxxxxxxxxxxxxxxxxxxxxxx
SBS2003 SP1 Premium Edition server. This server has become unstable
recently. It stops responding and requires a powereon/off cycle to
recover
(echhh!). Nothing in the event logs that would indicate why this is
happening. This has happened twice in the last week.
Can someone please give me a hand with this?










.