Hi Christoph
I had the same problem 2 weeks ago with one of about 5 novell servers
(Netware 5).
When you install TSM client on Novell server it creates a netware group
named "SMS SMDR Group". The group by default is created in the same context
in the Netware Tree, where the server resides. If you change its context
without reconfigure smdr.cfg file, TSM begin to generate the same errors
like this in your mail. That was and my problem. To resolve it, open and
check if the configurations in sys:\etc\sms\smdr.cfg are correct. That mean
context described in smdr.cfg to be the same like the context where "SMS
SMDR Group" resides. This way i solved my problem.
I'll be glad if this help you.
Cyril Todorov
System Administrator
BULBANK AD
7 Sv. Nedelya Sq. Sofia1000 Bulgaria
tel.: +359 2 98412662
email: [EMAIL PROTECTED]
----- Original Message -----
From: Christoph Pilgram <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 20, 2001 12:16
Subject: Problems Netware 5
> Hy all,
>
> last days we had (and have) some problems with clients on Novell.
> Every night one or two (of about 20) novell-server hang after starting a
> scheduled backup-operation.
> The logs say 'unable to connect ...' and it looks as if the client
> continuesly tries to transfer data (but gets no connection to the server).
> On the TSM-server no session to the client is alive after 900 sec
> (CommTimeOut-Parameter).
> If we then try to unload the TSM-Client with "unload dsmcad.nlm" and
"unload
> dsmc.nlm" a message pops up, that you should be sure that there is no
> activity on the client, otherwise the system may hang. If you now unload
the
> nlm's the system breaks and reboots.
>
> Has anybody seen this before and knows how to solve this problem
>
> Thanks
>
> Christoph
>
>
>
> Some Infos about the Systems :
> TSM-Server : AIX 4.3.3 TSM : 3.7.4
> Netware-Client : 5.1 + Service Pack 2A TSM : 3.7.2
>
>
> DSMSCHED.LOG
>
> 06/19/2001 20:18:01 Normal File--> 37,274
> SYS:/SYSTEM/NMA/NTREND/1010.NT [Sent]
> 06/19/2001 20:18:06 Normal File--> 4,506
> SYS:/SYSTEM/NMA/NTREND/1011.NT [Sent]
> 06/19/2001 20:18:09 Normal File--> 37,274
> SYS:/SYSTEM/NMA/NTREND/1012.NT [Sent]
> 06/19/2001 20:18:09 ANS1872E Unable to connect to NetWare target service
> 'THO-DE_FE01.NetWare File System'.
> Make sure the TSA NLM is loaded on the specified machine.
> 06/19/2001 20:18:10 Normal File--> 4,506
> SYS:/SYSTEM/NMA/NTREND/1013.NT ** Unsuccessful **
> 06/19/2001 20:18:10 ANS1809E Session is lost; initializing session reopen
> procedure.
> 06/19/2001 20:18:24 ... failed
>
>
> DSMERROR.LOG
>
> 06/19/2001 20:18:09 ANS1872E Unable to connect to NetWare target service
> 'THO-DE_FE01.NetWare File System'.
> Make sure the TSA NLM is loaded on the specified machine.
> 06/19/2001 20:18:09 (SMDR-5.0-21) The maximum number of connections
allowed
> through the SMDR (64) has been exceeded.
> 06/19/2001 20:18:09 ANS1809E Session is lost; initializing session reopen
> procedure.
> 06/19/2001 20:18:10 ANS1809E Session is lost; initializing session reopen
> procedure.
> 06/19/2001 20:18:24 sessOpen: Session state transition error, sessState:
> sSignedOn.
> 06/19/2001 20:18:24 sessOpen: Transitioning: sSignedOn state ===>
sTRANSERR
> state
> 06/19/2001 20:18:24 ANS1811S TSM session could not be reestablished.
> 06/19/2001 20:18:24 cuFSQry: Received rc: 136 from cuBeginTxn
> 06/19/2001 20:18:24 fsCheckAdd: received error from server query
> 06/19/2001 20:18:24 cuFSQry: Received rc: 136 from cuBeginTxn
> 06/19/2001 20:18:24 fsCheckAdd: received error from server query
> 06/19/2001 20:18:24 cuFSQry: Received rc: 136 from cuBeginTxn
> 06/19/2001 20:18:24 fsCheckAdd: received error from server query
>
> TSM-Server-ActLog :
>
> 06/19/01 20:15:07 ANR2561I Schedule prompter contacting THO-DE_FE01
(session
> 4903) to start a scheduled operation.
> 06/19/01 20:15:09 ANR0406I Session 4905 started for node THO-DE_FE01
> (NetWare) (Tcp/Ip 148.192.2.148(12807)).
> 06/19/01 20:34:02 ANR0481W Session 4905 for node THO-DE_FE01 (NetWare)
> terminated - client did not respond within 900 seconds.
