The Default database and archive maintenance job purges the Config Archive folder as expected and the log file no longer shows 0 files deleted.

When the option Direct URLs to JSON vulnerability announcement data files to be automatically downloaded and imported into database is disabled, firmware vulnerability matching updates the last date run as expected.

The performance of impersonation was improved to avoid long loading times for users with large profiles.

The SRD calculation no longer takes into account established ACL rules.

VLANs Ports polling no longer fails due to a broken SNMP VLAN context on a node.

When you add the Search for Nodes widget, and select Status from the Search by drop-down, the search no longer fails.

After adding Aruba Orchestrator and Edge devices, the Job Engine service process memory usage is stable, and the SdWan.Collector.Jobs and Collector.Service.log log files no longer include an error An item with the same key has already been added.

When the response from a Juniper Mist device does not include a MAC address, polling the device no longer fails and the device is not shown as down.

Members of Windows Group Account can change the Hardware Health Sensor temperature units.

After the migration to Timeseries, the FirstUpdate column of Wireless_Clients historical database tables is being properly summarized.

When the settings InterfacesCorrelationEventsRequestRetrievedFields and InterfacesRequestRetrievedFieldsPalo are empty, API polling no longer fails for Alto Prisma SD-WAN devices, resulting in missing VPN connection data.

When the response from an Extreme Networks Wireless Access Point does not include an IP address, polling no longer fails.

The SWIP query to retrieve SD-WAN orchestrator statistics no longer causes SQL Server performance issues, including rapid growth of the tempdb table.

When an Aruba API node has multiple interfaces with duplicate ifIndexes, the interfaces are discovered successfully, and logs no longer include messages such as: 

ERROR SolarWinds.Orion.Core.BusinessLayer.JobSchedulerEventService - (null) Processing of discovery result for profile 4 failed for plugin SolarWinds.Interfaces.DiscoveryPlugin.InterfacesDiscoveryPlugin System.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint 'PK_DiscoveredInterface'. Cannot insert duplicate key in object 'dbo.DiscoveredInterfaces'.

The Aruba EdgeConnect REST Walker no longer fails with an error similar to the following:

Walk unexpectedly finished with exception. The process cannot access the file 'C:\Users\nsell\Desktop\silverpeak_thgrp_com__08222024180247\CompressedPathsMapping.map' because it is being used by another process.

When processing v9 NetFlow from Fortigate devices, NTA no longer displays the following error: 

ERROR SolarWinds.Netflow.Processing.Workflow.PacketProcessingWorkflow - error processing packet System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.

Unmanaged interfaces no longer cause large amounts of DiscoverInterfacesOnNode:Orion.NPM.Interfaces verb invokes.

NTA logs no longer cause high CPU utilization due to a high number of incoming PDU warning messages.

When you upgrade NTA, interfaces are no longer labeled as deleted.

When the Autonomous System resource attempts to display information about Juniper MX480 devices, it no longer fails with the message Error while loading legend.

When a JMX node is added, the connection is established and the list of mBeams is displayed in the wizard.

The Cortex REST API server is limiting TLS renegotiation attempts as expected.

Errors such as the following no longer appear in the OrionWeb.log file:

Property 'Orion.Cloud.Azure.SqlDatabase:AllocatedDataStorage' metadata 'defaultAggregation' definition in SWIS schema is invalid. Cannot parse value 'LAST'.

The SqlDatabaseContextProviderBuilder class is thread-safe and SAM no longer displays errors about the wrong user trying to log in.

All parameters for AWS VPN connections are displayed as expected.

The password variable in a connection string for the PostgreSQL template is resolved as expected.

API Pollers no longer trigger false positive error messages about licensing.

The Performance Analysis (PerfStack) dashboard no longer displays incorrect units on charts for SAM applications.

Azure polling no longer fails with an error ERROR SolarWinds.VIM.CloudMonitoring.Pollers.Azure.AccountAutomonitoringPoller - Unable to get azure VMs.

The account automonitoring job no longer tries to find instances in regions the account does not have access to.

SAM made improvements to prevent slow performance in deployments with a large number of containers.

JMX Monitor on Linux no longer returns an error Java version < 8 is not supported, even though the correct version is used.

Assignment of bulk templates no longer causes duplicates.

Monitoring a large number of cloud accounts no longer causes high CPU utilization on the main polling engine.

After an upgrade, all AppInsight for SQL statistics are retained and any custom retention settings do not revert to their default values.

Attempts to poll Azure load balancers for Azure US Government accounts no longer fail with the following error: 

SolarWinds.Orion.Contract.Exceptions.RestClientException: Failed to request /0887f83c-eb3f-44a1-8ceb-5088172c5750/oauth2/token due to StatusCode: BadRequest

{"error":"invalid_request","error_description":"AADSTS900382: Confidential Client is not supported in Cross Cloud request.

Performance has been improved to reduce timeout errors and slow response times when adding nodes to groups.

When more than one entity has the same Resource Name, the Compute Entities resource on the Azure Overview tab and the Virtual Machines resource on the Azure Compute tab display data correctly.

The maintenance of CDR files no longer prevents VNQM from starting.

When you want to check credentials by certificate, VNQM checks AXL credentials by domain name as expected.

The IP SLA Operation Details page no longer times out if there are many operations.

Job Engines on different polling engines no longer interact.

Operation frequency validation works as expected.

In large deployments with the main polling engine alongside multiple additional polling engines, artificial limitations no longer slow down parallel processing of IP SLA jobs.

Large values in the destSpan_value no longer result in call data being dropped and errors such as the following appearing in the IPSLA business layer logs:

Exception occured on GetFilesInDirectory Method: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. - 2024-09-24 14:41:10,093 [13] ERROR BusinessLayer.Task.CdrCmrCsvFileReader (null) - Cannot convert int value [column:destSpan,rawValue:4134469638]”.

When you are monitoring a gateway, the Calls by Region widget in the VoIP Summary View no longer displays an error message.