Compaq ProLiant 6400R Microsoft Windows Event ID and SNMP Traps Reference Guid - Page 130

Log Message: The NIC Management Agent encountered a fatal error. The service is terminating.

Page 130 highlights

Event identifier: cpqnimsg.dll - 264 (Hex)0x84350108 (Service Event) Log Severity: Warning (2) Log Message: Unable to open the registry 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: cpqnimsg.dll - 265 (Hex)0x84350109 (Service Event) Log Severity: Warning (2) Log Message: Unable to read "%1" from the registry. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqnimsg.dll - 266 (Hex)0x8435010a (Service Event) Log Severity: Warning (2) Log Message: Unable to read "%1" from the registry. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqnimsg.dll - 267 (Hex)0x8435010b (Service Event) Log Severity: Warning (2) Log Message: Unable to write "%1" to the registry. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqnimsg.dll - 268 (Hex)0x8435010c (Service Event) Log Severity: Warning (2) Log Message: Unable to enumerate "%1" from the registry. This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error. Event identifier: cpqnimsg.dll - 269 (Hex)0xc435010d (Service Event) Log Severity: Error (3) Log Message: The NIC Management Agent encountered a fatal error. The service is terminating. The data contain the error code. Event identifier: cpqnimsg.dll - 270 (Hex)0x8435010e (Service Event) Log Severity: Warning (2) Log Message: Unable to create thread. This error can be caused by a low memory condition. Rebooting the server may correct this error. Event identifier: cpqnimsg.dll - 271 (Hex)0x8435010f (Service Event) Log Severity: Warning (2) Log Message: Could not open the driver for device "%1". This error can be caused by an improperly installed adapter. Removing and reinstalling the device may correct the problem. The data contain the error code. Event identifier: cpqnimsg.dll - 272 (Hex)0x84350110 (Service Event) Log Severity: Warning (2) Log Message: Failure in driver %1. This error can be caused by an outdated driver version. Installing a later version of the driver may correct the problem. The data contain the error code. Event identifier: cpqnimsg.dll - 273 (Hex)0x84350111 (Service Event) NIC agents 130

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138

NIC agents 130
Event identifier: cpqnimsg.dll - 264 (Hex)0x84350108 (Service Event)
Log Severity: Warning (2)
Log Message: Unable to open the registry 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: cpqnimsg.dll - 265 (Hex)0x84350109 (Service Event)
Log Severity: Warning (2)
Log Message: Unable to read “%1” from the registry. This error can be caused by a corrupt registry
or a low memory condition. Rebooting the server may correct this error.
Event identifier: cpqnimsg.dll - 266 (Hex)0x8435010a (Service Event)
Log Severity: Warning (2)
Log Message: Unable to read “%1” from the registry. This error can be caused by a corrupt registry
or a low memory condition. Rebooting the server may correct this error.
Event identifier: cpqnimsg.dll - 267 (Hex)0x8435010b (Service Event)
Log Severity: Warning (2)
Log Message: Unable to write “%1” to the registry. This error can be caused by a corrupt registry or
a low memory condition. Rebooting the server may correct this error.
Event identifier: cpqnimsg.dll - 268 (Hex)0x8435010c (Service Event)
Log Severity: Warning (2)
Log Message: Unable to enumerate “%1” from the registry. This error can be caused by a corrupt
registry or a low memory condition. Rebooting the server may correct this error.
Event identifier: cpqnimsg.dll - 269 (Hex)0xc435010d (Service Event)
Log Severity: Error (3)
Log Message: The NIC Management Agent encountered a fatal error. The service is terminating. The
data contain the error code.
Event identifier: cpqnimsg.dll - 270 (Hex)0x8435010e (Service Event)
Log Severity: Warning (2)
Log Message: Unable to create thread. This error can be caused by a low memory condition.
Rebooting the server may correct this error.
Event identifier: cpqnimsg.dll - 271 (Hex)0x8435010f (Service Event)
Log Severity: Warning (2)
Log Message: Could not open the driver for device “%1”. This error can be caused by an improperly
installed adapter. Removing and reinstalling the device may correct the problem. The data contain the
error code.
Event identifier: cpqnimsg.dll - 272 (Hex)0x84350110 (Service Event)
Log Severity: Warning (2)
Log Message: Failure in driver %1. This error can be caused by an outdated driver version. Installing
a later version of the driver may correct the problem. The data contain the error code.
Event identifier: cpqnimsg.dll - 273 (Hex)0x84350111 (Service Event)