Return
-
Title
Scheduled jobs on TIC are no longer running, What is causing all the existing jobs to fail when the server services are run with a domain admin service user? -
Description
Users to use “default user to execute script” option to publish automation script is to have multipleToad Intelligence Central server services to run as a domain service user.
After this change was made, none of the published jobs ran.
Since then, the process was rolled back so that the server processes run as a "Local System User" as before and the jobs were running.
What is causing all the existing jobs to fail when the server services are run with a domain admin service user? -
Resolution
When the user was given a new logid it was in a different domain than what the TIC server is part of.When you publish an automation script, you state who is to be impersonated when running the script on the TIC server.If you put in your domain logid, we logid as that user and start TDP up and run the automation script; in that, all the privileges will work as usual.(i.e.: File paths to network drives, logids to DB servers, etc.)However, if the logid cannot be authenticated, the script will not run and no error email will be emailed.We believe this is what occurred.When you publish the script to be run under system it can always run but may not be able to access the network drives or connect to databases.The success or failure of running a script is determined by the exit code when running TDP by the process explained above.Sometimes this error code is wrong and says the execution failed when what really happened is that we couldn't get the exit code from the windows process.It is suggested to use the “Manage all script" window. In the lower page is the results history. If it has the wrong return code, it will not show the result as an error.