70.0 TLI Messages
Transport Level Interface (TLI) is a UNIX-based interface that provides basic end-to-end data transfer support needed by software applications and higher level protocols. It hides the topology and characteristics of the underlying network from users. It defines a set of services common to different protocol suites so that data can be ported across a variety of transport providers. TLI supports the International Standards Organization (ISO) protocols, TCP/IP, XNS, and SNA.
All TLI messages are generated by a specific application. The messages listed here are called from the TLI library of function calls and are always followed by an application-specific message. If you need further information to resolve the problem, contact the vendor of the application or a Novell support provider.
2: No error was specified.
Source:
TLI library
Possible Cause:
An error occurred that did not set the t_errno function to a specific error value, or an error has not yet occurred.
Action:
Contact the developer or vendor of the application.
3: Insufficient permission.
Source:
TLI library
Possible Cause:
A function has been called that is not allowed.
Action:
If you have access to developer documentation, look up the platform-specific restrictions and options for the underlying protocol and operating system being used. Otherwise, contact the developer or vendor of the application.
4: Incorrect transport address format.
Source:
TLI library
Possible Cause:
The application has called a function by passing an address that contains an incorrect format or illegal information.
Action:
If you have access to developer documentation, look up the platform-specific restrictions and options for the underlying protocol being used. Otherwise, contact the developer or vendor of the application.
5: Illegal amount of data.
Source:
TLI library
Action:
If you have access to developer documentation, look up the platform-specific restrictions for the minimum and maximum amount of data that can be sent. Otherwise, contact the developer or vendor of the application.
6: File descriptor does not refer to a transport endpoint.
Source:
TLI library
Possible Cause:
The file descriptor that was passed to the function is invalid or has not been properly opened.
Action:
Contact the developer or vendor of the application.
Source:
TLI library
Action:
Contact the developer or vendor of the application.
8: Incorrect transport options.
Source:
TLI library
Possible Cause:
The user or application does not have permission to accept a connection on the responding transport endpoint or to use the specified options.
Action:
Contact the developer or vendor of the application.
9: Incorrect sequence number.
Source:
TLI library
Possible Cause:
The sequence number specified did not match the sequence number expected when the connection was being established or rejected.
Action:
Contact the developer or vendor of the application.
10: Buffer size insufficient.
Source:
TLI library
Possible Cause:
A function has been called with a buffer of insufficient size to return protocol information.
Action:
If you have access to developer documentation, look up platform-specific protocol requirements of the system to determine a valid buffer size. Otherwise, contact the developer or vendor of the application.
Source:
TLI library
Possible Cause:
An unidentified error has prevented the message from being sent.
Action:
Contact the developer or vendor of the application.
12: An asynchronous event has occurred.
Source:
TLI library
Possible Cause:
In the process of calling a function, an asynchronous event has occurred on the endpoint. The t_look function can be called to determine what event took place.
Action:
Contact the developer or vendor of the application.
13: Transport provider could not allocate an address.
Source:
TLI library
Possible Cause:
The specified protocol address was in an incorrect format, contained illegal information, or was already being used. No dynamic addresses remain.
Action:
If you have access to developer documentation, look up platform-specific protocol restrictions on address format. Otherwise, contact the developer or vendor of the application.
14: No data is available.
Source:
TLI library
Possible Cause:
The function has been called on an endpoint where no data is available.
Action:
Contact the developer or vendor of the application.
15: No orderly release indication is available.
Source:
TLI library
Possible Cause:
A t_rcvrel function has been called when no orderly release indication has arrived from the other endpoint.
Action:
Contact the developer or vendor of the application.
16: Function not supported by the transport.
Source:
TLI library
Possible Cause:
The function is not supported by the underlying transport provider.
Action:
Contact the developer or vendor of the application.
17: Primitive issued in the wrong sequence.
Source:
TLI library
Possible Cause:
The function has been called in an improper state.
Action:
Contact the developer or vendor of the application.
Source:
TLI library
Possible Cause:
The transport provider is undergoing a transient state change.
Action:
Contact the developer or vendor of the application.
19: A system error occurred.
Source:
TLI library
Possible Cause:
A system error occurred during the execution of the function.
Action:
Contact the developer or vendor of the application.
20: No unitdata error indication is available.
Source:
TLI library
Possible Cause:
An error function was used by the application when no error condition existed.
Action:
Contact the developer or vendor of the application.
21: No disconnect indication is available.
Source:
TLI library
Possible Cause:
No disconnect indication currently exists on the specified transport endpoint.
Action:
Contact the developer or vendor of the application.
22: Unsupported struct-type requested.
Source:
TLI library
Possible Cause:
The structure specified in the t_alloc function is not supported.
Action:
Contact the developer or vendor of the application.
23: Invalid transport provider name.
Source:
TLI library
Possible Cause:
The transport protocol specified when the t_open function is not available.
Action:
Make sure you have loaded all of the protocols required by the application. If the problem persists, contact the developer or vendor of the application.
Source:
TLI library
Possible Cause:
The argument qlen of the endpoint referenced by fd is zero. The application is trying to function as a server after initializing itself as a client.
Action:
Contact the developer or vendor of the application.
Source:
TLI library
Possible Cause:
The transport provider could not allocate the specified address because it is currently being used.
Action:
Specify an address that is not in use.
57: Unable to Register TLI with CLIB; TLI cannot load successfully.
Source:
TLI library
Severity:
This is a fatal error.
Action:
Contact a Novell support provider.
62: The internal consistency check on the TLI error message table has determined that the table is not large enough to hold all TLI error messages; TLI cannot load successfully.
Source:
TLI library
Severity:
This is a fatal error.
Action:
Contact a Novell support provider.