WBEM error during Data Collection

[Jeff Cottrill_1]

Didn't get much the first time I posted, so I'll try again...

A couple my servers give me the following error during Data Collection:

"[WBEM] Unrecoverable problem encountered while handling WBEM data coming from this system.
Root Cause: Possible problem with the WBEM provider on the target system.
Corrective Action: Rerun Identification and Data Collection if necessary.

An unexpected general error occurred during data collection. Data may be incomplete.
Root Cause: Refer to any accompanying, more specific, lower level, error messages that precede this one.
Corrective Action: Refer to any accompanying, more specific, lower level, error messages that precede this one."

1 server is an ML370 G3 running Windows Server 2003 SP2 std with PSP 8.15A, plus the latest SMH (3.0.0.64) and WBEM Providers (2.2.1.0). Another is an ML370 G4 running Windows Server 2003 SP1 std with PSP 8.0, plus the latest SMH and WBEM Providers.

The Identify System results state "Running WBEM rules based identification" and "Got ComputerSystem WBEM/WMI data from the system", which would seem to indicate that SIM can connect to it via WBEM/WMI ok. This seems to only affect Data Collection (and Data Collection Reports, where a few entries such as OS and Memory are missing). Accessing the WMI data from the affected servers' System Pages in SIM works fine, however, and all of the information is there, including what is missing from the DC Report.

I've tried completely removing the affected servers from SIM and re-adding them (via both the GUI and CLI), verified the credentials (via both the GUI and CLI), restarted WMI services on the target servers and the CMS, restarted the WMIMapper service on the CMS, and verified that WMI is working ok on the targets via other tools. I have reinstalled the SMH and WBEM Provider Agents, and have removed the SNMP-based agents.

Basically, I can't see any significant difference between this system and the others that are not having this problem. I'm currently running SIM 5.3, but this problem existed when I was still on 5.2 SP2.

I'm at a loss.