The following table lists all of the event log error messages that can be generated by the Alacritech driver.
The most commonly seen error is Event 5002. This indicates (in order of likelihood):
|
Event ID
|
Name
|
Text
|
Occurs
|
|
4100
|
EVENT_TCPIP_CREATE_DEVICE_FAILED
|
Unable to create device object. Initialization failed.
|
When the ATCP driver fails to create a device object.
|
|
4101
|
EVENT_TCPIP_NO_RESOURCES_FOR_INIT
|
Unable to allocate required resources. Initialization failed.
|
When the ATCP driver fails to allocated the resources it needs for initialization.
|
|
4186
|
EVENT_TCPIP_NO_MASK
|
No subnet mask was specified for interface. This interface and all subsequent interfaces on adapter cannot be initialized.
|
When a subnet mask is not specified for the interface.
|
|
4187
|
EVENT_TCPIP_INVALID_ADDRESS
|
Invalid address was specified for adapter. This interface cannot be initialized.
|
When an invalid IP address or route is specified for the adapter.
|
|
4189
|
EVENT_TCPIP_NO_ADAPTER_RESOURCES
|
IP could not allocate some resources required to configure adapter. Some interfaces on this adapter will not be initialized.
|
When some system resource, such as memory, could not be allocated as required for interface configuration.
|
|
4190
|
EVENT_TCPIP_DHCP_INIT_FAILED
|
IP was unable to initialize adapter for configuration by DHCP. If DHCP is enabled on this adapter, the primary interface may not be configured properly. Interfaces on this adapter not configured by DHCP will be unaffected.
|
When DHCP is improperly configured for the interface.
|
|
4191
|
EVENT_TCPIP_ADAPTER_REG_FAILURE
|
IP could not open the registry key for adapter. Interfaces on this adapter will not be initialized.
|
When a registry key or value that is required by the ATCP driver could not be opened.
|
|
4193
|
EVENT_TCPIP_NO_ADDRESS_LIST
|
Unable to read the configured IP addresses for adapter. IP interfaces will not be initialized on this adapter.
|
When the IP address for an interface could not be read from the registry.
|
|
4194
|
EVENT_TCPIP_NO_MASK_LIST
|
Unable to read the configured subnet masks for adapter. IP interfaces will not be initialized on this adapter.
|
When the subnet mask for an interface could not be read from the registry.
|
|
4196
|
EVENT_TCPIP_IP_INIT_FAILED
|
Initialization of IP failed.
|
When the initialization of the IP address for a given interface fails.
|
|
5000
|
EVENT_NDIS_RESOURCE_CONFLICT
|
Has encountered a conflict in resources and could not load.
|
When the SLIC driver could not claim the PCI resources associated with the adapter.
|
|
5001
|
EVENT_NDIS_OUT_OF_RESOURCE
|
Could not allocate the resources necessary for operation.
|
When a system resource, such as memory, could not be allocated by the SLIC driver.
|
|
5002
|
EVENT_NDIS_HARDWARE_FAILURE
|
Has determined that the adapter is not functioning properly.
|
This indicates that either the SLIC adapter hardware or the SLIC adapter microcode is not functioning properly.
|
|
5003
|
EVENT_NDIS_ADAPTER_NOT_FOUND
|
Could not find an adapter.
|
This indicates that the adapter found in the expected PCI slot is not a SLIC adapter.
|
|
5004
|
EVENT_NDIS_INTERRUPT_CONNECT
|
Could not connect to the interrupt number supplied.
|
This indicates that the SLIC driver could not register the adapter's interrupt vector.
|
|
5006
|
EVENT_NDIS_BAD_VERSION
|
The version number is incorrect for this driver.
|
This event ID is used by the SLIC driver to indicate that a debug version of the driver is running.
|
|
5009
|
EVENT_NDIS_UNSUPPORTED_CONFIGURATION
|
Does not support the configuration supplied.
|
This event indicates that the contents of the EEPROM on the SLIC adapter are not configured properly.
|
|
5011
|
EVENT_NDIS_MISSING_CONFIGURATION_PARAMETER
|
A required parameter is missing from the Registry.
|
Something is missing in the registry that is needed by the SLIC driver.
|