I believe I have this working now without the session logged in or a desktop window session saved in the system tray. N.B., you are correct it is not a bug but more of a multi-user configuration issue.
First of all, to clarify the operating system I am having this issue with is a Windows Server 2012 and not Windows 7 or 10 for workstations. I did open a ticket with support as suggested on the forum, and we spent 3 plus hours on the issue. The first thing I had to do was change the compatibility for the scheduled tasks to Windows Server 2012. My TAPs were first developed & migrated from Windows Server 2003 using TDP 3.0. I never had this issue until going to Windows Server 2012. Since I was downgrading my run-time user from a full-domain admin to just a regular user, I then had to check the “Run with highest privileges” check box for the scheduled task.
However, I was still having a problem with the tasks showing that they were running and queued up in task manager. I had this same issue with the full domain user account. It tuned out that when I migrated to the new server and started importing the Database Connections from one server to another, the roaming profiles were using DB connections from the import file “My Connections.xml” from a shared folder where all .tas projects and supporting files were being stored. Actually, Toad would grab that file and copy it to each c:\users***\username***\AppData\Roaming\Quest Software\Toad Data Point 3.6\ folder rather than making a “Connections.xml” file that is needed for this version of TDP. Some of the DB connections were missing as projects were developed/migrate over time. The Connections.xml file subsequently need to be copied to each user folder including the c:\users***\default***\AppData\Roaming\Quest Software\Toad Data Point 3.6.
We also continued testing and re-scheduled the project via TDP. I was still having issues and discovered the target file for this particular project was a .xls file created with DB queries that are exported correctly but the email was failing. Checking the log file generated, we discovered we needed to create an “Automation” subfolder under each user folder. Support believed that since these projects were first developed under older version, they were not using the “Automation Publishing” subfolder that is now used with the newer version (or vice-versa) if a new project was created. This “Automation” subfolder subsequently needed to be created to each user folder including the c:\users***\default***\AppData\Roaming\Quest Software\Toad Data Point 3.6.
I have tests running daily now and will see how it goes. The lesson I learned on supporting a multi-user environment for the same projects is to keep all of the AppData in-synch.
Thanks for everyone’s input on this issue!