Release history
3 releases with fixes since version 16. Show everything
-
Version 16.0.3 Latest Fixes11
Highlights
- CriticalA malformed or invalid API call can no longer cause NetCrunch Server to restart; such calls are answered with an error to the caller instead.
- CriticalJSON data stores enforce their read and write access levels on every call, and read-only sessions can no longer write to them.
- CriticalPicture names are validated, so pictures outside the map picture repository can no longer be read or deleted through a crafted name.
- MajorEnabling or disabling a monitoring pack with several nodes selected applies to all selected nodes.
- MajorFixed a crash caused by weak references being released after the memory manager was shut down.
-
Version 16.0.2 Fixes56
Highlights
- CriticalFixed a crash caused by a race between a sensor view target and its shutdown.
- CriticalLoading an atlas no longer causes an access violation when the license manager is not assigned.
- CriticalOpening the monitor report settings no longer crashes when no counter classes are returned.
- CriticalThe event database no longer crashes when the PostgreSQL server terminates an open connection.
- CriticalThe Web Access server no longer fails to start when its listening port cannot be opened.
-
Version 16.0.1 Fixes30 Features84
Highlights
- Critical[#6750] Adding nodes via script through the NC API no longer fails with `Status code` errors.
- Critical[MJ0038] Windows services excluded via a case-insensitive regex no longer trigger unwanted Service Stopped alerts.
- Critical[MP0035] The alerting script now runs correctly for the NetCrunch Status alert.
- Critical[MP0079] Alerts with time restrictions and disabled mode now close properly instead of staying open.
- Critical[MP0084] Nodes with monitoring disabled no longer generate events.