Skip to content
  • There are no suggestions because the search field is empty.

Fixed Issues in 12.0 Release

Tags: Documentation, Version 12.0

Fixed Issues

This section lists issues fixed after the last major release. For additional information on fixed issues, see the Fixed Version column in the NetWitness® Platform Known Issues list on NetWitness Community Portal.

Administration Fixes

  • Tracking Number: ASOC-114808
  • Description: Multiple operations fail after you enable logging for CRUD operation on app rules and use separate API for ADD, DELETE, and UPDATE.

  • Tracking Number: ASOC-113813
  • Description: The Jobs (Admin > System > Jobs) with lengthy queries take a long time to load. As a result, the load time of the Jobs page is affected.

Endpoint Fixes

  • Tracking Number: SACE-17157
  • Description: Network adapter in promiscuous state is not identified due to querying wrong wmi namespace by NetWitness agent.

  • Tracking Number: ASOC-113849
  • Description: Failed icon is displayed beside the agent version (Hosts> Agent History) when there is a time difference between agent and server.

Respond Fixes

  • Tracking Number: ASOC-115196
  • Description: Aggregation syntax count is not displayed in the report, when you try to create a report with metas such as alert.name, alert.severity,count (alert.numEvents).

Core Services (Broker, Concentrator, Decoder, Archiver) Fixes

  • Tracking Number: ASOC-114900
  • Description: Brotil data fails to decompress in Events page (Investigate> Events). When exporting data, it is decompressed but on Events page invalid data is displayed.

  • Tracking Number: ASOC -115052
  • Description: Due to the large size of incoming logs aggregation fails and archiver service crashes. The mem page issue occurs if sessions to be aggregated from log decoder are with large packet andlog sizes.

Reporting Engine Fixes

  • Tracking Number: ASOC -115232
  • Description:

    NetWitness Weekly Scheduled Reports run on a different day after conversion to UTC flows into either the previous or next day for time zones other than the UTC time zone


Log Collection Fixes

  • Tracking Number: ASOC-120851
  • Description:

    After upgrading to 11.7.1.0, WinRM log collection is interrupted due to the conflict in the internal artifact. As a result, logs are not collected from the WinRM server.