Should your scheduled imports or reports suddenly fail to start, please check the following conditions:
A. The scheduled task starts:
If the task actually starts, it will launch PROMODAG Reports that will generate a new trace file in the application \Logs
folder for that batch session. The path to the \Logs folder is displayed in the Trace & Alert
tab of Tools > Options
If no new trace file can be found in the \Logs folder, verify that:
- The password of the user account set to start the task is correct. Has it been recently reset?
- The command line parameter is /BatchFile=<batch file name>.prb.
- The application started by the scheduled task is the version of PROMODAG Reports you are using. For example, if you are using version 9 and you see that the application started by the Scheduler is Repex.exe in \Reports8, it means that it is an old v.8 scheduled task and that it does not start because you uninstalled that older version.
Test the scheduled task by manually starting it (right-click, Run
B. The batch file starts:
If the task actually started, but the batch file does not run, verify that:
- The user account set to run the scheduled task is the same as the one used to run PROMODAG Reports in interactive mode. For example, if you normally import message tracking files when logged as DOMAIN\Admin1, do not set your scheduled task to run as DOMAIN\Admin2 (see Known issues below). This is the number one source of automation-related incidents.
- The batch file (*.prb) that fails to run is located in the \Batches folder. The path to this folder is displayed in the General tab of Tools > Options.
- The batch file that fails to run can be started in command line mode. For the correct syntax, see the embedded help file and search for 'command line'.
If you are using an Access database and that it is located on a network resource, use a UNC path rather than a mapped path.
For example, if you should connect to a database called PROMODAG.mdb, open it, using the File > Open Database option, as \\SERVER\Share\PROMODAG.mdb rather that D:\Share\PROMODAG.mdb.
A mapped path may not be accessible when the batch job starts (because you are using a different account for which it may stand for another network resource...) while the UNC path always will.
Five Q & A about automating PROMODAG Reports
How to confirm that scheduled operations completed successfully
How to receive an email notification of warnings and errors when automating PROMODAG Reports
How to automate import operations, data purge or database compaction
How to automate report generation