Nathan,

we copied the necessary files (for dsmcutil) from the baclient directory
to the agentexc directory, and when we ran the command from there, with
the "Clientdir"-option pointing to that directory (agentexc),  the
service was installed without a problem.

Thanks a lot !

Chris




>-----Original Message-----
>From:  Nathan King [SMTP:nathan.king AT USAA DOT COM]
>Sent:  maandag 4 oktober 1999 17:10
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: ADSM Connect Agent for MS Exchange
>
>Chris,
>
>I've seen this problem before and I'm wondering what version of the ADSM
>Client you are using.
>
>I had problems like this where it depended which directory I was in when I
>issued the dsmcutil command.
>Normally this is issued from the baclient directory, but sometimes it only
>worked when I issued the command from within the agentexc directory.
>
>Kinda weird?? I'm wondering if some env. variables should be set for the
>Connect Agent?
>
>Does anyone know if there are any DSM env. variables that should be setup
>for the Connect Agent (Exchange) . The Lotus Notes agent requires some, but
>there's nothing about what the Connect Agent requires.
>
>I've also had the Error initializing API Session when the TCP/IP settings
>were incorrect.
>Check that you don't have a mispelling in your dsm.opt file.
>
>Nathan
>
>        -----Original Message-----
>        From:   Chris De Bondt [SMTP:Chris.De.Bondt AT DVVLAP DOT BE]
>        Sent:   Monday, October 04, 1999 4:00 AM
>        To:     ADSM-L AT VM.MARIST DOT EDU
>        Subject:        ADSM Connect Agent for MS Exchange
>
>        Hi all,
>
>        We downloaded the ADSMConnect Agent for MS Exchange Server version
>1.1
>        level 0A from the web, installation and manually running back-up and
>        restore worked fine, but we encounter a problem trying to define the
>        back-up as a service for NT.
>
>        This the command:
>
>        DSMCUTIL INST /NAME:'adsm exchange agent' /NODE:ADSMCA1
>        /PASSWORD:ADSMCA1 /AUTOSTART:YES
>        /CLIENTDIR:c:\win32app\ibm\adsm\baclient
>        /OPTFILE:c:\win32app\ibm\adsm\agentexc\dsm.opt
>
>
>        And here is the result:
>
>        "ADSM Windows NT Scheduler Service Configuration Utility
>        Command Line Interface Version 1.00.d
>        Last Updated 9-11-1997
>
>        Command: Install and Configure ADSM Scheduler Service
>        Machine: DVVLABEXCH551 (Local Machine)
>
>        Installing ADSM Client Service:
>
>               Machine          : DVVLABEXCH551
>               Service Name     : ADSM Exchange agent
>               Client Directory : c:\win32app\ibm\adsm\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' .
>
>        Generating registry password ...
>        Authenticating password with ADSM for node ADSMCA1....
>
>        Error 189 initializing ADSM API Session .
>
>        Password Authentication failed.
>
>        The Registry password wasn't updated."
>
>        We checked and doublechecked the password, tried with the generate
>        password option on and off,  even set authentication off on the ADSM
>        server to test if this would help, but even then the command seems
>to
>        requiere a password parameter ... when it is supplied,
>authentication
>        fails again .... even though the password is DEFINITIVELY correct.
>
>        Anybody familiar with this problem ? Does anybody know where I can
>look
>        up the API errror codes ? All help is appreciated.
>
>        Chris