Hi there.
I've installed the BAclient and the TDPSql on a win2k3 server.
the dsm.opt file says generate on password.
and if i start up the gui it asks for the password, if i enter the password do a backup and close down the gui and restart it, it no longer asks for a password.
I've updated the scheduler with the same password and it "verifies" the password with the server on install when using the gui.
running the sqlfull.cmd by hand works fine, which pretty much runs
tdpsqlc backup * full /tsmoptfile=dsm.opt
this is not asking for password.
however the scheduler fails with:
ACO5091E PASSWORDACCESS is Generate. Either the stored password
is incorrect or there is no stored password. If you do
not have a stored password, use the -TSMPassword=xxx option
to set and store your password.
running the tdpsqlc backup * full /tsmoptfile=dsm.opt with the -TSMPassword="the right password" works just fine as well.
But still the next day the scheduler has failed.
Any ideas ?
Terkel
I've installed the BAclient and the TDPSql on a win2k3 server.
the dsm.opt file says generate on password.
and if i start up the gui it asks for the password, if i enter the password do a backup and close down the gui and restart it, it no longer asks for a password.
I've updated the scheduler with the same password and it "verifies" the password with the server on install when using the gui.
running the sqlfull.cmd by hand works fine, which pretty much runs
tdpsqlc backup * full /tsmoptfile=dsm.opt
this is not asking for password.
however the scheduler fails with:
ACO5091E PASSWORDACCESS is Generate. Either the stored password
is incorrect or there is no stored password. If you do
not have a stored password, use the -TSMPassword=xxx option
to set and store your password.
running the tdpsqlc backup * full /tsmoptfile=dsm.opt with the -TSMPassword="the right password" works just fine as well.
But still the next day the scheduler has failed.
Any ideas ?
Terkel