Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1208
  • Last Modified:

SBS 2003 Monitoring - "Critical condition. WMI Status: 8 Timeout reached. The system may be busy and unable to service the request or the data collector may be misconfigured."

I have a sick SBS 2003 machine which is spitting out a heap of alerts (created with Reporting & Monitoring) which I need a hand on.

There are two main errors that I am seeing:
1. Critical condition. WMI Status: 8 Timeout reached. The system may be busy and unable to service the request or the data collector may be misconfigured.

2. Critical condition. WMI Status: 2147749889 Enumeration failed. Object not found. Data Collector is misconfigured. 0x80041001

I am receiving these alerts for a lot of different components: Server Memory, Paging File, System Information etc.

I have followed the KB below:
http://support.microsoft.com/default.aspx?id=300956

But still seeing these errors - I dont care about keeping the data from the past, so if there is a way to clear data and configure then that is fine .... thoughts?
0
Flipp
Asked:
Flipp
2 Solutions
 
Shreedhar EtteCommented:
Run SBS 2003 Best Practise Analyser tool and fix the errors reported.

Post the event decription.
0
 
FlippAuthor Commented:
Server is being replaced in next two weeks so not looking at this issue at the moment.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now