Version 2013.137 Released - Report Runner Batch and Report Runner Viewer - Critical Update

1. Critical Bug Fix - A few releases ago, we released an update that fixed a bug in our software (actually the bug is in .Net itself) related to how the scheduler data file (jnSchedules.XML) was saved. We missed updating a side routine that cleans up the scheduler data file when you remove/delete a batch XML using our software. This has been fixed.
2. Along with update #1, previously whenever the scheduler data file was unable to be opened (because it was missing or corrupted), we would automatically create a new scheduler data file. This feature still exists, BUT has been updated to give you a large pop-up message that the file is corrupt and to either restore from a backup or allow Report Runner Batch to create an empty scheduler file for you.
3. New! Email domain validation. Most users will not need this, but if you want to prevent email from ever accidentally going out to domains other than your company domain, we have a way to prevent this now. There is a new JNRRB.INI setting under [Options] called "BatchEmailAuthorizedDomains". You simply set it to the domain(s) that CAN receive email. If a Batch tries to send an email to any other domain(s), the Batch will fail.
4. New! Along with update #3, we did the same thing for Web Portal (which utilizes the Report Runner Batch engine) with the setting of "WebPortalEmailAuthorizedDomains". This will prevent Web Portal users from emailing reports to unapproved domains. These two JNRRB.INI settings are EXCLUSIVE of one another. Both settings are never used together, so you can set different exclusions for both without affecting the other. For example, you can set it so Batch sends to anything (leave Batch setting blank) and Web Portal only sends within your company (Web Portal setting is set to yourcompanydomain.com).
5. Bug Fix for Event Server processed XML files; if Event Server calls Batch engine to run an XML file that no longer exists, the process will no longer hang up. Previously it would loop with 3 second waits "looking" for the XML file. This is rare and something is drastically out-of-sync when this happens (usually happens with new users testing different things). 
6. Added additional error/crash correction routines
7. Added new log file messages

Viewer

1. Added additional error/crash correction routines (semi-critical because it helps prevent bad reports from crashing Viewer application and opening an auto-ticket)
2. Added new log file messages

---