Ben,
Things to check:
1) Set trace on agent
2) Check to login object
3) Try to log into DB manually with id/password that Automic is using to ensure the password has not been changed on the DB side.
My experience has been with passwords on login objects. We use login objects with our connection objects instead of hard-coding user/password.
I understand the confusion. If you have a successful test with the object then why the issue if you are using that object? A trace is your first best bet in helping to determining the root cause.
Good Luck.
------------------------------
Cheers,
Gary Chismar
Manager, Automic, PeopleSoft HCM/FI
Florida State University
Florida
------------------------------
Original Message:
Sent: 10-17-2019 04:03 AM
From: Benedikt Weiler
Subject: SQL JOBS not working
Hi guys,
i am struggling with the SQL JOBS since today.
Using AE/AWI 12.3
Error message:
17.10.2019 09:55:59
U00011003 Job 'JOBS.GENERIC_SQL_COMMAND' (RunID '0003166062') on Host 'SQL_MSSQL_01' aborted (return code='0102'). Remote status=Waiting for Database
Agent log (PLOG)
2019-10-17 09:55:44 - U02000005 Job 'JOBS.GENERIC.SQL_COMMAND' with RunID '3166062' started.
2019-10-17 09:55:59 - U02012031 The database driver returned the following error message:
2019-10-17 09:55:59 Integrated authentication failed. ClientConnectionId:c7b617e0-9b9a-4b9c-9707-f8d965e92d9f
2019-10-17 09:55:59 - U02004025 Job-script execution was aborted.
If i do a test in the connection object is saying: Connection test was successful.
Don't know how to start investigating as nothing has changed.
Does anyone has an idea?
Thanks a lot
regards,
Ben