Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/105018

From BetaArchive Wiki
Knowledge Base

Article ID: 105018

Article Last Modified on 10/30/2006


  • Microsoft Mail Gateway to X.400 3.2

This article was previously published under Q105018


When using the new Microsoft Mail Gateway to X.400 utility TTXT.EXE, you may get the following error message:

Could not activate local TSAP


A transport service access point (TSAP) is the point at which the application (in this case TTXT, but normally X400GATE.EXE) hooks into the network transport.

The message indicates that the TTXT utility tried to activate a TSAP, but could not do so because the TSAP was unavailable (for instance, it was already being used by another process). TSAPs must be unique for each process running on the local system. Occasionally, all system TSAPs are in use or otherwise unavailable.


Retype the command line. Specify a TSAP that is available. Otherwise, restart the system and try again.


The Microsoft Mail Gateway to X.400 provides a new transport level not available in previous releases: TP4 or connectionless protocol (CLNP). TP4 also supplies testing and diagnostic utilities.

usage: ttxt -n rx_nsap [-d] [-v] [-q] [-e] [-b size] [-c ntc]
                       [-s interval] [-r rx_tsap] [-t tx_tsap]
                       [-x cmds] [-u driver]
-n: rx_nsap specifies the receiver NSAP address
-d: do data integrity checking
-v: variable buffer size
-q: quiet (non-verbose) mode
-e: test expedited data transfers
-b: size specifies the receive buffer
-c: ntc specifies number of transport connections
-s: interval specifies the reporting interval size
-r: rx_tsap specifies the receiver TSAP
-t: tx_tsap specifies the transmitter TSAP
-x: cmds specifies number of outstanding commands
-u: driver specifies the device driver to be used

Additional query words: 3.20 errmsg 3.2

Keywords: KB105018