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
ct: 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: Erro
Claude,
Had the same problem on a cluster server running client 3.7.2.. Tried updating the
password but still did not workDrilled down to the registry and deleted the
password key for scheduler. Reinstalled scheduler and it worked
arturo
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 ANS10
