Re: NT SQL Connect Agent
1998-04-16 05:37:47
Chris
Thanks for the reply.
I did as you suggested and here's what I found:-
It appears that you DO need to specify the node name when installing the SQL
scheduler service as otherwise the NT machine name is used. This is actually
documented in the ADSM Central Scheduler readme file.
After installing the SQL scheduler service (using the /node: parameter), using
DSMCUTIL works OK for showing the password. However when you run sqldsmc
/adsmquerydb (which fails the first time), using the DSMCUTIL again shows the
password has disappeared. Re-running "sqldsmc /adsmquerydb" works but this
time using DSMCUTIL shows a completely different password. The scheduler now
fails to start.
Because this is a tad difficult to explain, I have appended the output below.
Thanks & Regards
Phil
D:\ADSM_V3\baclient>dsmcutil install /name:"ADSM SQL Scheduler Service"
/password:client /autostart:yes /optfile:"D:\ADSM_V3\AGENTSQL\DSM.OPT"
/schedlog:"D:\ADSM_V3\AGENTSQL\AGENTSQL.LOG"
/errorlog:"D:\ADSM_V3\AGENTSQL\DSIERROR.LOG"
ADSM Windows NT Scheduler Service Configuration Utility
Command Line Interface Version 1.00.e
Last Updated Mar 2 1998
Command: Install and Configure ADSM Scheduler Service
Machine: DIL005 (Local Machine)
Installing ADSM Client Service:
Machine : DIL005
Service Name : ADSM SQL Scheduler Service
Client Directory : D:\ADSM_V3\baclient
Automatic Start : Yes
The service was successfully installed.
Creating Registry Keys ...
Updated registry value 'ImagePath' .
Updated registry value 'EventMessageFile' .
Updated registry value 'TypesSupported' .
Updated registry value 'OptionsFile' .
Updated registry value 'EventLogging' .
Updated registry value 'ClientNodeName' .
Updated registry value 'ADSMClientKey' .
Updated registry value 'ScheduleLog' .
Updated registry value 'ErrorLog' .
Generating registry password ...
Authenticating password with ADSM for node DIL005 ....
Connecting to ADSM Server via client options file 'D:\ADSM_V3\AGENTSQL\DSM.OPT'
...
Password authentication successful.
The Registry password for node DIL005 has been updated .
D:\ADSM_V3\baclient>dsmcutil remove /name:"ADSM SQL Scheduler Service"
ADSM Windows NT Scheduler Service Configuration Utility
Command Line Interface Version 1.00.e
Last Updated Mar 2 1998
Command: Remove ADSM Scheduler Service
Machine: DIL005 (Local Machine)
Removing ADSM Client Service:
Machine : DIL005
Service Name : ADSM SQL Scheduler Service
The service was successfully removed.
D:\ADSM_V3\baclient>dsmcutil install /name:"ADSM SQL Scheduler Service"
/password:client /autostart:yes /optfile:"D:\ADSM_V3\AGENTSQL\DSM.OPT"
/schedlog:"D:\ADSM_V3\AGENTSQL\AGENTSQL.LOG"
/errorlog:"D:\ADSM_V3\AGENTSQL\DSIERROR.LOG" /node:DIL005_SQL
ADSM Windows NT Scheduler Service Configuration Utility
Command Line Interface Version 1.00.e
Last Updated Mar 2 1998
Command: Install and Configure ADSM Scheduler Service
Machine: DIL005 (Local Machine)
Installing ADSM Client Service:
Machine : DIL005
Service Name : ADSM SQL Scheduler Service
Client Directory : D:\ADSM_V3\baclient
Automatic Start : Yes
The service was successfully installed.
Creating Registry Keys ...
Updated registry value 'ImagePath' .
Updated registry value 'EventMessageFile' .
Updated registry value 'TypesSupported' .
Updated registry value 'OptionsFile' .
Updated registry value 'EventLogging' .
Updated registry value 'ClientNodeName' .
Updated registry value 'ADSMClientKey' .
Updated registry value 'ScheduleLog' .
Updated registry value 'ErrorLog' .
Generating registry password ...
Authenticating password with ADSM for node DIL005_SQL ....
Connecting to ADSM Server via client options file 'D:\ADSM_V3\AGENTSQL\DSM.OPT'
...
Password authentication successful.
The Registry password for node DIL005_SQL has been updated .
D:\ADSM_V3\baclient>dsmcutil showpw /node:dil005_sql
ADSM Windows NT Scheduler Service Configuration Utility
Command Line Interface Version 1.00.e
Last Updated Mar 2 1998
Command: Display Registry Password
Machine: DIL005 (Local Machine)
Registry password for node DIL005_SQL = 'client' .
Authenticating password with ADSM for node DIL005_SQL ....
Connecting to ADSM Server via client options file 'D:\ADSM_V3\baclient\dsm.opt'
...
Password authentication successful.
D:\ADSM_V3\baclient>cd ..\agentsql
D:\ADSM_V3\Agentsql>SQLDSMC /ADSMQUERYSERVERS
ADSTAR Distributed Storage Manager
ADSMConnect Agent for Microsoft SQL Server - Version 1, Release 1, Level 0.0
(C) Copyright IBM Corporation 1990, 1997. All rights reserved.
ADSM API Version: 3, Release: 1, Level: 3
ADSM Nodename: dil005_sql
Server Options
------------------------------------------------------------------------------
-----
dsm Nodename dil005_sql
dsm Nodename dil005_sql
Compression Off
PasswordAccess Generate
WaitMount True
commmethod TCP/IP
tcpserveraddress dil001
tcpport 1500
D:\ADSM_V3\Agentsql>SQLDSMC /ADSMQUERYDB
ADSTAR Distributed Storage Manager
ADSMConnect Agent for Microsoft SQL Server - Version 1, Release 1, Level 0.0
(C) Copyright IBM Corporation 1990, 1997. All rights reserved.
ADSM API Version: 3, Release: 1, Level: 3
ADSM Nodename: dil005_sql
Logging on to the ADSM server...
ANS1017E (RC-50) Session rejected: TCP/IP connection failure
D:\ADSM_V3\Agentsql>cd ..\baclient
D:\ADSM_V3\baclient>dsmcutil showpw /node:dil005_sql
ADSM Windows NT Scheduler Service Configuration Utility
Command Line Interface Version 1.00.e
Last Updated Mar 2 1998
Command: Display Registry Password
Machine: DIL005 (Local Machine)
The specified node key wasn't found in the registry .
D:\ADSM_V3\baclient>cd ..\agentsql
D:\ADSM_V3\Agentsql>SQLDSMC /ADSMQUERYDB
ADSTAR Distributed Storage Manager
ADSMConnect Agent for Microsoft SQL Server - Version 1, Release 1, Level 0.0
(C) Copyright IBM Corporation 1990, 1997. All rights reserved.
ADSM API Version: 3, Release: 1, Level: 3
ADSM Nodename: dil005_sql
Logging on to the ADSM server...
SQL Server Database Type Size Date Time ADSM Object Name
--------------------------------------------------------------------------------
-------
-
-
DIL005 master db 17825792 04/14/1998 12:58:02 DIL005
master db 17825792 04/14/1998 12:58:02 04141998125802.d
b
DIL005 master db 17825792 04/14/1998 13:15:28 04141998131528.d
b
DIL005 master db 17825792 04/14/1998 16:06:39 04141998160639.d
b
DIL005 master db 17825792 04/14/1998 16:18:38 04141998161838.d
b
DIL005 model db 1048576 04/14/1998 13:16:01 04141998131601.d
b
DIL005 model db 1048576 04/14/1998 16:30:46 04141998163046.d
b
DIL005 model db 1048576 04/14/1998 16:55:55 04141998165555.d
b
DIL005 model db 1048576 04/14/1998 17:15:18 04141998171518.d
b
DIL005 model db 1048576 04/14/1998 19:00:19 04141998190019.d
b
DIL005 model db 1048576 04/14/1998 23:37:31 04141998233731.d
b
DIL005 model db 1048576 04/15/1998 09:49:59 04151998094959.d
b
DIL005 msdb db 8388608 04/14/1998 12:05:29 04141998120529.d
b
DIL005 msdb db 8388608 04/14/1998 13:16:08 04141998131608.d
b
DIL005 msdb db 8388608 04/14/1998 16:30:52 04141998163052.d
b
DIL005 msdb db 8388608 04/14/1998 16:57:15 04141998165715.d
b
DIL005 msdb db 8388608 04/14/1998 17:15:23 04141998171523.d
b
DIL005 msdb db 8388608 04/14/1998 19:00:25 04141998190025.d
b
DIL005 msdb db 8388608 04/15/1998 09:50:05 04151998095005.d
b
DIL005 pubs db 3145728 04/14/1998 13:16:19 04141998131619.d
b
DIL005 pubs db 3145728 04/14/1998 16:13:09 04141998161309.d
b
DIL005 pubs db 3145728 04/14/1998 16:31:03 04141998163103.d
b
DIL005 pubs db 3145728 04/14/1998 16:37:44 04141998163744.d
b
DIL005 pubs db 3145728 04/14/1998 16:57:27 04141998165727.d
b
DIL005 pubs db 3145728 04/14/1998 17:15:34 04141998171534.d
b
DIL005 pubs db 3145728 04/14/1998 19:00:36 04141998190036.d
b
DIL005 pubs db 3145728 04/14/1998 23:36:57 04141998233657.d
b
DIL005 pubs db 3145728 04/15/1998 09:50:16 04151998095016.d
b
DIL005 tempdb db 2097152 04/14/1998 12:34:36 04141998123436.d
b
DIL005 tempdb db 2097152 04/14/1998 12:56:48 04141998125648.d
b
DIL005 tempdb db 2097152 04/14/1998 13:16:26 04141998131626.d
b
DIL005 tempdb db 2097152 04/14/1998 16:11:33 04141998161133.d
b
DIL005 tempdb db 2097152 04/14/1998 16:14:36 04141998161436.d
b
DIL005 tempdb db 2097152 04/14/1998 16:28:17 04141998162817.d
b
DIL005 tempdb db 2097152 04/14/1998 16:31:10 04141998163110.d
b
DIL005 tempdb db 2097152 04/14/1998 16:57:34 04141998165734.d
b
DIL005 tempdb db 2097152 04/14/1998 17:15:41 04141998171541.d
b
DIL005 tempdb db 2097152 04/14/1998 17:29:12 04141998172912.d
b
DIL005 tempdb db 2097152 04/14/1998 19:00:43 04141998190043.d
b
DIL005 tempdb db 2097152 04/15/1998 09:21:33 04151998092133.d
b
DIL005 tempdb db 2097152 04/15/1998 09:50:23 04151998095023.d
b
D:\ADSM_V3\Agentsql>cd ..\baclient
D:\ADSM_V3\baclient>dsmcutil showpw /node:dil005_sql
ADSM Windows NT Scheduler Service Configuration Utility
Command Line Interface Version 1.00.e
Last Updated Mar 2 1998
Command: Display Registry Password
Machine: DIL005 (Local Machine)
Registry password for node DIL005_SQL = 'êæ=,? ê+A(r)ð»;ùIç-?ðiPºáV¥1ئÛP"?ù%Ø'
.
Authenticating password with ADSM for node DIL005_SQL ....
Connecting to ADSM Server via client options file 'D:\ADSM_V3\baclient\dsm.opt'
...
Authentication of the specified password failed .
Password Authentication failed.
D:\ADSM_V3\baclient>
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: NT SQL Connect Agent, (continued)
- Re: NT SQL Connect Agent, Chris Zaremba
- Re: NT SQL Connect Agent, Kerssen, Larry
- Re: NT SQL Connect Agent, Del Hoobler
- Re: NT SQL Connect Agent, Kerssen, Larry
- Re: NT SQL Connect Agent, Del Hoobler
- Re: NT SQL Connect Agent, Phil.Chissell
- Re: NT SQL Connect Agent, Virginia Hysock
- Re: NT SQL Connect Agent, Del Hoobler
- Re: NT SQL Connect Agent, Phil.Chissell
- Re: NT SQL Connect Agent, Chris Zaremba
- Re: NT SQL Connect Agent,
Phil.Chissell <=
- Re: NT SQL Connect Agent, Phil.Chissell
- Re: NT SQL Connect Agent, Del Hoobler
- Re: NT SQL Connect Agent, Chris Zaremba
- Re: NT SQL Connect Agent, Del Hoobler [SMTP:hoobler
- Re: NT SQL Connect Agent, Chris Zaremba [SMTP:zaremba
|
|
|