Critical condition for processor and memory at boot up

I have a SBS 2000 Server which is experiencing critical error messages when
it boots up. It appears to be taking too many resources to start up all the
services. After I log in it is a couple of minutes before I can access the
desktop. As soon as I can I open the Admin console to the server status view
and see that Backup Exec and Remote Access services are stopped. Under
Health Monitor Alerts there are several critical alerts for memory and
processor. After I see these errors and start the remaining services, I can
refresh and everything appears normal. The server behaves normally until it
is rebooted again. This Monday Sept 19. I replaced the memory and got the
same problem. I haven't replaced the processor yet and wonder if that
should be my next step.



Here is what the Health Monitor Alerts window shows



Severity--- Critical

Data Collector---- memory

Threshold----Pages input/sec > 5

Alert -----Memory critical condition. WMI status 2147749889



There are several of these listed with Page Read/sec >5, Pages/sec > 80,
listed as well.

Other Data Collectors involve the processor queue length.



Performance counters look normal.



Health Monitor shows a red X on the %Processor time > 75.





Thank-you for your time.





Joy

Applebaum
Wed Sep 28 21:05:53 CDT 2005

Not sure if this is the best idea, because maybe it's a hardware-related
problem, but here's something you could try:

For non-essential services, change them from automatic to manual. Since the
Backup Exec & Remote Access svcs don't fully load, maybe start with all of
them - set them to manual and reboot. Maybe if the problem continues, find
out what services those services depend on, maybe there's a problem with
them.

It's just a thought. Good luck.


"Joy" <joy@caldwellpc.com> wrote in message
news:Ojk5VtGxFHA.916@TK2MSFTNGP10.phx.gbl...
> I have a SBS 2000 Server which is experiencing critical error messages
when
> it boots up. It appears to be taking too many resources to start up all
the
> services. After I log in it is a couple of minutes before I can access
the
> desktop. As soon as I can I open the Admin console to the server status
view
> and see that Backup Exec and Remote Access services are stopped. Under
> Health Monitor Alerts there are several critical alerts for memory and
> processor. After I see these errors and start the remaining services, I
can
> refresh and everything appears normal. The server behaves normally until
it
> is rebooted again. This Monday Sept 19. I replaced the memory and got the
> same problem. I haven't replaced the processor yet and wonder if that
> should be my next step.
>
>
>
> Here is what the Health Monitor Alerts window shows
>
>
>
> Severity--- Critical
>
> Data Collector---- memory
>
> Threshold----Pages input/sec > 5
>
> Alert -----Memory critical condition. WMI status 2147749889
>
>
>
> There are several of these listed with Page Read/sec >5, Pages/sec > 80,
> listed as well.
>
> Other Data Collectors involve the processor queue length.
>
>
>
> Performance counters look normal.
>
>
>
> Health Monitor shows a red X on the %Processor time > 75.
>
>
>
>
>
> Thank-you for your time.
>
>
>
>
>
> Joy
>
>

Joy
Wed Sep 28 21:47:42 CDT 2005

Thank. Sounds like a good start. Will need to try it when I can reboot.

Joy
"Applebaum" <mappleNOSPAM@inch.com> wrote in message
news:ObPrloJxFHA.2516@TK2MSFTNGP12.phx.gbl...
> Not sure if this is the best idea, because maybe it's a hardware-related
> problem, but here's something you could try:
>
> For non-essential services, change them from automatic to manual. Since
> the
> Backup Exec & Remote Access svcs don't fully load, maybe start with all of
> them - set them to manual and reboot. Maybe if the problem continues,
> find
> out what services those services depend on, maybe there's a problem with
> them.
>
> It's just a thought. Good luck.
>
>
> "Joy" <joy@caldwellpc.com> wrote in message
> news:Ojk5VtGxFHA.916@TK2MSFTNGP10.phx.gbl...
>> I have a SBS 2000 Server which is experiencing critical error messages
> when
>> it boots up. It appears to be taking too many resources to start up all
> the
>> services. After I log in it is a couple of minutes before I can access
> the
>> desktop. As soon as I can I open the Admin console to the server status
> view
>> and see that Backup Exec and Remote Access services are stopped. Under
>> Health Monitor Alerts there are several critical alerts for memory and
>> processor. After I see these errors and start the remaining services, I
> can
>> refresh and everything appears normal. The server behaves normally until
> it
>> is rebooted again. This Monday Sept 19. I replaced the memory and got the
>> same problem. I haven't replaced the processor yet and wonder if that
>> should be my next step.
>>
>>
>>
>> Here is what the Health Monitor Alerts window shows
>>
>>
>>
>> Severity--- Critical
>>
>> Data Collector---- memory
>>
>> Threshold----Pages input/sec > 5
>>
>> Alert -----Memory critical condition. WMI status 2147749889
>>
>>
>>
>> There are several of these listed with Page Read/sec >5, Pages/sec > 80,
>> listed as well.
>>
>> Other Data Collectors involve the processor queue length.
>>
>>
>>
>> Performance counters look normal.
>>
>>
>>
>> Health Monitor shows a red X on the %Processor time > 75.
>>
>>
>>
>>
>>
>> Thank-you for your time.
>>
>>
>>
>>
>>
>> Joy
>>
>>
>
>