Release date: September 1, 2026
Service build: 26.9.0.689
Configuration Client build: 26.9.0.1772
User Interface build: 26.9.0.1017
Upgrade assessment
Recommendation: Recommended update
Why update now: This release adds calendar-aware, time-based File Action rotation and corrects service operation, OLE DB Database Action shutdown, and SNMP Trap Receiver sender attribution.
If you defer: Existing schedules continue to work, but cannot use the new rotation intervals. Deployments using SNMP Trap Receiver, OLE DB Database Action, configuration reloads, or custom service names retain the operational limitations addressed by this release.
Who benefits most: Administrators who use MonitorWare Agent for time-based file rotation, SNMP-trap processing, database actions, or dashboard-based monitoring.
Upgrade and verification: Update using the normal supported path. Confirm service build 26.9.0.689, test a File Action rotation interval, and, where applicable, verify OLE DB shutdown and SNMP sender attribution.
Important changes
Time-based File Action rotation
- Change: File Action rotation supports seconds, minutes, hours, days, weeks, and calendar months.
- Operational impact: Rotation can align more closely with retention, reporting, and archival schedules.
- Applies to: MonitorWare Agent deployments using File Action.
- Verification: Configure a suitable test interval and confirm the expected file-rotation behaviour.
Service operation and database-action shutdown
- Change: Stop requests are retained during configuration reload, custom Windows service names start reliably, and an OLE DB Database Action shutdown crash is corrected.
- Operational impact: Reduces avoidable disruption during service administration and shutdown.
- Applies to: All MonitorWare Agent installations for service operation; deployments using OLE DB Database Action for the database correction.
- Verification: Reload configuration and stop/start the service during a controlled maintenance window; test an OLE DB-enabled configuration where applicable.
SNMP Trap Receiver sender attribution
- Change: Incoming traps record the actual sender address.
- Operational impact: Source-dependent filtering, correlation, forwarding, and incident handling can use the correct sender identity.
- Applies to: MonitorWare Agent installations using SNMP Trap Receiver.
- Verification: Send a trap from a known device and compare the recorded sender address with that device.
Configuration Client and User Interface
- Configuration Client and User Interface support the new File Action rotation units.
- Rotation settings preserve the configured time unit and warn when a newly configured interval is shorter than five minutes.
- After local Metrics Helper setup, standard users can reload the User Interface metrics dashboard.
- Service-owned older General settings no longer produce unnecessary unknown-configuration indications.
Published errata and known issues
SNMP Trap Receiver sender attribution: ERR-2026-001: Incorrect source address for received SNMP traps documents affected earlier versions, operational impact, and verification guidance.