XTS* - Software AG Internal Transport Subsystem Messages

The transport subsystem processing completed successfully.

A server has only XTSconnect entries and no XTSlisten. It is possible for a server to connect only to a proxy, and the warning helps applications determine if XTSlisten is missing.

The transport subsystem failed to load the XTS.MSG file. This file contains text for the error messages; there is an internal table also, so XTS.MSG is not mandatory.

Multiple XtsBindClient calls occurred for the same client. Only the first call is considered.

The receive buffer defined by a transport subsystem send and wait call is not big enough to get all data received by the transport subsystem. A subsequent call has to be made to receive all data.

There is no random file defined for a transport subsystem/Secure Sockets Layer (SSL) application; a random file usage by SSL is highly recommended.

This is a receive callback notification for an incoming connection.

This is a receive callback notification for a disconnection.

This is a receive callback notification for a chirp.

This is a receive callback notification when protocols set by XTSlisten are not supported.

This is a receive callback notification indicating the active message references are deleted when a client disconnects.

This is a receive callback notification for an outbound connection.

This is a notification to the callback routine submitted by XtsRegisterByTargetName or XtsRegisterByTargetId indicating a failure of an XTSlisten URL.

This is a notification to the callback routine submitted by XtsRegisterByTargetName or XtsRegisterByTargetId indicating a failure of an XTSconnect URL.

This is a notification to the callback routine submitted by XtsRegisterByTargetName or XtsRegisterByTargetId indicating an unchirp message was received from another node.

A failure to create a semaphore occurred. Contact Software AG customer support.

A failure to allocate memory occurred. Contact Software AG customer support.

The transport subsystem server is already registered.

A URL with a syntax error was encountered. Check the Directory Server repositories.

A failure to load protocol handlers (for example, Xtstcp.lib) occurred. It was probably caused by a configuration problem. Contact Software AG customer support.

A protocol initialization failure occurred. Contact Software AG customer support.

The specified protocol is not supported by the transport subsystem. This is possibly and error in URL syntax.

A listen failed. Check the log file for protocol-specific errors. This is caused mostly by trying to listen on a port taken by another server.

The accept failed. Check the log file for protocol-specific errors.

The connect failed. Check the log file for protocol-specific errors.

No XTSaccess information is provided for the server to which the application wants to connect. Please add a target definition through the Directory Server.

A failure to create a thread occurred. Contact Software AG customer support

A failure to connect or send data in the time set by the user occurred. To complete the connect or send, repeat the call or increase the timeout value.

A completion code is returned to the send callback routine when send fails. Check the log file for the protocol-specific error code.

An invalid message reference was passed by the user.

A send was interrupted by a client disconnection.

A nonexistent server name was passed by the user. It applies to the transport subsystem statistics and dumps calls.

The client failed to send a handshake message to the server; Error caused by the server going down or a protocol send error.

The server failed to reply to the client during handshaking. This error is caused by the client going down or by a protocol send error.

The client failed to resolve the target name. This error is caused by different names used by the server and the client but with the same address.

The transport subsystem call was submitted before the transport subsystem was initialized. Errors were returned by XtsShutdown, XtsSendMessageByRT, and the transport subsystem statistics call.

The client bind failed because of a protocol send error or because the server went down.

The number of user threads in existence reached the maximum (64). Stop creating new user threads or reduce their time to live (timeout).

The transport subsystem failed to create a new user thread. This is an SMP error, possibly because of the limitations of the number of threads that a system can support. Contact Software AG customer support.

The conversion between wide character and MBNS failed. Contact Software AG customer support.

The target name is a zero pointer. Pass a valid string.

The client name is a zero pointer. Pass a valid string.

The length of the data to be sent is zero, Make the length a positive number.

The target ID value is bigger than "2113929215".

The server-client connection was no longer active when XtsSendByRt or XtsBindClient were called. This error is generated by a client going down during the call.

A client or server disconnection was detected during a transport subsystem call.

An internal transport subsystem hash table error occurred. Contact Software AG customer support.

An allocate/delete thread memory failure occurred. Contact Software AG customer support.

A server registration failed to submit at least one listen or connect. Check the XTSlisten or XTSconnect URL parameters.

An attempt was made to use XtsBindClient over the RAW or XTSDS protocol. This feature is not supported.

This error code is returned when the transport subsystem call does not support the single thread feature. Examples include XtsRegisterServerByName(ID) and XtsGiveThread.

A zero pointer was passed by the user. This is an invalid value.

An internal transport subsystem hash table error occurred. Contact Software AG customer support.

The user exit send routine failed. Check the user exit code.

The user exit receive routine failed. Check the user exit code.

The transport subsystem failed to load the user exit library. Check the environment or the user exit routine names.

This error code is returned when the transport subsystem is in shutdown mode (because XtsShutdown was called by another thread).

