Event Identifiers 256-299
Event identifier: cpqnimsg.dll - 256 (Hex)0x84350100 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent detected an error. The insertion string is: %1. The data contain the error code.
Event identifier: cpqnimsg.dll - 257 (Hex)0x84350101 (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: cpqnimsg.dll - 258 (Hex)0x84350102 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent could not register with the Service Control Manager. The data contain the error code.
Event identifier: cpqnimsg.dll - 259 (Hex)0x84350103 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent could not set the service status with the Service Control Manager. The data contain the error code.
Event identifier: cpqnimsg.dll - 260 (Hex)0x84350104 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent could not start the Service Control Dispatcher. The data contain the error code.
Event identifier: cpqnimsg.dll - 261 (Hex)0x84350105 (Service Event)
Log Severity: Warning (2)
Log Message: Unable to read 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 - 262 (Hex)0x84350106 (Service Event)
Log Severity: Warning (2)
Log Message: Could not create 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 - 263 (Hex)0x84350107 (Service Event)
Log Severity: Warning (2)
Log Message: Could not delete 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 - 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)
Log Severity: Warning (2)
Log Message: There were no physical adapters in team: “%1.” This error can be caused by improperly installed drivers. Remove all device instances associated with the team and re-install the drivers and team.
Event identifier: cpqnimsg.dll - 274 (Hex)0x84350112 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent cannot generate Traps due to a communication problem with the NIC SNMP extension agent.
Event identifier: cpqnimsg.dll - 275 (Hex)0x44350113 (Service Event)
Log Severity: Information (1)
Log Message: Communication with the NIC SNMP extension agent has been restored. TRAPS can now be sent.
Event identifier: cpqnimsg.dll - 276 (Hex)0x84350114 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent cannot communicate with the Token Ring Protocol driver (CNMPROT.SYS).
Event identifier: cpqnimsg.dll - 277 (Hex)0x44350115 (Service Event)
Log Severity: Information (1)
Log Message: The NIC Management Agent version %1 has started.
Event identifier: cpqnimsg.dll - 279 (Hex)0x84350117 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent could not set an event. The data contain the error code.
Event identifier: cpqnimsg.dll - 280 (Hex)0x84350118 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent service could not start any agents successfully.
Event identifier: cpqnimsg.dll - 281 (Hex)0x84350119 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent main thread did not terminate properly. The data contain the error code.
Event identifier: cpqnimsg.dll - 283 (Hex)0x8435011b (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent did not respond to a request. The data contain the error code.
Event identifier: cpqnimsg.dll - 285 (Hex)0x8435011d (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Management Agent could not get the system type. The data contain the error code.
Event identifier: cpqnimsg.dll - 287 (Hex)0x8435011f (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Agent service could not load the module “%1”. The data contain the error code.
Event identifier: cpqnimsg.dll - 288 (Hex)0x84350120 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Agent service could get the control function for module “%1”. The data contain the error code.
Event identifier: cpqnimsg.dll - 290 (Hex)0x84350122 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Agent service could not start agent “%1”. The data contain the error code.
Event identifier: cpqnimsg.dll - 291 (Hex)0x84350123 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Agent service detected an invalid state for agent *”%1”. The data contain the state.
Event identifier: cpqnimsg.dll - 292 (Hex)0x84350124 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Agent service could not stop agent “%1”. The data contain the error code.
Event identifier: cpqnimsg.dll - 293 (Hex)0x84350125 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Agent service could not terminate agent “%1”. The data contain the error code.
Event identifier: cpqnimsg.dll - 294 (Hex)0x84350126 (Service Event)
Log Severity: Warning (2)
Log Message: The NIC Agent service could not unload the module “%1”. The data contain the error code.
Event identifier: cpqnimsg.dll - 296 (Hex)0xc4350128 (Service Event)
Log Severity: Error (3)
Log Message: A driver for a NIC failed to open. This error can be caused by an improperly installed adapter. Removing and reinstalling all adapters may correct the problem. The NIC Agent service will not respond to any management requests.
Event identifier: cpqnimsg.dll - 297 (Hex)0x84350129 (Service Event)
Log Severity: Warning (2)
Log Message: An attempt to log an event to the IML failed. The IML log may be full. Clearing the IML log may correct this problem.
Event identifier: cpqnimsg.dll - 298 (Hex)0xc435012a (Service Event)
Log Severity: Error (3)
Log Message: A fatal error occurred during Virus Throttle WMI event processing. Virus Throttle related traps will not be sent.
Cause: WMI service is probably not running. Starting WMI service or NIC agent might solve this problem.
Event identifier: cpqnimsg.dll - 299 (Hex)0x8435012b (Service Event)
Log Severity: Warning (2)
Log Message: An attempt to query WMI for Virus Throttle event failed. The event data gives the error number.