ANS1344E Job is running in the background. Cannot prompt for the Key. 1

[Trana]

Hi,

Because of some errors I upgraded from TSM 5.3.2.0 to 5.5.0.0, now I get:

ANS1344E Job is running in the background. Cannot prompt for the Key.

How do I run the job in the foreground to be prompted for password?

There is currently no password key in the hklm\software\ibm\adsm\currentversion\backupclient\nodes\'nodename'\'servername'\ folder.

I know virtually nothing about TSM so please keep any tips in very simple terms.

Thank you very much,
Trana

 

[ProbablyDown]

Hi there, So assuming you are talking about the TSM client node, you can just open a cmd window cd to the TSM client install dir. (Usually Program Files->Tivoli->TSM->baclient) and enter 'dsmc' at the prompt. That will start the TSM client in the foreground.

Sometimes if I have password problems I will open the dsm.opt file in notes (same path as above) and change 'passwordaccess' from 'generate' to 'prompt' then run dsmc in the foreground (as above). That way it will prompt you for the password. Once you verify that the pw is correct, switch passwordaccess back to 'generate' and run dsmc again in the foreground.

 

[Trana]

Thank you ProbablyDown,

I did what you said and I was prompted for the password and I am now running TSM in the foreground. Basically I'm at a "tsm>" prompt now in my command prompt window. Is that all I need to do, stay in this window until the next scheduled job and then it will prompt for the password?

If the answer is yes, do I have to enter the password quite close to when the schedule run or can I enter it the next morning? (its scheduled at 8pm).

I checked the registry and I still dont have the reg_binary keys named 'Encrypt' and 'Password' even after editing the dsm.opt file to prompt me for the password (and then entering the password after running 'dsmc')

 

[ProbablyDown]

Ok good.. no don't leave it like that, now what you can do is change passwordaccess back to 'generate' and run dsmc again - it will prompt you for the password again, enter it again, then quit again and run dsmc once again. This time, however, you should go right to the tsm> prompt.

After that, you will want to try to reset (stop/start) you TSM Scheduler process in windows services. Altenatively, you can use the 'setup wizard' in the TSM GUI (under 'Utilities' and check 'Help me configure the TSM Client Scheduler') -just follow the prompts- to verify your scheduler process.

 

[Trana]

I tried everything you said but I never got prompted for the password after changing back to 'generate'. I tried again, this time with RUNASSERVICE NO but with the same result.

However, I just remembered that the upgrade from TSM version 5.3.2.0 to 5.5.0.0 instructions told me to export the node registry keys, for the purpose of rolling back to 5.3.2.0 if neccesary. I just made a backup of my current node registry keys and then I imported the old 5.3.2.0 registry keys, these contain the reg_binary keys 'encrypt' and 'password'. I am hoping this will solve my problem, but of course I wont find out until the schedule runs tomorrow.

Can you see any problems with doing this?

Thanks again for your help and I'll let you know how it goes tomorrow.

 

[ProbablyDown]

Hmm.. I think I ran into something similar on a TDP for SQL node. It happened when I changed the node name - and for the life of me I couldn't get the darn password to change in the registry on the tsm node. I think I ended up deleting the key

from 'nodename' and below (so "\'nodename'\'servername'\")

After I did that I started the client, it prompted for a password and all was well.

Not sure if that is your issue, and again, be careful with the registry here - but I'm sure you know that. Hope it works out

 

[Trana]

My approach didn't make any difference.

I tried deleting the registry node entries and running dsmc with various settings in dsm.opt but no luck.

I'm going to leave it to run with 'runasservice no' for tonights schedule and see if that makes a difference. If that doesn't help I think I'm just going to wait for the regular guy to get back from vacation.

Unless you have any other ideas?

Thanks again for helping.

 

[ProbablyDown]

Hmm if thats the case, you would have to run 'dsmc sched' at the prompt to let it get a schedule..

The only other thing I can think of is to completely uninstall the client and reinstall...

Sorry - sometimes its difficult to tell when you don't have access ;-)

 

[Trana]

Ok, finally solved it.

Pretty basic really.

I created a new file on the server, started up the GUI and backed it up, got prompted for the password and volia, the scheduled backup has run fine since.

Still no reg keys in the registry, but hey, if its not broken dont fix it!

Thanks again ProbablyDown!

 

[ProbablyDown]

Nice job!