BI Tools Task Scheduler

Hello,

We are attempting to set multiple scheduled tasks into Windows Task Scheduler from BI-Tools. We have generated the scheduled task script and everything seems to run fine when "Run Only when user is logged in" is selected.

However, since servers reboot and sessions get logged out, we would like this task to "Run Whether user is logged in or not". Whenever this option is selected, the report does not run.

Below are the item's we've tried to diagnose this:

1) Configure the task to run as a service account with the allowed permissions inside group policy to log on as a service.

2) Configure the task to "Run with highest privileges"

3) Place the command into a .bat file and schedule Windows to execute

4) Place the command in a PowerShell file and schedule windows to execute with the "No-NewSession" and "-ExecutionPolicy Bypass" flags

For the last test, I placed the command into a PowerShell file and had it write the output to a log file in order to see if any errors were being encountered during the execution. Below is a copy of the transcript which shows no errors in execution..... We just never get the emails,

To confirm, the report command is working fine, it just doesn't work when "Run weather user is logged on or not" is selected" 

Any assistance would be appreciated.

Thanks in advance

  • I'm not sure if it applies to your situation, but we inherited a script written using Excel macros to reformat a file, and it would only run when the right disconnected session was running.  The core problem was that Excel simply can't run without a user session.

    If the functions you're trying to automate touches Excel.exe at all, that could be the problem.

  • in reply to Kevin M

    Hi Kevin,

    Thank you so much for the prompt reply! I am unsure the specifics of the function as I am the IT administrator for this company working with the Sage support provider. I do know that it generates an email which gets sent to many of the users in accounting.

    I will pass this information along to our Sage support provider and see if this is something we can work around. I will post any follow-ups which we have.

    Thanks again