There was a problem loading the comments.

Version 2030.990/995 - Report Runner Batch and Report Runner Viewer (.Net 4.8 or Later Now Required)

Support Portal  »  News  »  Viewing Article

  Print

DO NOT DOWNLOAD UNLESS YOU CLEARLY UNDERSTAND THE BREAKING CHANGES IN THIS RELEASE!

 

While we are confident in the stability of this release, there are a few BREAKING CHANGES (not bugs... changes). We have taken a lot of pride in the past of always being backwards compatible and never releasing anything that would break production. This release is different. While everything is still 99% compatible, here are the new/updated features/changes to be aware of BEFORE UPDATING:

 

  1. .Net 4.8 or 4.8.1 is now required. This won't be an issue for most of you, but previously we only required .Net 4.6. .Net 4.8 has been available since 2019.
  2. If you have configured ANY kind of TOKEN PROCESSING previously to send mail (either Microsoft or Google), those tokens will NOT WORK with this release. You need to RE-CREATE your tokens, and the tokens interface now ONLY SUPPORTS Microsoft MSAL/Graph tokens.
  3. If you have configured ANY kind of Microsoft Sharepoint Online processing with an ID and password, that will NOT WORK with this release. Those batch jobs will fail. ALL Sharepoint Online connections are now ONLY token-based, and you must CREATE a token to do the processing. We do NOT SUPPORT ID and password at all for Sharepoint Online accounts any more.
  4. Lastly, if you do use the new Microsoft MSAL/Graph tokens for emailing or Sharepoint Online, and you SCHEDULE the batch, you MUST USE the SAME Windows ID/account to schedule as you did to create the token. You can not, for example, create a token and then schedule with the System account. Microsoft doesn't allow tokens to be renewed by a different account (tokens must be renewed by the same account that created it). We went with personal tokens vs some broader-based token, because they are much easier to manage and approve, and we've found the renewal process to be flawless if the same Windows account is running the account at the time. 
  5. If anyone NEEDS to stay on 2030.980/985 due to not being able to upgrade to .Net 4.8 and/or email/Sharepoint is working just fine... you will not be forced to update. Of course, any of the features/changes below will ONLY be available with 2030.990/995 and later (and of course there will never be any kind separate/extra update to 2030.980/985) should something stop working. 

DO NOT DOWNLOAD UNLESS YOU CLEARLY UNDERSTAND THE BREAKING CHANGES IN THIS RELEASE!

 

---

 


Batch:
 

  1. NEW: .Net 4.8 is now required.
  2. NEW: Global Monitoring now enabled/allowed for all Batch editions.
  3. NEW: 64-bit edition is now available to all users for an additional yearly licensing cost. The 64-bit edition was previously only available to Infinity customers (an Infinity edition is still the most cost-effective solution for most). 
  4. NEW: All token processing now utilizes Microsoft's MSAL/Graph API. This token usage is for sending mail, Event Server Mail Rules (getting/analyzing mail), and Sharepoint Online (upload files) processing.
  5. NEW (B): Improved licensing messages and Licensing Manager messages; for example, if you have a hardware change that breaks your licensing, it will now say so.
  6. Bug Fix: Fixed an issue where a password was still required even when using keys to do FTP connections
  7. Bug Fix (B): Fixed an issue with Event Server activation/deactivation when licensing is modified
  8. Update: For Sharepoint Online configurations, you now always use your root Documents folder and any sub-folder (or any folder at that level -- technically this "root" folder is referred to as a Library). Previously if you had a sub-site, you used that first then the folder. Sub-site URL now goes into main URL only if needed/used. Your Folder setting might look something like: \Documents\Reports\2025\PDFs
  9. Update: All password displaying is now globally disabled. The old setting for HideLogPasswords=0 (to show) no longer works. You must use HideLogPasswords=ForceNo (B) to show passwords in log files. We did this, because we still occasionally see passwords in ticket log files, and usually the customer is unaware that password displaying is enabled.
  10. Update: Upgraded Chilkat library to 9.5.98 (provides functionality for modern SMTP and FTP connections).
  11. Update: Job edit window "Login Information" has been changed to "Database Login" to be more clear about what kind of login information.
  12. Update: Additional and changed log file messages
  13. Update: Added an undocumented INI setting to allow for keeping of utility log files
  14. Update: Modified catastrophic emails, if there is no log file to attach, to show what command line was being called at time of crash
  15. Update: The End of Batch Notification report is no longer bundled with other emailed reports. It will always go out as a separate email now.
  16. Update: Modified a few system messages and pop-ups related to licensing.
  17. Update (B): Modified Global Options, Settings window to remove some paths are aren't modifiable; Also added display of the Web Portal install directory and a Reset option if path needs to change.
  18. Update: If you use ANY tokens, you MUST use the SAME Windows ID to schedule your batch or IT WILL FAIL the first time the token expires.

  
Viewer:
 

  1. NEW: .Net 4.8 is now required.
  2. NEW: Global Monitoring now enabled/allowed for all Viewer editions.
  3. NEW: 64-bit edition is now available to all users for an additional yearly licensing cost. The 64-bit edition was previously only available to Infinity customers (an Infinity edition is still the most cost-effective solution for most). 
  4. NEW: All token processing now utilizes Microsoft's MSAL/Graph API. This token usage is for sending mail.
  5. NEW: LDAPS connections are now available for Viewer Enterprise edition (instead of less secure LDAP)
  6. NEW (B): Improved licensing messages and Licensing Manager messages; for example, if you have a hardware change that breaks your licensing, it will now say so.
  7. Update: All password displaying is now globally disabled. The old setting for HideLogPasswords=0 (to show) no longer works. You must use HideLogPasswords=ForceNo (B) to show passwords in log files. We did this, because we still occasionally see passwords in ticket log files, and usually the customer is unaware that password displaying is enabled.
  8. Update: Upgraded Chilkat library to 9.5.98 (provides functionality for modern SMTP).
  9. Update: Additional and changed log file messages
  10. Update: Modified a few system messages and pop-ups related to licensing
  11. Update: Added an undocumented INI setting to allow for keeping of utility log files

 

 ---

 

DO NOT DOWNLOAD UNLESS YOU CLEARLY UNDERSTAND THE BREAKING CHANGES IN THIS RELEASE!

 

Downloads for 2030.990/995 can be found here:

 

32-bit: https://reportrunner.com/downloads-latest

 

64-bit: Request access via a support ticket if you're licensed for the 64-bit edition.

 

All installers and updaters are now available (as of September 6th, 2025).

 

DO NOT DOWNLOAD UNLESS YOU CLEARLY UNDERSTAND THE BREAKING CHANGES IN THIS RELEASE!

 

---

 

The (B) indicates it was added in Release B which came at a later date than the original release (07/06/2025)

 


Share via

Related Articles

© Report Runner Support