Fritch84
asked on
SBS 2003 - Processor Activity Alert
Hi All,
I just got an alert from my SBS 2003 server that I'm hoping someone could help me ascertain the reason/s. Here is the alert message:
'The processor is experiencing a low level of idle time. Consistently low levels of idle time can cause performance problems. Use Task Manager to view the top processes by CPU. If a service or less important process appears to be unusual, try stopping and then restarting it. You can disable this alert or change its threshold by using the Change Alert Notifications task in the Server Management Monitoring and Reporting taskpad.'
After reading this thread - https://www.experts-exchange.com/questions/21709242/Windows-SBS03-SP1-The-processor-is-experiencing-a-low-level-of-idle-time.html
The alert seemed to be caused by services 'hogging' the processor as displayed in the performance report using 100% cpu time. This is what makes my alert seem strange to me - the top 5 processor services displayed in my report were just;
upsis - 5.8 %
svchost - 2.0 %
StorServ - 1.5 %
wmiprvse - 1.0 %
services - 0.9 %
However, when I look at task manager of the server the 'System Idle Process' is hovering between 60-75. What does this mean and should I be concerned?
I just got an alert from my SBS 2003 server that I'm hoping someone could help me ascertain the reason/s. Here is the alert message:
'The processor is experiencing a low level of idle time. Consistently low levels of idle time can cause performance problems. Use Task Manager to view the top processes by CPU. If a service or less important process appears to be unusual, try stopping and then restarting it. You can disable this alert or change its threshold by using the Change Alert Notifications task in the Server Management Monitoring and Reporting taskpad.'
After reading this thread - https://www.experts-exchange.com/questions/21709242/Windows-SBS03-SP1-The-processor-is-experiencing-a-low-level-of-idle-time.html
The alert seemed to be caused by services 'hogging' the processor as displayed in the performance report using 100% cpu time. This is what makes my alert seem strange to me - the top 5 processor services displayed in my report were just;
upsis - 5.8 %
svchost - 2.0 %
StorServ - 1.5 %
wmiprvse - 1.0 %
services - 0.9 %
However, when I look at task manager of the server the 'System Idle Process' is hovering between 60-75. What does this mean and should I be concerned?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This could be caused by your system not having enough RAM installed, or your hard disk access being slow or indeed both. SBS has some out of the box default limits set in the Monitoring and Alerts section in the SBS Admin console, these limits can be safely adjusted to higher values to stop the alert popping up but this should only be done if you simply don't have the money to spend on upgrading the hardware. What is the UPSIS service ? I don't recognise that as a standard SBS service ?
ASKER
Thanks for your suggestions guys (sorry for the delayed response - different timezones?).
I need to edit my OP - the process performance %'s were from the day earlier. The report generated the next day showed that the UPSIS service as the 'errant process' hogging the resources.
Realtec: the upsis service isn't a default app - it's from a third-party UPS (power protection).
Now that I know exactly what process is giving me the error - I'll check their site for an update. No new updates\programs were installed on the server recently, which makes this 'hiccup' strange.
I need to edit my OP - the process performance %'s were from the day earlier. The report generated the next day showed that the UPSIS service as the 'errant process' hogging the resources.
Realtec: the upsis service isn't a default app - it's from a third-party UPS (power protection).
Now that I know exactly what process is giving me the error - I'll check their site for an update. No new updates\programs were installed on the server recently, which makes this 'hiccup' strange.
ASKER
The service is working fine now.