Token Ring Adapters - Error Message Descriptions

Support Home

Support & Downloads

Token Ring Adapters

Error Message Descriptions

These error messages apply to the TokenExpress^TM 16/p LAN Adapter software release v7.0 which is available in the archive TE16DISK.EXE .

DOS ODI Driver Error Messages

Error Message: Adapter card not found
Action: Check that you have installed the adapter correctly, that it is seated firmly in its slot and that the adapter configuration does not conflict with other installed devices.

Error Message: Max Frame Size is too large in NET.CFG. Max = XXXX
Action: Insert a valid number in the NET.CFG file.

Error Message: Max Frame Size is too small in NET.CFG. Min = XXXX
Action: Insert a valid number in the NET.CFG file.

Error Message: Unexpected adapter register behavior or adapter not supported.
Action: Check that the adapter configuration does not conflict with other installed devices.

Error Message: Illegal I/O address specified in file: NET.CFG.
Action: Correct your NET.CFG file.

Error Message: No adapter found at port address specified in file: NET.CFG.
Action: Check that the adapter configuration does not conflict with other installed devices.

Error Message: Node address must have 12 hex digits, the first being 4, 5, 6 or 7.
Action: Correct the node address.

Error Message: Error opening adapter. Error code 02YZ
Action: "Y" in the error code indicates the Open Phase and "Z" indicates the error type. See also the hints that follow the error codes.

The "Y" error codes are:

021z Lobe media test
022z Physical insertion
023z Address verification
024z Participation in ring poll
025z Request initialization
028z Unknown phase error
029z Request registration
02Bz Address verification

The "Z" error codes are:
02y1 Function failure
02y2 Signal loss
02y5 Timeout (at Full Duplex: Protocol error)
02y6 Ring failure
02y7 Ring beaconing
02y8 Duplicate node address (at Full Duplex: Insert denied)
02y9 Request initialization
02yA Remove received
02yB C-port changed

Hints:

021z Check the cable from the card connector to the MAU or wall outlet (the lobe media).

02y7 Check that the card speed (4 or 16 Mbps) corresponds with the ring speed of the Token-Ring.

02y8 Another card on the Token-Ring network has a node address identical to yours. If you are using Local Administered Node Address, change it for one of the cards.

OS/2 ODI Driver Error Messages

Error Message: MLI0198: Attempt to add MLID protocol ID failed.
Action: Correct your NET.CFG file

Error Message: MLI0199: Attempt to allocate memory for Virtual Boards failed.
Action: Get more memory for the driver.

Error Message: MLI0204: LSL support module not installed.
Action: Check that LSL.SYS is installed correctly and before TE16.SYS.

Error Message: MLI0208: Error initializing Token-Ring adapter
Action: Run the diagnostics program. This error may occur, if for some reason the interrupt from the adapter does not go through to the driver.

Error Message: MLI0210: Error opening Token-Ring adapter - check cabling
Action: Check the cable from the card connector to the MAU or wall outlet (the lobe media).

Error Message: MLI0211: Illegal Interrupt used for 8-bit Slot.
Action: Correct your NET.CFG file or re-configure your adapter.

Error Message: MLI0212: Error Max Frame Size is too Large in NET.CFG. MAX = 4216
Action: Insert a valid number in your NET.CFG file

Error Message: MLI0213: Error Max Frame Size is too Small in NET.CFG. MIN = 632
Action: Insert a valid number in your NET.CFG file

Error Message: MLI0214: Error Opening adapter:
Lobe Media -
Action: Check the cable from the adapter connector to the MAU or wall outlet (the lobe media).

Physical Insertion -
Addr. Verification -
Participation in Ring Poll -
Request Initialization -
Function Failure-
Signal Loss-
Timeout-
Ring Failure-

Error Message: Ring Beaconing
Action: Check that the adapter speed (4 or 16 Mbps) corresponds with the ring speed of the Token-Ring.

