What authorities/permissions are needed for the Report Runner Batch User when creating and running a scheduled task?
A Report Runner Batch User manually running a batch needs read/write access for primarily two things:
1) All settings for Report Runner are stored in the Jeff-Net data folder
in the "Public" Documents and Settings folder (by default). The user needs full read/write/delete there.
2) Any other read/write settings are simply based on where the user is trying to read data from and write output to. Users will need write/delete to those areas.
As for the Windows Scheduler (which our built-in Scheduler talks/interfaces with), if the user uses a Windows ID/password combination, the scheduler generally has access to whatever it needs. In contrast, if they use the basic "System Account", it ONLY has access to local resources. For example, it would not be able to read a report file on a network drive or output a report to a network location.
When trying to save a schedule, you might get the error... Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
The error can be a bit misleading, because sometimes the ID/password you're entering is correct. Windows gives that error for pretty much any "saving" error to the Windows Task Scheduler.
If you have problems saving a schedule in our Scheduler, and the ID/password is correct (or you're using the SYSTEM account), verify the following:
1) Make sure the Windows Tasks folder has read/write permissions (full permissions) for the user scheduling the report (whether it's the SYSTEM account or a Windows user account). This folder is located at C:\Windows\System32\Tasks (or whatever the path is on other/later operating systems).
2) Take a look at your security policies and verify, for example, that the "SYSTEM" account has permissions to use the Windows Scheduler (the SYSTEM account does not have access to network resources like UNC paths, but it does not require a password, so many users prefer this account when scheduling):
a. Run gpedit.msc
b. Local Computer Policy, Computer Configuration, Windows Settings, Security Settings, Local Policies, User Rights Assignment
c. Check out "Log on as batch job"; if you're wanting to schedule batches using the built-in SYSTEM account, make sure you see SYSTEM (or any other account you want to use) in that list
d. Also check out your "Deny" rules and make sure SYSTEM (or any other account you want to use) is not listed. An example of a "Deny" rule would be "Deny log on as a batch job"
There are a lot of Windows policies. These are a few to check out. Also, you may have to reboot/re-logon on to your Windows account for these updated policies to go into affect
3) If you've recently changed a password for a Windows account that already has existing schedules, and you need to edit that existing schedule, if you get a bad password error, you may need to manually delete the schedule in the Windows Task Scheduler, then you can successfully save it again with the new credentials using the Scheduler in Report Runner Batch.
4) You may find that running the Report Runner executable (Report Runner Unified.exe) as administrator allows for saving schedules, too. Try right-clicking on executable and setting the "Run As" settings to administrator. We have seen this work even when a user believes they already have administrator rights.
5) If you're using a Windows account to save you scheduled task, make sure the account isn't set up with a blank password. You must enter a password to save a scheduled task (unless you're using the SYSTEM account).
This article may also help with scheduling permissions:
Also, you can check out another knowledgebase article pertaining to successfully scheduled report not working at: