The latest Report Runner Event Server 2030.400 release is a substantial update focused on something that matters a lot for a service designed to run unattended: reliability.
You won’t see a dramatically different interface. Instead, we spent our time improving what happens behind the scenes—fixing rare timing problems, making processing more resilient, improving monitoring, and shaving seconds (and half-seconds) off operations throughout the service.
A Better Way to Know Everything Is Running
One of the biggest additions is the new Heartbeat Check in Windows Event Viewer. Every few minutes, Event Server records a snapshot showing that the service is alive and what it’s doing—including Input queue scans, XML files launched, running processes, and the status of Mail, File, and SQL rules.
If something remains wrong, such as an unreachable Input queue, the problem continues to appear in each heartbeat until it’s resolved. That means an ongoing problem can’t simply disappear as newer log entries push it out of view.
Event Server can also now identify hung processes. A process still running after 23 hours is assumed to be hung, ended automatically, and logged. The timeout is configurable if 23 hours doesn’t fit your environment.
Smarter Queues and More Independent Processing
Several changes make Event Server better at keeping work moving.
If the same XML file fails three times, it’s now automatically moved to the Error queue rather than being retried indefinitely. File and SQL rules also run independently, so a long-running SQL rule no longer holds up File rules—or vice versa.
Process capacity is now reserved for active Mail, File, and SQL rules as well. This helps ensure those rules continue running on schedule even when Event Server is busy processing other work.
Temporary network problems are handled more gracefully, too. For example, losing access to an AutoPrint folder no longer disables AutoPrint until the service is restarted. Event Server waits, keeps checking, and resumes automatically when the folder becomes available again.
Faster and More Reliable Under Load
A lot of work went into eliminating the kinds of rare problems that are difficult to reproduce but important to fix.
We corrected a startup timing issue that could occasionally leave the Windows service showing Running while it wasn’t actually doing anything. We also fixed overlapping scan cycles that could potentially launch the same XML file twice, stranded process slots after failed launches, and problems that could interfere with rules when an Input directory became unavailable.
Input queues containing large numbers of files are also scanned faster, and unnecessary disk activity has been reduced throughout the service.
Event Server Monitor and Controller Improvements
The Event Server Controller and Monitor received plenty of attention as well.
The Controller now does a better job confirming that start, stop, pause, and resume commands actually succeeded. It also handles service-status and permissions problems more gracefully instead of simply failing or displaying misleading messages.
The Monitor is faster and more resilient with large queues. It keeps your scroll position and selection during refreshes, caches report information instead of repeatedly rereading XML files, and continues working even when a network-based queue temporarily becomes unavailable.
We also improved log-file matching, queue clearing, status indicators, and numerous smaller details throughout both utilities.
Built for the Jobs You Don’t Want to Think About
Event Server exists to watch, process, and react without someone constantly checking on it.
2030.400 is about making it better at exactly that. Fewer edge-case failures, better recovery when something goes wrong, clearer information when you need to troubleshoot, and better performance the rest of the time.
If you already have a recent Event Server installation, you can update just the executables rather than performing a complete installation.