Error Message: Duplicate Node Address
Action: Another adapter on the Token-Ring network has a node address identical to yours. If you are using Local Administered Node Address, change it for one of the adapters.

Parameter Request
Remove Received
No Monitor Detected
Monitor Contention Fail

Error Message: MLI0217: Illegal I/O address specified in file NET.CFG
Action: Correct your NET.CFG file

Error Message: MLI0218: No Token-Ring Adapter found!
Action: Check that you have installed the adapter correctly, that it is seated firmly in its slot and that the adapter configuration does not conflict with other installed devices.

Error Message: MLI0219: Unexpected adapter register behavior or adapter not supported.
Action: Check that adapter configuration does not conflict with other installed devices.

Error Message: MLI0222: No adapter found at port address specified in file: NET.CFG.
Action: Check that the address specified matches the adapter configuration.

Error Message: MLI0223: Node Address must have 12 digits, the first being 4,5,6 or 7
Action: Correct the node address.

Novell NetWare* Error Messages

This section lists commonly-occurring error return codes between 0211h and F400h.

#	Message
02yz	An error was detected while inserting into the ring. "Y" indicates the command phase and "Z" specifies the type of error.
021	Lobe media test
022	Physical insertion
023	Address verification
024	Participation in ring poll
025	Request initialization
028	Unknown phase error
029	Request registration
02B	Address verification
02-1	Function failure
02-2	Signal loss
02-5	Time-out (at Full Duplex: Protocol error)
02-6	Ring failure
02-7	Duplicate address
02-8	Duplicate node address (at Full Duplex: Insert denied)
02-9	Request initialization
02-A	Remove received
02-B	C-port changed
0400	Transmit buffer count error
0800	Adapter RAM error
1000	Buffer size error
2000	List size error
4000	Invalid node address passed with Open command
F000	Time-out
F030	Initial test error
F031	Adapter ROM checksum error
F032	Adapter RAM error
F033	Instruction test error
F034	Context/interrupt test error
F035	Protocol handler hardware error
F036	System interface register error
F0xx	Unexpected I/O register behavior
F101	Invalid unit block passed to adapter
F102	Invalid initialization options
F103	Invalid receive burst count
F104	Invalid transmit burst count
F105	Invalid DMA abort threshold
F106	Invalid SCB address
F107	Invalid SSB address
F108	Direct I/O parity error
F109	DMA time-out
F10A	DMA parity error
F10B	DMA bus error
F10C	DMA data compare error
F10D	Unrecoverable error during initialization
F1FE	Adapter DMA to wrong addresses in PC memory
F1FF	Time-out waiting for initialize to complete
F200	Time-out error waiting for a Read Adapter Buffer command to complete
F300	Unexpected response to Open command
F400	Adapter check during Open command. Possibly caused by RAM error on the adapter

DOS DLC Driver Error Messages

Error Message: 161E No adapters found
Action: Check that you have installed the adapter correctly, and that it is firmly fixed in its expansion slot.

Error Message: Driver not installed. Press <F1> to continue
Action: Contact your system administrator.

Error Message: 162E Interrupt arbitrator not loaded
Action: Copy the file TE16IA.SYS from the Driver Disk to the NETWORK directory, and insert "device=\network\TE16IA.SYS" as the first line in your CONFIG.SYS file.

Error Message: 163E Invalid node address. 12 hex digits needed if non-zero
Action: Check that the device driver line in CONFIG.SYS contains an address consisting of 12 hexadecimal digits. We recommend that the first four digits be 4000.

Error Message: 164E Invalid node address. First digit must be 4, 5, 6 or 7.
Action: Check that the device driver line in CONFIG.SYS contains an address beginning with 4, 5, 6 or 7.

Error Message: 165E Unknown parameter on command line
Action: Check the parameters given for TE16DLC.SYS in CONFIG.SYS.

