If you have customised SuperWEB2, then you must make sure that any customised resources are available to Job Queue Manager when it processes jobs in the queue.
Changes such as table labels, headings, copyright, file templates, even entire languages, which are available to SuperWEB2 must also be available to the Job Queue Manager instance that runs the job and produces the output table. If Job Queue Manager cannot find a requested resource it will log a MissingResourceException in the server log file, and the job may fail.
The resources that may be needed include the labels.properties configuration files. If you have customised these resources then you must make sure the customised versions are available to Job Queue Manager in <tomcat_home>\webapps\queuedjobservice\WEB-INF\classes