Larry,

Have you tried connecting the TSM Server with the Data Protection
for SQL command-line interface? For example:

     TDPSQLC QUERY TSM

and if necessary.... use the "/TSMPassword=tsmpassword" option.
For example:

     TDPSQLC QUERY TSM /TSMPassword=tsmpassword

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 04/27/2005
04:59:39 PM:

> In preparation for an upgrade of our TSM server from 5.1.7.0 to 5.2.3.0,
I
> have been testing the various clients just to verify that they still
work.
> All was smooth sailing until the test with a TDP MSSQLV2 NT client.  It
> fails authentication with
> 04/27/05 12:14:08     ANR0406I Session 3924 started for node
CTNHDCA02_SQL
> (TDP
>                         MSSQLV2 NT) (Tcp/Ip 147.185.2.195(3706)).
(SESSION:
> 392
>                        4)
>
> 04/27/05 12:14:08     ANR0424W Session 3924 for node CTNHDCA02_SQL (TDP
> MSSQLV2
>                         NT) refused - invalid password submitted.
(SESSION:
> 392
>                        4)
>
> 04/27/05 12:14:08     ANR0403I Session 3924 ended for node CTNHDCA02_SQL
> (TDP M
>                        SSQLV2 NT). (SESSION: 3924)
>
> I have used the "dsmcutil updatepw" to make sure the stored password
matches
> the value I set on the TSM server, and I am certain that I enter the
correct
> password when prompted on the client side.  The client is NT 4.0 with
TSM
> 4.2.2.0 b/a version, and the standard node backups work with the new TSM
> server.  Something else that looks unusual is that although the node
fails
> authentication, the "Invalid Sign-on Count:" is always 0.
>
> It is not likely that the client could be upgraded, so we may have to
forego
> using the TDP.  I would appreciate any suggestions or ideas on how to
> salvage this barge.
>
>
>                      Node Name: CTNHDCA02_SQL
>                       Platform: TDP MSSQLV2 NT
>                Client OS Level: (?)
>                 Client Version: (?)
>             Policy Domain Name: SERVER
>          Last Access Date/Time: 04/27/05 12:47:45
>         Days Since Last Access: <1
>         Password Set Date/Time: 04/27/05 10:39:56
>        Days Since Password Set: <1
>          Invalid Sign-on Count: 0
>                        Locked?: No
>                        Contact:
>                    Compression: Client
>        Archive Delete Allowed?: Yes
>         Backup Delete Allowed?: Yes
>         Registration Date/Time: 04/27/05 10:39:56
>      Registering Administrator: MCNUTT
> Last Communication Method Used:
>    Bytes Received Last Session: 0
>        Bytes Sent Last Session: 0
>       Duration of Last Session: 0.00
>    Pct. Idle Wait Last Session: 0.00
>   Pct. Comm. Wait Last Session: 0.00
>   Pct. Media Wait Last Session: 0.00
>                      Optionset:
>                            URL: http://client.host.name:1581
>                      Node Type: Client
>     Password Expiration Period: 0 Day(s)
>              Keep Mount Point?: No
>   Maximum Mount Points Allowed: 0
>         Auto Filespace Rename : No
>              Validate Protocol: No
>                    TCP/IP Name:
>                 TCP/IP Address:
>             Globally Unique ID:
>          Transaction Group Max: 0
>                Data Write Path: ANY
>                 Data Read Path: ANY
>             Session Initiation: ClientOrServer
>             High-level Address:
>              Low-level Address:
>
>
>
>
> Thanks,
> Larry McNutt
> The Timken Company
>
> -----------------------------------------
> This message and any attachments are intended for the individual or
entity
> named above. If you are not the intended recipient, please do not
forward,
> copy, print, use or disclose this communication to others; also please
> notify the sender by replying to this message, and then delete it from
your
> system.  The Timken Company / The Timken Corporation