You should be loading the TSA NLM just before you load ADSM.  On a NetWare 3.x
system, it is either TSA311 or TSA312, depending on your release.  On a
NetWare 4.x system, it is TSANDS.NLM. I am not familiar with TSANDS, but the
TSA31x NLMs also autoload SMDR.NLM.

If you are trying to remotely attach to a server - the TSA modules must also
be loaded on those machines.

Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Temporary Novell Connection Failure
10-03-96 05:33 AM

Does anyone see the following, which happens fairly frequently
on our Novell ADSM clients -- ones running both NetWare 3
and Netware 4 --- when starting a scheduled backup.

An error ANS4972E (highlighted below) is *always* followed after
a few seconds by a successful connection between client and server.
The ADSM server is 2.1.0.8 running under AIX 4.1 on an RS/6000;
the client level is 2.1.0.3.

Thanks,
Bob Douglas
----------------------------------------------------------------------
20/08/96 01:07
20/08/96 01:07
Executing scheduled command now.
20-08-1996 01:07:13 Session established with server OX_HFS:
AIX-RS/6000 20-08-1996 01:07:13   Server Version 2, Release 1, Level
0.8 20-08-1996 01:07:13   Server date/time: 20-08-1996 01:08:34   Last
access: 19-08-1996 09:56:04

20/08/96 01:07
Connecting to a NetWare File System (NSF_OUCS).

20/08/96 01:07
Connected to NSF_OUCS.

****** 20-08-1996 01:07:19 ANS4972E Unable to connect to NetWare target
****** service ''. Make sure the TSA NLM is loaded on the specified machine.
20/08/96 01:07 Connecting to a NetWare File System (NSF_OUCS).

20/08/96 01:07
Connected to NSF_OUCS.

20-08-1996 01:07:22 Incremental backup of volume 'NSF_OUCS\SYS:'
etc etc --- successful backup
-------------------------------------------------------------------------
=========================================================================