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.