Re: NT SQL Connect Agent
2015-10-04 17:59:02
Phil,
This is actually a bug in the ADSM API client.
The SQL Agent uses the ADSM API to communicate
with the ADSM Server. The bug has been fixed.
Here is what you need to do to fix the problem:
1. Obtain and install the latest version of the
ADSM API.
2. Copy the new "ADSMV3.DLL" and "DSCAMENG.TXT" file
to the "agentsql" directory. (Replacing the ones
shipped with the SQL Agent.)
3. Reconnect with PASSWORDACCESS GENERATE with the
SQL Agent.
Let me know if you have any problems
Del Hoobler
ADSM Agent Development
IBM Corporation
>> Does anybody else have this problem?
>>
>> I have created a separate ADSM scheduler service for the
>> SQL Connect Agent which seems to work fine.
>>
>> However, setting the password access option to generate
>> for the SQL Connect agent seems to rather confuse the
>> SQL scheduler service as it then appears unable to access
>> the server due to "password errors".
>>
>> I have tried re-installing the SQL scheduler service
>> which then works fine until you manually run the
>> SQL connect agent which then causes the generated
>> passwords to become out of sync. again. It almost
>> appears that the connect agent and the SQL scheduler
>> generated passwords are 2 separate entities.
>>
>> Is there anyway around this?
>>
>> Regards
>>
>> Phil
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: NT SQL Connect Agent, (continued)
- 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
|
|
|