Re: NT SQL Connect Agent
1998-04-14 07:17:09
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>
|
- NT SQL Connect Agent, Kerssen, Larry
- Re: NT SQL Connect Agent, Chris Zaremba
- 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
|
|
|