Imanami Community

We've been running a job that synchs an HR DB (SQL) with our AD.  It's been running flawlessly for about 18 mos.  Within the last week or so it began failing every time.  The connection to SQL is made via an ODBC System DSN.  I verified with our DB team that the account still has the credentials on the DB server.  When the job runs unattended, it immediately fails and this is what I see in the log:

Error running job: Failed during startup: ERROR [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

This looks like the DTM server is not passing credentials to the SQL server for authentication.  Google hasn't been too helpful on this.  What's even stranger is that when I log into the server with the DTM service account, the ODBC test connection shows as successful, and I can even run the job in question to completion. 

Why does the job succeed when I'm directly logged on, and fail when I am not?  BTW, I've tried creating duplicate DSNs, recreating the job with the new DSN, and the results are the same.

The DTM account is a member of the local server admins, and has 'log on as a service', 'log on as a batch job', and 'act as part of the OS' perms.

Does anyone have any idea of what I'm missing?  I need to get back to having this automated VERY quickly, so PLEASE help!

Thanks.

Do you log on to DTM Server with the same account as the account provided for scheduled task?

Try running the scheduled task with another account.

Please also see if your SQL Server is in 'Windows Authentication Mode' or in 'Mixed Authentication Mode (Windows and SQL Server)'.

Great suggestion.  I checked the account creds under which the scheduled task was supposed to run and it was set to:  "NT AUTHORITY\SYSTEM".  I changed the scheduled task credentials to use the actual service account for the job (which DOES have the perms on the SQL box) and set it for a couple minutes in the future and it seemed to run just fine.  Don't know how that got changed (or if it did at all) - I certainly don't recall doing it.  Strange. Obviously something wasn't being passed through to the SQL box, but I thought the DTM job would do that with the 'source' setup.  OK.  Problem seems to be solved.

 FWIW the SQL Server is in 'Mixed' mode. 

Thanks webmister!