Error Message: 166E Invalid adapter number on command line
Action: Check that the adapter number specified in the CONFIG.SYS file is 0 or 1 (0 = first adapter, 1 = second adapter).

Error Message: 167E An interface with this adapter number has been loaded
Action: An attempt was made to install a driver with a adapter number which already was used. Repeat the installation procedure using a valid adapter number.

NDIS 2.0 MAC Driver Error Messages

Error Message: 330E MAC Driver not Installed - Adapter not found or invalid, CC=
Action: Check that you have installed the adapter correctly.

Error Message: 333E MAC Driver not Installed - Interrupt conflict detected, CC=
Action: Check that the interrupt level chosen for the adapter does not conflict with other expansion cards installed on your PC.

Error Message: 334E MAC Driver not Installed - Memory allocation error 1, CC=
Action: This message only appears on OS/2 based systems. The MAC driver was not able to allocate the memory it needs in either high (above 1M bytes) or in low memory. Check configuration parameters in PROTOCOL.INI.

Error Message: 335E MAC Driver not Installed - Memory allocation error 2, CC=
Action: This message only appears on OS/2 based systems. The MAC driver was not able to allocate the needed number (two) of GDT (Global Descriptor Table) selectors. Check the configuration parameters for other installed devices, to see if you are able to decrease their GDT selector claim.

Error Message: 336E MAC Driver not Installed - Memory allocation error 3, CC=
Action: This message only appears on OS/2 based systems. Check that your disk has not been damaged (CHKDSK).

Error Message: 337E MAC Driver not Installed - Memory allocation error 4, CC=
Action: This message only appears on OS/2 based systems. Check that your disk has not been damaged (CHKDSK).

Error Message: 340E MAC Driver not Installed - PROTMAN open error, CC=
Action: Check that your CONFIG.SYS has not been garbled. The device= ... \PROTMAN.SYS statement shall precede the device= ...\TE16.xxx statement.

Error Message: 341E MAC Driver not Installed - PROTMAN interface error, CC=
Action: Check that your PROTMAN.SYS device installs properly (no error messages are displayed during system initialization). Check that your CONFIG.SYS has not been garbled. The /i parameter of the line device=...\PROTMAN.SYS must identify the path to the directory in which PROTOCOL.INI is located, e.g. C:\LANMAN. If you are using IBM LAN Server or LAN Requester, the PROTOCOL.INI file is normally located in the \IBMCOM directory.

Error Message: 342E MAC Driver not Installed - PROTMAN register error, CC=
Action: Check that your PROTMAN.SYS device installs properly (no error messages are displayed during system initialization). Check that your CONFIG.SYS has not been garbled. The /i parameter of the line device= ...\PROTMAN.SYS must identify the path to the directory in which PROTOCOL.INI is located, for example

C:\LANMAN\DRIVERS\TOKENRNG\TE16.

Error Message: 344W MAC Configuration Error - Unknown keyword, Keyw:
Action: The TE16 section of PROTOCOL.INI contains an unknown keyword. The keyword in question is the number indicated by Keyw counted from the start of the TE16 section. Check the keyword for spelling errors.

Error Message: 345W MAC Configuration Error - Parameter out of Range, Keyw:
Action: A keyword in the TE16 section of PROTOCOL.INI has been assigned an illegal value. The keyword in question is the number indicated by Keyw counted from the start of the TE16 section. If the keyword is "NODEADDRESS," a universally administered address has been assigned. Correct the assigned value.

Error Message: 346W MAC Configuration Error - Too Few Parameters, Keyw:
Action: A keyword in the TE16 section of PROTOCOL.INI has been assigned too few values. The keyword in question is the number indicated by Keyw counted from the start of the TE16 section. Assign the missing value(s).

Error Message: 347W MAC Configuration Error - Too Many Parameters, Keyw:
Action: A keyword in the TE16 section of PROTOCOL.INI has been assigned too many values. The keyword in question is the number indicated by Keyw counted from the start of the TE16 section. Correct the keyword assignment.

