You'll need to use the 4.1.1 client, there is an apar out for this issue on
the 4.1.2 client.
James Thompson
----- Original Message -----
From: "Disler Claude, ABX-SERV-ZH" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 31, 2001 5:07 AM
Subject: ANS1029E Communications have been dropped and MSCS
Hi cracks
til 3 days ago, the tsm scheduler of one of my cluster nodes works verry
well.
but now, i've get some errors.
errorlog says:
31-01-2001 12:35:14 sessOpen: Error 137 from signon authentication.
31-01-2001 12:35:14 sessOpen: Error 137 from signon authentication.
31-01-2001 12:35:15 ANS1029E Communications have been dropped.
schedulelog says:
31-01-2001 12:35:53 Querying server for next scheduled event.
31-01-2001 12:35:53 Node Name: Nodename
31-01-2001 12:35:53 Please enter your user id <Nodename>: ANS1029E
Communications have been dropped.
31-01-2001 12:35:54 Scheduler has been stopped.
i removed, and installed the scheduler new, but's always the same.
after the installation of the scheduler, i've got the registry entry of this
node.
but if y start the node with the msc console, the registryentry moves to
hell.
client:
win2k adv. srv with sp1
tsm 4.1.2.0
who has the golden idea?
tx
> Claude Disler
> Abraxas Informatik AG
> Waltersbachstrasse 5
> CH-8035 Z|rich
> Schweiz / Switzerland
> E-Mail: mailto:[EMAIL PROTECTED]
>
