Same thing happened to a number of our TDP schedulers
on the cluster.  Re-installing only worked part of the
time, and in a clustered environment, really a pain.
To truly fix it, I ended up modifying the dsm.opt file
and set PASSWORDACCESS PROMPT.
I then schedule a command line backup and set the
password option.
Hardly secure (although only admins have any access to
the server) or elegant, but it appears to work.

Cheers....


--- "Disler Claude, ABX-SERV-ZH"
<claude.disler AT ABRAXAS DOT CH> wrote:
<claude.disler AT ABRAXAS DOT CH> wrote:
> 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:claude.disler AT abraxas DOT ch
> >


_______________________________________________________
Do You Yahoo!?
Get your free @yahoo.ca address at http://mail.yahoo.ca