If there are any issues with running a job or reports within a job, error messages will be returned within the UI.
In instances where a job has “hung up” and it will not ever complete, it may take some time for the error message to be displayed.
How long each report takes to run will depend on factors such as number of reports, data volume, number of concurrent reports running, etc. If a report job has not returned results or an error within 45 minutes, contact SysAdmin who can look on the back end for status and assist with next steps.
Report Errors within the UI
- Error = Internal Error on Campaign Reports Server | Cause = An error occurred on Campaign Reports | Action = Contact SysAdmin with Report Job ID(s) information
- Error = Unable to create report entry for: <Report parameters> | Cause = The Scheduler was unable to create this report. It possible that there was a database error | Action = Contact SysAdmin and supply the parameters along with the error and ReportJob ID(s)
- Error = S3 Error: Problem connecting to AWS | Cause = The Scheduler was unable to fetch the completed reports | Action = This could be an issue with a variety of components. Contact SysAdmin and supply the parameters along with the error and Report Job ID(s)
- Error = Java heap space
- Error = Invalid parameters to dateLoad – no data to return.
- Error = Internal Spark Exception | Cause = Unknown | Action = Backend error. Contact SysAdmin and supply the parameters along with the error and Report Job ID(s)
- Error = Cannot obtain minimum year, month from <name> | Cause = This campaign’s data could not be found | Action = Contact SysAdmin and supply the parameters along with the error and ReportJob ID(s) Note: this should not occur via the UI. Since the UI should not be able to submit report requests for non-extant campaigns
- Error = Start time <userStartDate> cannot be after end time <userEndDate> | Cause = As described | Action = Contact SysAdmin and supply the parameters along with the error and ReportJob ID(s) Note: this should not ever be seen in the UI as the UI prevents a user from entering a start time that comes after the end time. Usually if this happens, someone tried to manipulate the system within the UI or after it was submitted to the scheduler
- Error = User entered end time <userStartDate> cannot be before <userEndDate>S3bucket date for campaign
- Error = User entered start time <userStartDate> cannot be after <userEndDate> S3 bucket date for campaign | Cause = No data for time range | Action = Review report parameters and if you know there is data/no errors made when submitting report, contact SysAdmin and supply the parameters along with the error and Report Job ID(s)
- Error = Invalid start date <userStartDate> in the future | Cause = The report’s start date is in the future, so it’s impossible for us to have any data yet | Action = Review report parameters and try again, ensuring the start date/time is in the past Note: This should not be seen by a user. Our system UI and Scheduler should prevent reports from running before the information has been gathered
- Error = No data found for the report parameters provided | Cause = This indicates that we do have data for the indicated time-range, however due to the report types and filters the reports are empty. | Action = Review report parameters and if you know there is data/no errors made when submitting report, contact SysAdmin. Note: do not contact SysAdmin unless you are 100% sure you have checked your work thoroughly and have not made an error
- Error = Internal Error on Spark Server. Please contact SysAdmin.
- Error= Unable to create report entry for: <Report parameters>
- Error= S3 Error: Problem connecting to AWS