Hej Veli,
this looks really after a network problem you have with this NT client.
That's why the TSM Server cannot connect the client anymore. Can you ping
the client PC from the TSM server?
Error 10054 is a TCP/IP error that means that a connection has been forcibly
closed. The reason for this can be locally on the system, from a network
device or from the remote host.
RC -50 indicates that a connection is lost through errors.
Can you give further explainations about when this error is coming up on the
client (during a backup?). Is the scheulder working on after this error
appears? I can see that you are using prompted mode for the scheduler. Did
you try using polling mode?
Regards, Thomas Anthon-Kiel
-----Oprindelig meddelelse-----
Fra: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]P� vegne af
Viirel� Veli (Samlink)
Sendt: 28. juni 2001 14:54
Til: [EMAIL PROTECTED]
Emne: Error on test TSM-server
Any help is greatly appreciated.
Following error on TSM client:
On client Error.log:
06/25/2001 17:45:38 TcpRead(): recv(): errno = 10054
06/25/2001 17:45:38 sessRecvVerb: Error -50 from call to
'readRtn'.
06/25/2001 17:45:38 RecvSchedPing: Received rc: -50 from
sessRecvVerb
06/25/2001 17:45:38 sessInit: Starting communications
initialization
06/25/2001 17:45:38 sessInit: Transitioning: sInit state ===>
sTRANSERR state
No error on server log.
When next scheduled backup is supposed to occur results error on
server log:
ANR2716E Schedule prompter was not able to contact client NAME
using type 1 (111.22.33.44 1501).
Server: OS/390 V2R8 TSM 4.1.2.0
Client: Windows 2000 MS SQL Server 2000
TSM 4.1.2.12 TDP for MS SQL Server 2.2
Sincerely
Veli Viirel� e-mail: [EMAIL PROTECTED]
Oy Samlink Ab phone: +358-9-133 6746
PL 140 fax: +358-9-520 170
02631 ESPOO mobile: +358-40-715 5361
FINLAND
http://www.samlink.fi
