1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

TSM Client Password Failure on Microsoft Server - FIX

Discussion in 'Backup / Archive Discussion' started by peterbaugh, Aug 3, 2006.

  1. peterbaugh

    peterbaugh New Member

    Joined:
    Mar 18, 2005
    Messages:
    3
    Likes Received:
    0
    TSM Client Password Failure on Microsoft Server - FIX

    Technical Services Group, Carilion Clinic

    Author: Peter Baugh



    Operating system: TSM Client Version 5.3.2.0, running on Microsoft 2003 Server in a two node clustered environment (MSCS).



    Symptoms: After failover to node one, the TSM cluster scheduler failed with the following error: "ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background." Repeated attempts to start the cluster scheduler service then caused the following error: "ANR0430W Session 680406 for node MSCSERVER-A (WinNT) refused - node name is locked.



    Action / Resolution:

    1. Repeated TSM Client Scheduler password failure may be caused by corrupted registry keys. Check entries below the following registry key (for a cluster resource, as below, check the registry on the ACTIVE node).



    HKEY_LOCAL_MACHINESOFTWAREIBMADSMCurrentVersionBackupClientNodes



    Look for the node name key of the TSM service that is failing. Below the node name is MSCSERVER-A.



    [HKEY_LOCAL_MACHINESOFTWAREIBMADSMCurrentVersionBackupClientNodes MSCSERVER-ATSM01]

    "Password"=hex:1e,91,ca,68,58,0c,58,b9,09,29,a4,8d,a7,14,03,a6,1f,56,d4,12,a1,ec,f9,cc,1f,1f,62,b5,05,ca,e6,5b,53,31,16,11,cb,9f,63,f0,16,3a,ad,3a,0c,90, 99,61,1b,55,f2,b6,8e,0c,c7,f1,61,40,6b,34,6e,40,93,87





    2. Highlight the node name key (MSCSERVER-A above), right click and set permissions. Add (domain)\Domain Admins, or your Active Directory user ID. This forces the Microsoft server to update the ACL (Access Control List) for the corrupt registry keys.





    3. Look for the "Password" key in the registry (seen in step 1). This key may be absent due to corruption. If present, delete the key and password, as below.



    [HKEY_LOCAL_MACHINESOFTWAREIBMADSMCurrentVersionBackupClientNodes MSCSERVER-ATSM01]





    4. Find a WORKING key, as below. Highlight the "Password" key and select File-Export to save as a .reg file to a local drive. Your .reg file will look like the example below;



    Windows Registry Editor Version 5.00



    [HKEY_LOCAL_MACHINESOFTWAREIBMADSMCurrentVersionBackupClientNodes MSCServer-BTSM01]

    "Password"=hex:1e,91,ca,68,58,0c,58,b9,09,29,a4,8d,a7,14,03,a6,1f,56,d4,12,a1,ec,f9,cc,1f,1f,62,b5,05,ca,e6,5b,53,31,16,11,cb,9f,63,f0,16,3a,ad,3a,0c,90,99,61,1b,55,f2,b6,8e,0c,c7,f1,61,40,6b,34,6e,40,93,87



    The example above is a working, scheduler password key for the cluster MSCServer-B.





    5. Edit the saved .reg file with notepad, and rename the node name key to the node name of the failing service (example below, change MSCServer-B to MSCSERVER-A).



    Windows Registry Editor Version 5.00



    [HKEY_LOCAL_MACHINESOFTWAREIBMADSMCurrentVersionBackupClientNodes MSCSERVER-ATSM01]

    "Password"=hex:1e,91,ca,68,58,0c,58,b9,09,29,a4,8d,a7,14,03,a6,1f,56,d4,12,a1,ec,f9,cc,1f,1f,62,b5,05,ca,e6,5b,53,31,16,11,cb,9f,63,f0,16,3a,ad,3a,0c,90,99,61,1b,55,f2,b6,8e,0c,c7,f1,61,40,6b,34,6e,40,93,87



    Save your changes and close the .reg file.





    6. Now import the .reg file into the registry.



    7. Set the node name password and unlock the node by updating it with TSM Administrator.



    8. Manually start the TSM client by double-clicking on DSM.EXE. Supply the password if prompted. To do this on a cluster node, you will need to copy the contents of C:program FilesTivoliTSMbaclient to the TSM directory on the cluster drive, taking care not to overwrite the DSM.OPT or LOG files. After supplying the password, exit the TSM client.



    9. Start the TSM scheduler service, or bring the cluster service online with Cluster Administrator, found in Administrative Tools on the cluster node.



    EOF
     
  2.  

Share This Page