Error Message: 348W MAC Configuration Error - Illegal Parameter Type, Keyw:
Action: A keyword in the TE16 section of PROTOCOL.INI has been assigned an illegal value, e.g. the assigned value is a text and it should be a decimal value. The keyword in question is the number indicated by Keyw counted from the start of the TE16 section. Correct the keyword assignment.

Error Message: 349E MAC Driver not Installed - PROTMAN configuration error, CC=
Action: Check your PROTOCOL.INI file for the correct specification of the protocols constituting the protocol stack. Check that the entry for the adapter contains the line: "Drivername=TE16$".

Error Message: 350E MAC Driver not Installed - Dynamic data overflow, CC=
Action: This message is only received on DOS based installations. The receive buffer pool size is too large. Decrease the values for either RecBufSize or RecBufCount in PROTOCOL.INI.

Error Message: 352E MAC Driver not Installed - Adapter I/O port conflict, CC=
Action: Two adapters are installed, but there are no "IOBase =" statements in PROTOCOL.INI or they specify the same I/O port.

Error Message: 355W MAC Driver receive area too large - Receive area set to default 0xNNNN
Action: The receive buffer pool is too large. Decrease the values for RecBufSize or RecBufCount in PROTOCOL.INI. Default values will be used.

Error Message: 356W Failed to allocate interrupt 2F ID. SNMP will not be available.
Action: A large number of TSR programs using this interrupt is active. Reduce the number of active TSR programs.

Error Message: 361E MAC driver not installed - Adapter initialization error, CC=
Action: See MAC Driver Error Codes.

NDIS 3.0 Driver Error Messages

The NDIS 3.0 error messages reported under Microsoft Windows* for Workgroups 3.11, Microsoft Windows 95 and Microsoft Windows NT* are identical. However, the way the errors are reported to the user differs.

Windows for Workgroups 3.11

In Windows for Workgroups 3.11 error codes reported by NDIS 3.0 drivers are written to the NDISLOG.TXT file located in your Windows directory. Error messages are divided into two groups: Intel defined error messages and general error messages.

An example of an Intel defined error message reported by the MAC driver could be:

TE16, Unknown Error Code, 0X8100000A, 0XC0000023, 0X0000D860

