HP ML150 Support Question

Find answers below for this question about HP ML150 - ProLiant - G6.
Need a HP ML150 manual? We have 57 online manuals for this item!

HP Overview Questions Manuals Reviews Videos Research

Question posted by nasb on August 28th, 2014

Unable To Open The Registry Key This Error Can Be Caused By A Corrupt Registry

or a low memory condition. rebooting the server may correct this error

I Know the Answer!

I have the same question
Request More Information

Current Answers

There are currently no answers that have been posted for this question.
Be the first to post an answer!

Remember that you can earn up to 1,100 points for every answer you submit. The better the quality of your answer, the better chance it has to be accepted.

Related HP ML150 Manual Pages

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 6

...not allocate memory. Event identifier: cpqhsmsg.dll - 259 (Hex)0x84350103 (Service Event) Log Severity: Warning (2) Log Message: The Foundation Agents service could not open registry key "%1". Foundation agents Event Identifiers 256-774 Event identifier: cpqhsmsg.dll - 256 (Hex)0x84350100 (Service Event) Log Severity: Warning (2) Log Message: The Foundation Agents service detected an error. Event...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 18

...-key: "%1". This error can be caused by a corrupt registry or a low memory condition. Event identifier: cpqhsmsg.dll - 2098 (Hex)0x84350832 (Service Event) Log Severity: Warning (2) Log Message: Unable to allocate memory. This error can be caused by a low memory condition. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 19

... be caused by a low memory condition. Event identifier: cpqhsmsg.dll - 2307 (Hex)0x84350903 (Service Event) Log Severity: Warning (2) Log Message: "%1". Event identifier: cpqhsmsg.dll - 2311 (Hex)0x84350907 (Service Event) Log Severity: Warning (2) Log Message: The Threshold Agent could not open the base of the registry. Rebooting the server may correct this error. Rebooting the server may...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 21

...a corrupt registry or a low memory condition. This error can be caused by a corrupt registry or a low memory condition. Event identifier: cpqhsmsg.dll - 3076 (Hex)0x84350c04 (Service Event) Log Severity: Warning (2) Log Message: Unable to read "%1" 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...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 22

...a low memory condition. Rebooting the system will correct this error. Event identifier: cpqhsmsg.dll - 3842 (Hex)0x84350f02 (Service Event) Log Severity: Warning (2) Log Message: Could not write the registry sub-key: "%1". Rebooting the server may correct this error. Rebooting the server may correct this error. This error can be caused by a corrupt registry or a low memory condition...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 24

...correct this error... open the Cluster service registry key...Rebooting the server may have been stopped. The Cluster service may not be running. The Cluster service may not be caused by the Agent. Event identifier: cpqhsmsg.dll - 3869 (Hex)0x84350f1d (Service Event) Log Severity: Warning (2) Log Message: The Cluster service is not supported by a corrupt registry or a low memory condition...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 27

...) Log Severity: Warning (2) Log Message: Unable to be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. 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". Event identifier: cpqhsmsg.dll...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 29

...) Log Severity: Warning (2) Log Message: The Storage Agents service could not open registry key "%1". The data contains the error code. Event identifier: cpqstmsg.dll - 262 (Hex)0x84350106 (Service Event) Log Severity: Warning (2) Log Message: The Storage Agents service could not allocate memory. The data contains the error code. The insertion string is: %1. The data contains the...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 31

... error can be caused by this error. Rebooting the server may correct this error. This error can be caused by a corrupt registry or a low memory condition. Event identifier: cpqstmsg.dll - 401 (Hex)0x44350191 (Service Event) Log Severity: Information (1) Log Message: %1 Event identifier: cpqstmsg.dll - 512 (Hex)0x84350200 (Service Event) Log Severity: Warning (2) Log Message: Unable...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 76

...is indicated in the status of %6. Rebooting the server may correct this error. This error can be caused by a corrupt registry or a low memory condition. This error can be caused by a corrupt registry or a low memory condition. The Storage Agent has detected a change in the cpqSasLogDrvStatus variable. This indicates a low memory condition. Storage agents 76 The current logical...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 77

... Severity: Warning (2) Log Message: Could not write the registry subkey: "%1". Always reboot the system after a Storage Agents upgrade. Event identifier: cpqstmsg.dll - 1792 (Hex)0x84350700 (Service Event) Log Severity: Warning (2) Log Message: The SNMP Agent is running. This error can be caused by a corrupt registry or a low memory condition. Reinstalling the agents may need to an...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 80

...a request. Rebooting the server may correct this error. Rebooting the server may correct this error. Event identifier: cpqstmsg.dll - 3600 (Hex)0x84350e10 (Service Event) Log Severity: Warning (2) Log Message: The IDE Agent received an unknown action code from the registry subkey. This error can be caused by a corrupt registry or a low memory condition. Event identifier...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 81

... not read the registry subkey: "%1". This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. This error can be caused by a corrupt registry or a low memory condition. Event identifier: cpqstmsg...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 82

... Agents service could not read the registry value "%1". The data contains the error code. The data contains the error code. The data contains the error code. Event identifier: cpqsvmsg.dll - 261 (Hex)0x84350105 (Service Event) Log Severity: Warning (2) Log Message: The Server Agents service could not open registry key "%1". Server agents Event Identifiers 256-774 Event identifier: cpqsvmsg...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 124

... Log Severity: Error (3) Log Message: Unable to write to load a required driver. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Rebooting the server may correct this error. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 125

... Unable to correct this error. Use the Network control panel to load a required library. This indicates a low memory condition. Rebooting the system may correct this error. Rebooting the server may correct this error. Reinstalling the Server Agents or running the Emergency Repair procedure may correct this error. This error can be caused by a corrupt registry or a low memory...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 126

...: The Rack And Enclosure MIB Agent could not open the base of the registry. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. The Remote Insight Agent requires the Remote Insight Board device driver (CPQSM2.SYS) to be caused by a corrupt registry or a low memory condition. If you do not have a Remote Insight Board...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 129

.... Rebooting the server may correct this error. This error can be caused by a corrupt registry or a low memory condition. This indicates a low memory condition. Rebooting the system will correct this error. The data contain the error code. The data contain the error code. Event identifier: cpqnimsg.dll - 261 (Hex)0x84350105 (Service Event) Log Severity: Warning (2) Log Message: Unable...

Microsoft Windows Event ID and SNMP Traps Reference Guide for use with SmartStart version 8.25 - Page 130

...: Unable to enumerate "%1" from the registry. This error can be caused by a corrupt registry or a low memory condition. Event identifier: cpqnimsg.dll - 271 (Hex)0x8435010f (Service Event) Log Severity: Warning (2) Log Message: Could not open the registry key "%1". The data contain the error code. Installing a later version of the driver may correct the problem. Rebooting the server...

HP Insight Server Migration Software for ProLiant User Guide - Page 127

... environment variable. 1. Possible causes for the error message include: • Network card is not connected to the network. • Network to which the card connects to does not have DHCP. • Network card is not supported by pressing the F9 key during POST. 2. Reboot the destination server using the HP Insight Server Migration software for migration...