Applicable Versions: All
There can be several causes for a user being able to 'Run a Task now' successfully, but the same task does not complete when scheduled.
The first step would be to enable Verbose Logging so that as much information is displayed in the log file.
The scheduler and the normal DataPA client applications run under different users. When a job is scheduled the Job is picking up the data location from c:\programdata\datapa\config.xml and when the users runs it using Run Task Now it picks it up from c:\users\<username>\appdata\roaming\datapa\config.xml (where <username> is the user that is used when running the Scheduler Maintenance).
In c:\programdata\datapa\config.xml the data location will probably be c:\ProgramData\DataPA.
In c:\users\<username>\appdata\roaming\datapa\config.xml this may be different.
If the user is not an admin user (according to the Windows API) then data location changes will just be written to the users roaming DataPA folder.
The above is more specific to the DataLocation but illustrates the fact that the user running Schedule Maintenance's 'Run Task Now' may not be the user, or maybe using a different Data Location, that is used when the Scheduler process runs the Scheduler uses the Windows Task Scheduler. The user that owns the job will be displayed in the Windows Task/Scheduler Maintenance, this is usually the account 'SYSTEM'. This is the user that needs to have access to the Dat Files through the DataLocation and also the Files.
Given the above the following checks should be carried out:-
- Check access to shared/Mapped Drives
- Check Permissions of Files/Folders
- For certain versions of office ( e.g. Excel 2010 onwards ) a folder "C:\Windows\SysWOW64\config\systemprofile\Desktop" must exist. This is only likely for exporting to Excel where the logging error relates to Excel. For instance ("DataPA_Sched SaveAs method of Workbook class failed").
If you are using 64bit Excel then the folder to create would be "C:\Windows\System32\config\systemprofile\Desktop"
- If the Data Location is set to a DataPA Enterprise Service and user security has been applied to the service then the Scheduler's Security Settings must match an Enterprise Service user. This is the most likely root cause if the Scheduler Log file is displaying "Could not create Client Config object. License is likely Unregistered."