The proxy cannot deliver the message because the route timeout was insufficient. Change the route timeout.

The proxy cannot deliver the message because of a route table overflow. Repeat the transport subsystem call.

The proxy cannot deliver the message because the route time to live was insufficient. Change the time to live time.

The proxy cannot deliver the message because of a route failure. Repeat the transport subsystem call.

A null parameter is encountered when a notify callback routine registration is called.

The connection was rejected by the notify callback routine.

The connection was redirected by the callback routine.

A timeout error occurred, but connection is in progress. Submit the call again or increase the timeout value.

An invalid session handle was used by the transport subsystem session calls.

An invalid session handle was used by the transport subsystem session calls.

The count of available converter names failed.

The enumeration of text converter names failed.

The text conversion buffer is not big enough..

No replicated server ports are available .

The load of the transport subsystem converter ending failed.

The text converter interface function could not be resolved.

The ICU converter name to Software AG ECS EDD key conversion failed..

The XDS library used by ADVDIR could not be loaded.

A timeout occurred accessing the Directory Server (the default timeout is one minute).

A failure occurred when setting the ECS environment.

The UDP port selected by user cannot be used (because it is used by another application).

Using synchronous and asynchronous calls on the same channel is not allowed.

The transport subsystem received an unknown buffer from an application.

The transport subsystem function is not supported any longer.

This error is generated when the same server is registered again with a different protocol than the one used when it was first registered.

An internal error occurred, indicating a severe transport subsystem code problem. Contact Software AG customer support.

The transport subsystem failed to load a library (the log file indicates which one).

The key used to retrieve transport subsystem parameters does not exist.

The key used by the user to retrieve transport subsystem parameters from xts.config file does not exist.

The profile is not defined in the Directory Server.

A failure occurred loading a function (the name of the function and the name of the library are in the log file).

The transport subsystem failed to initialize the Secure Sockets Layer (SSL) library. Check the log file for the SSL error messages.

The Secure Sockets Layer (SSL) failed to load the CA certificates. Probable causes include an invalid path specification or nonexistent CA certificates.

No Secure Sockets Layer (SSL) certificate was specified.

The URL-specified Secure Sockets Layer (SSL) certificate has an invalid format.

The URL-specified Secure Sockets Layer (SSL) key file has an invalid format.

The Secure Sockets Layer (SSL) key specified by the user is invalid.

A Secure Sockets Layer (SSL) connect failed (caused by an SSL handshaking error). Check the log file for the Secure Sockets Layer (SSL) error messages.

A Secure Sockets Layer (SSL) accept failed (caused by an SSL handshaking error). Check the log file for the SSL error messages.

A Secure Sockets Layer (SSL) read failed. Check the log file for the SSL error messages.

A Secure Sockets Layer (SSL) write failed. Check the log file for the SSL error messages.

A failure to load the Secure Sockets Layer (SSL) library occurred. Check the environment.

The peer certificate subject name and host name are different, indicating an illegal connection.

There is no local Secure Sockets Layer (SSL) certificate.

There is no local Secure Sockets Layer (SSL) certificate.

There is insufficient user memory for returning the requested data.

The certificate was rejected during verification.

The Secure Sockets Layer (SSL) write or read routines returned an invalid zero value. Contact Software AG customer support.

The Secure Sockets Layer (SSL) write routine returned want read error code. Contact Software AG customer support. This is a transport subsystem internal sequence error.

The Secure Sockets Layer (SSL) read routine returned want write error code. Contact Software AG customer support. This is a transport subsystem internal sequence error.

A failure to open a file occurred. Check if the file exists and that the path is correct.

A URL syntax error occurred. Check the log file for detailed information.

An invalid Directory Service selection was made.

A Directory Service call was encountered with a null parameter.

An attempt to add an incomplete URL record was made.

An unknown XTSDS request was encountered. Check the syntax of the Directory Server call.

A Directory Service delete call failed. Check the log file for detailed information.

An attempt was made to add a record that already exists.

A failure occurred loading a directory service. Check the environment. Contact Software AG customer support.

The target name contains one of the following characters: "#", ".", "[", "]", "=", "\", "\", or "*". The target name is invalid.

An incomplete XTSDS request was caused by a zero value of the target, qualifier, or user data.

The XTSDS server does not have any URL to return for the retrieve call.

An XDS processing error occurred..

No Directory Service rollback was performed..

An OVO error occurred during Directory Service processing.

A one-time setting function was called multiple times. A programs encoding mode cannot change once it is set.

The INIDIR file encoding conflicts with programs encoding.

The file creation failed during Directory Service processing..

A file I/O error occurred during Directory Service processing.

The INIDIR file format was not recognized.

An internal transport subsystem error occurred, generated when a URL is added or deleted from the Directory Server and its size exceeds 65520 bytes.

This message is returned by XtsGetMessage when it cannot find text for a given error code.