This release is a major performance and reliability update for the Monitor and Debugger, plus new features driven by customer requests (including gMSA support for mass credential updates).
---
Monitor and Debugger:
- NEW: Hover your mouse over any job meter to see the Process ID it is measuring (for example, PID 6008); this works in conjunction with Report Runner Batch and Report Runner Viewer, which log the process ID at the top of the log file and in the log file name (allowing you to match up a meter with the correct process and log file)
- NEW: The mass credential update (Windows Task Scheduler Analysis tab) now supports Group Managed Service Accounts (gMSA); enter the gMSA account ID ending with the dollar sign (for example, MYDOMAIN\ReportRunnerSVC$) and leave the password EMPTY -- Windows retrieves the gMSA password automatically from Active Directory
- NEW: Added a new Result value to the Batch, Event Server, and Viewer Analysis tabs: "Log Unreadable" -- the log exists but could not be read (check permissions and/or network share availability); this does NOT mean the job failed... it means the result is unknown because the log could not be read; these rows are also included when showing only unsuccessful logs
- NEW: The CPU meters now show "Blocked" if the application is not running as an administrator, or "Error" if the Windows performance counters on the machine have a problem (instead of a percentage that told you nothing)
- NEW: The status line on the analysis tabs now tells you when logs cannot be found or read (instead of just showing an empty list); an empty list with "Status: Ready" means there really were no logs for the period
- UPDATE: Major performance work throughout the interface... process information is now collected in the background and cached, log analysis reads only the end of each log file, and analysis results are cached so checkbox filtering no longer re-reads every log; the interface stays smooth and responsive even at the 20 process maximum
- UPDATE: The job meters now show each job's share of the TOTAL machine CPU, so the job meters add up toward the overall CPU meter (on a machine with 8 CPUs, one report using a full CPU will show around 12%)
- UPDATE: Monitor reads no longer interfere with live logging; a log still being written by a running job can now be read (it will show as needing attention until the job finishes), and the Monitor can no longer briefly block Report Runner from writing, renaming, or cleaning up log files
- UPDATE: The Windows Task Scheduler Analysis tab loads faster (tasks are read once per refresh and only the next 5 runs are calculated per task)
- UPDATE: The mass credential update now runs in the background with live per-task progress, so the window stays responsive during long updates
- UPDATE: The Batch, Event Server, and Viewer Analysis tabs re-scan the logs every time you click the tab, so the view is always current
- BUG FIX: Fixed the CPU meters "sticking" at 100% when the interface first loads (the first sample now primes the counters behind the "Please Wait" and the meters display real numbers starting with the next refresh)
---
This release ins included in the 2030.1000/1005 Report Runner release.
You can install it on any machine with ANY release, though. This is a standalone application, and here is the direct installer:
https://reportrunner.s3.us-east-1.amazonaws.com/Report_Runner_Monitor_Debugger_Setup.exe
---
This release was tweaked and rebuilt on 09/11/26. If you updated prior to that, please redownload the installer. We fixed a bug where the icon did not always show correctly on the desktop.
