Skip to main content

Reports failing when run from a batch job: The report to run has not been specified or could not be found.

Reports failing when run from a batch job: The report to run has not been specified or could not be found.

H
Written by Harry Ledger
Updated over a month ago

Known Causes

Resolution

The Service Administrator is not running.

Ensure the Service Administrator is running.

The user does not have permission to the Document Store.

Ensure the user running the batch job has permissions to save files to the specified output directory in the Document Store.

The Temp Folder in the Document Store contains more than 3000 files.

Open the Temp Folder and delete any files that are older than required. Alternatively, you may wish to create a new Folder and move the files from Temp into the new folder.

The batch job is unable to run correctly due to other batch jobs running reports at the same time.

You should ensure that the report batch job which is failing is run with at least a five minute gap from any other batch jobs or report batch jobs.

This will prevent the SQL Connection from being overwhelmed and should allow the report to generate correctly.


Check service administrator settings

You may wish to ensure that the Service Administrator is set to turn on automatically in the instance the server may restart.


Check document store permissions

Ensure that the user who is running the batch kob has the correct permissions on the output file. We have guidance on setting up permissions in the Document Store available.

If this is run automatically rather than manually, then you should check that the Administrator has Update & Delete access to the output folder and Root Category.


Check Temp folder

If the Temp Folder has a significant number of files in it, this could contribute to the issue, as the Crystal Report may not be able to save to the Temp Folder in good time. As the Crystal Report fails to save, the Batch Job can't then process it, resulting in the error.

We advise clearing the Temp Folder out once a month if you are utilising many Batch Jobs to generate Reports. For customers with lower levels of usage, you will likely be able to clear the temp folder every 6 months with no issues.

You can also run a data export in the Admin Tool to identify the number of files in the Temp Folder (recommended).

  1. In the Admin Tool, click Import/Export Data.

  2. Click Create an export definition.

  3. Click Select the data to export.

  4. Change the database to SelectCDMS.

  5. Log in.

  6. Copy the below SQL:

  7. Select Item.[Parent Item Number], Item.[Item Number], Item.[Item Type], Item.[Creator Number], Item.[Created Date], Item.[Is Locked], Item.[System Id], Item.[Inherit Permissions], Item.[Source Type Number], Item.[Binding Field], Item.[Item Id], [Item Version].Title From Item Inner Join [Item Version] On Item.[Item Number] = [Item Version].[Item Number] Where Item.[Parent Item Number] = 1977 Order By Item.[Created Date]
  8. In the top left of the data export window, click Options, Paste SQL from clipboard.

  9. Click Data.

📌 Note: If none of the above applies or still proves to be ineffective, then a restart of the HR Notification Server Service may be needed.

If you need further advice or encounter a timeout error, please raise a new case online and reference the title of this article.

Did this answer your question?