The text "0X8100000A" describes the error and refers to a specific error code, listed below. Ignore the leading "0X8100" (resulting in errorcode A for the example above - Lobe wire fault.

General error messages familiar to the system are displayed as:

TE16A, Adapter Not Found, 0XAA000004, 0XC0000001, 0X0000FFFF

These messages are displayed in clear text and are listed below as well for completeness.
If you experience any problems, you should make a backup copy of the NDISLOG.TXT file before restarting Windows For Workgroups 3.11.

Windows 95

In Windows 95 error codes reported by NDIS 3.0 drivers are written to the NDISLOG.TXT file located in your Windows directory. An example of an error message reported by the MAC driver could be:

Intel TokenExpress Adapter (0002).

Error Code = 0XA100000A

The text "0XA100000A" describes the error and refers to a specific error code, listed below. Ignore the leading "0XA100" (resulting in errorcode A for the example above - Lobe wire fault ..).

If you experience any problems, you should make a backup copy of the NDISLOG.TXT file before restarting Windows 95

Windows NT

When running Windows NT, errors are reported using the Event Log. This log can be examined using the Event Viewer located in the Administrative Tools group.

If you experience any problems with the network, you should check if any error messages or warnings are posted by the Miniport driver by using the Event Viewer found in the Administrative Tools window. All error messages and/or warnings posted by the TokenExpress driver have the Source field set to "TE16." System error messages, related to the TokenExpress driver, may occur with different source names, i.e. "Service Control Manager."

The messages are enumerated by the Event field and are described below in Event number order. You can display the message description, by highlighting the message and pressing enter.

If you experience any problems, you should write down the "Event ID," "Source," "Description," and "Data" fields in the "Event Detail" window.

Error Messages

For each of the following error messages the first line contains the error code used by Windows 95 and Windows for Workgroups 3.11. The second line contains the "Event ID" and "Data" fields used by Windows NT.

Intel-defined Error Messages and Actions

Code Description

Error Message: 1 Unknown error code
Error Message: 1 Bring-up diagnostics failed for OcTk1601.
Action: The adapter failed during the bring-up diagnostics. Shut down your system and retry the operation.

Error Message: 2 Unknown error code
Error Message: 2 Adapter initialize failed for OcTk1601.
Action: The adapter failed the initialization phase. Shut down your system and retry the operation.

Error Message: 3 Unknown error code
Error Message: 3 Adapter Check on OcTk1601.
Action: A serious error occurred on the adapter, causing an Adapter check code to be posted. Restart your system.

Error Message: 4 Unknown error code
Error Message: 4 Could not open adapter OcTk1601. Ring beaconing. Check network speed settings.
Action: The network speed setting is wrong. Change it and restart your system.

Error Message: 5 Unknown error code
Error Message: 5 Could not open adapter OcTk1601. Duplicate node address.
Action: A duplicate address has been discovered on the ring. Change your locally administered address as discussed in the "Adapter parameter" section above and restart your system.

Error Message: 6 Unknown error code
Error Message: 6 Could not open adapter OcTk1601. Request initialization failed.
Action: An error occurred during adapter initialization. Restart your system.

Error Message: 7 Unknown error code
Error Message: 7 Could not open adapter OcTk601. Remove station received.
Action: The adapter has been removed by a LAN Manager station. Contact your network administrator.

Error Message: 8 Unknown error code
Error Message: 8 Could not open adapter OcTk1601.
Action: The adapter failed to open. Please check cables and connections and retry the operation.

Error Message: 9 Unknown error code
Error Message: 9 Could not download code on adapter OcTk1601.
Action: The download operation failed.

Error Message: A Unknown error code
Error Message: 10 Lobe wire fault detected by OcTk1601. Please check cable connections.
Action: Check all cables and connections and try another lobe media cable. Retry the operation.

Error Message: B Unknown error code
Error Message: 11 OcTk1601 has failed the lobe wrap test resulting from the beacon auto-removal process and has deinserted from the ring.
Action: The adapter has deinserted from the ring, because the ring was beaconing. Check the network speed settings and cable connections and retry the operation. If the error persists, contact your network administrator.

Error Message: C Unknown error code
Error Message: 12 OcTk1601 has received a remove ring station Mac frame request and has deinserted from the ring.
Action: The adapter has been removed by a LAN Manager station. Contact your network administrator.

Error Message: D Unknown error code
Error Message: 13 The detected adapter for OcTk1601 is not supported by this driver.
Action: You have installed a wrong MAC driver for the adapter used.

Error Message: E Unknown error code
Error Message: 14 The configuration read for OcTk1601 is invalid.
Action: A configuration entry is invalid. Use the network control panel to set up proper adapter settings.

Error Message: F Unknown error code
Error Message: 15 OcTk1601 has received a Trace Tool Remove frame from a Network Management station and has disabled the promiscuous packet filter.
Action: The adapter driver has cleared the PROMISCUOUS packet filter bit, as instructed by a LAN Manager station. Contact your network administrator.

General Error Messages

For each error message below the first line contains the error code used by Windows 95, Windows NT, and Windows for Workgroups 3.11. The second line contains the "Event ID" and "Data" fields used by Windows NT.

Code Description

Error Message: 1388 Resource Conflict
5000 OcTk1601: Has encountered a conflict in resources and could not load.
Action: Check the resources used by the network adapter(s) to ensure, that no conflicts exists.

Error Message: 1389 Out of Resources
5001 OcTk1601: Could not allocate resources necessary for operation.
Action: The driver failed to load, because it tried to allocate too many resources. Decrease the number of receive and/or transmit buffers and retry the operation.

Error Message: 138A Hardware failure
5002 OcTk1601 : Has determined that the adapter is not functioning properly.
Action: The adapter could not be found or is not working properly. Check I/O base settings and retry the operation.

Error Message: 138B Adapter not found
5003 OcTk1601 : Could not find an adapter.
Action: The adapter could not be found by the MAC driver. Check I/O base settings and retry the operation.

Error Message: 138C Interrupt Connect
5004 OcTk1601 : Could not connect to the interrupt number supplied.
Action: The interrupt is already used by another device. Change the adapter interrupt number and retry the operation.

Error Message: 138D Driver Failure
5005 OcTk1601 : Has encountered an internal error and has failed.
Action: An internal error has been discovered.

Error Message: 1390 Network Address
5008 OcTk1601 : Has encountered an invalid network address.
Action: An invalid network address was specified. Change the locally administered network address and restart your system. The driver uses the burned-in address when loading.

Error Message: 1391 Unsupported Configuration
5009 OcTk1601 : Does not support the configuration supplied.
Action: An invalid configuration entry was discovered. Use the network control panel to set proper adapter parameters.

Error Message: 1392 Invalid Value From Adapter
5010 OcTk1601 : The adapter has returned an invalid value to the driver.
Action: An internal error has occurred.

Error Message: 1393 Missing Configuration Parameter
5011 OcTk1601 : A required parameter is missing from the registry.
Action: A parameter necessary for operation has been omitted in the registry. Use the network control panel to set proper parameters.

Error Message: 1394 Bad IO Base Address
5012 OcTk1601 : The IO Base Address supplied does not match the jumpers on the adapter.
Action: The adapter could not be found by the MAC driver. Check I/O base settings and retry the operation.

Error Message: 1396 Adapter disabled
5014 OcTk1601 : The adapter is disabled. The driver cannot open the adapter.
Action: Make sure the start-up parameter for the TokenExpress adapter driver is set to "Manual". Use the "Devices" icon in the control panel to change the settings.

Error Message: 1397 I/O Port Conflict
5015 OcTk1601 : There is an I/O port conflict.
Action: The ports used by the MAC driver are already in use by another device. Change the I/O Base address for the adapter.

Error Message: 1398 Port or DMA Conflict
5016 OcTk1601 : There is an I/O port or DMA channel conflict.
Action: Check the I/O port and DMA usage by the adapter to ensure that there are no resource conflicts.

Error Message: 1399 Memory Conflict
5017 OcTk1601 : There is a memory conflict at address xx.
Action: The MAC driver and another device could not share the memory.

Error Message: 139A Interrupt Conflict
5018 OcTk1601 : There is a interrupt conflict at interrupt number xx.
Action: Change the interrupt selection on the adapter and retry the operation.

Error Message: 139B DMA Resource Conflict
5019 OcTk1601 : There is a resource conflict at DMA channel xx.
Action: Change the DMA channel selection on the adapter and retry the operation.

This applies to:

TokenExpress™ 16/p Adapter
TokenExpress™ EISA 16/4 Adapter
TokenExpress™ EISA 32 Adapter
TokenExpress™ MCA Adapter

End of Interactive Support Announcement
These products are no longer being manufactured by Intel. Additionally, Intel no longer provides interactive support for these products via telephone or e-mail, nor will Intel provide any future software updates to support new operating systems or improve compatibility with third party devices and software products.

THESE DOCUMENTS ARE PROVIDED FOR HISTORICAL REFERENCE PURPOSES ONLY AND ARE SUBJECT TO THE TERMS SET FORTH IN THE "LEGAL INFORMATION" LINK BELOW. For information on currently available Intel products, please see www.intel.com/products.

Solution ID: CS-012025
Date Created: 31-May-2004
Last Modified: 27-May-2009