HP ProLiant DL160se Microsoft Windows Event ID and SNMP Traps Reference Guide - Page 27
Log Message: The External Status MIB Agent is not loaded. Sets are not available. The data contains
View all HP ProLiant DL160se manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 27 highlights
Event identifier: cpqhsmsg.dll - 4407 (Hex)0x84351137 (Service Event) Log Severity: Warning (2) Log Message: The External Status MIB Agent is not loaded. Sets are not available. The data contains the error code. Event identifier: cpqhsmsg.dll - 4608 (Hex)0x84351200 (Service Event) Log Severity: Warning (2) Log Message: Unable to allocate memory. This indicates a low memory condition. Rebooting the system will correct this error. Event identifier: cpqhsmsg.dll - 4609 (Hex)0x84351201 (Service Event) Log Severity: Warning (2) Log Message: Could not read from the registry sub-key. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqhsmsg.dll - 4610 (Hex)0x84351202 (Service Event) Log Severity: Warning (2) Log Message: Could not write the registry sub-key: "%1". This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqhsmsg.dll - 4611 (Hex)0x84351203 (Service Event) Log Severity: Warning (2) Log Message: Could not read the registry sub-key: "%1". This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqhsmsg.dll - 4612 (Hex)0x84351204 (Service Event) Log Severity: Warning (2) Log Message: Could not read from the registry sub-key: "%1". This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqhsmsg.dll - 4613 (Hex)0x84351205 (Service Event) Log Severity: Warning (2) Log Message: Could not read from the registry sub-key: "%1". This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqhsmsg.dll - 4623 (Hex)0x8435120f (Service Event) Log Severity: Warning (2) Log Message: The Agent could not access WMI. The WMI support may have not been started or installed. Restart or Install WMI service and restart the agents. Event identifier: cpqhsmsg.dll - 4624 (Hex)0x84351210 (Service Event) Log Severity: Warning (2) Log Message: The Agent requires WMI service to be running. If NT 4.0 installed the latest version of WMI from Microsoft®, WMI service may need to be started. Event identifier: cpqhsmsg.dll - 4625 (Hex)0x84351211 (Service Event) Log Severity: Warning (2) Foundation agents 27