Most of the jobs run fine without issue.  I have two jobs that are always Killed (Condition: execution lasts longer than 300 seconds) when automatically run in ad Tempus but DO EXECUTE properly when I manually Run the Job in the ad Tempus console.

Normally the Jobs run in the early morning (between 2am & 5am) AFTER the databases are done updating.  When I come in they've failed (been Killed).  I open the console, right click on the particular Job and Run... it.  Works fine, no problems whatsoever.  During testing I would exit ad Tempus and logoff.  I wait the appropriate amount of time (before the 5 minute Kill condition) and re-logon to the server.  I get an MS Excel error stating "Excel cannot complete this task with available resources.  Choose less data or close other applications".  There is only an OK button and this must be clicked for Excel to continue.  This leads me to believe that something is happening during the virtual logon with ad Tempus.  The virtual logon is the same as the admin logon and it works fine with other Jobs that are being executed by ad Tempus.

Additional info:
1. Windows XP with SP2
2. MS Excel 2002 with SP3.  Using VB code to update a workbook and DISPLAYALERTS = FALSE is in the code.  The VB code is used in other workbooks without issue and it's very small (it simply performs a REFRESHALL on the pivot tables, nothing complex and no huge data pull).
3. ad Tempus 2.0.3.0 (latest version)

I'm at my wits end on trying to solve this issue.  Help?!