Before running any schedules, as root you need to invoke a client-server action (dsmc q fi is sufficient) to cause a prompt for the password, which will then be stored on the client per "passwordaccess generate".
I'd also suggest advancing beyond the 5.1.5 level, which had a number of problems in general.
Richard Sims
On Dec 9, 2004, at 10:45 PM, nghiatd wrote:
I install TSM ver 5.1.5 server on Win2K and TSM ver5.1.5 client on Linux. I can backup data manual and access through Web client. But I got error message following when I used schedule :
cuGetAuthResult: Authorization failed. Result code: 2
ANS3004E Session for user RMQG_LINUX terminated - invalid password entered
I log on account root and excuted "nohup dsmc schedule 2> /dev/null &" command. And there is "passwordaccess generate" option in dsm.sys
Pls help me to fix it,
