IBM Support

IC35878: TSM SERVER NAME RESET CAUSES WINDOWS CLIENT AUTHENTICATION FAILURE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • Customer was adding a new TSM server to his operation. He
    decided to change his naming convention which requires using the
    SET SERVERNAME command to change the TSM server name. This
    caused all of his Windows clients to become out of synch with
    their generated passwords. The name of the TSM server is part of
    the path in the registry to the stored password the client uses
    to authenticate. When the servername changes, the client looks
    in a new path in the registry for the password key and is not
    able to find one. All Windows clients will fail their backups
    if on a schedule and passwordaccess generate is used until there
    is manual intervention on each client to reset the password
    after the servername change.
    -
    Error messages in the dsmerror.log on the client will be the
    standard login failure messages:
    sesscntl.cpp (3183): sessOpen: Error 137 from signon
    authentication.
    -
    However, the customer should also see this which indicates a
    failure to find the registry key (because the servername is
    now changed and it is part of the path to the key):
    pssec.cpp ( 694): ReadPswdFromRegistry(): getRegValue():
    Win32 RC=2 .
    

Local fix

  • None. Use caution when changing the server name of the TSM
    server using the SET SERVERNAME command. Windows client
    passwords will have to be manually reset at the client to ensure
    scheduled operations can continue.
    ADDITIONAL KEYWORDS:
    authentication schedule fail client servername reset
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager users of version  *
    *                 5.1 and previous releases.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: The SET SERVERNAME command requires     *
    *                      an warning to be added to the books.    *
    *                      Using the SET SERVERNAME command can    *
    *                      have far reaching ramifications.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Using the SET SERVERNAME command can cause client associations
    to be lost and create other problems for the user. The command
    must be used with great respect for the ramifications of
    its use.
    

Problem conclusion

  • Warnings have been added to the documentation and will be
    available in a future release of the product.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC35878

  • Reported component name

    TSM SERVER 510

  • Reported component ID

    5698ISMSV

  • Reported release

    51A

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2003-03-07

  • Closed date

    2003-03-12

  • Last modified date

    2003-03-12

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Publications Referenced
GC32076800 GC32077200 GC23469000 GC32077500 GC23469400
GC32077800 GC32078200 GC32076900 GC32077300 GC23469100
GC32077600 GC23469500 GC32077900 GC32078300  

Fix information

Applicable component levels



Document information

More support for: Tivoli Storage Manager

Software version: 51A

Reference #: IC35878

Modified date: 2003-03-12