VoIP and Network Quality Manager 4.4.1 Release Notes

The global navigation menu bar is missing.

Netpath cannot access the requested path.

Netpath times out and only shows a single point in time.

A CPU utilization issue on multi-core nodes running Microsoft^® Windows Server^® 2008 R2 when using WMI or the agent polling method.

Orion agent Debian-based Linux packages are missing a space in the version information.

Agents appear connected on the Manage Agents page, but cannot send information back to the server after an upgrade.

Linux-based Orion agents fill the /tmp folders with TaskProperties files.

The Orion agent cannot differentiate between two nodes with the same IP address when one node is behind a NAT.

Cannot add SNMPv3 credentials to poll a Windows node with the Orion agent.

When deploying an Orion agent, the Application Event log has the following error:

The job schedule database file is corrupt....

IPv6 nodes polled with ICMP do not return correct values or are unreachable.

Incorrect time zone information for the southern hemisphere and the alerts are scheduled one hour earlier than intended.

Repeated alert actions stop working after one of the following occurs:

• restarting Alerting Service v2
• modifying an alert action
• losing the connection to the database or Information Service v3

Domain users or groups added after an upgrade cannot log in with a error:

SolarWinds.Orion.Web.OrionMixedModeAuth - (null) Failed to retrieve WindowsIdentity for user <user>: System.Security.Authentication.AuthenticationException Cannot logon '<user>' via Interactive/Default.

Repeated alert actions do not trigger when an alert is edited or the alerting service is restarted.

The Node Reboot alerts and event-based alerts do not trigger.

Scheduling for alerts and reports is one hour off.

Some alert actions cannot be simulated and return an error similar to the following:

2017-06-22 08:01:43,724 [140] INFO AlertingLogger - NetObjectData for entity Alerting: swis://example.com/Orion/Orion.Nodes...olumeID=#####/
ForecastCapacity/EntityType="Orion.Volumes",MetricId=3 (AlertObjectId = ) does not exist. Alert action ###: 'Post to http://192.168.1.1:8081/http/applications_solarwinds' will not be executed.

The Orion Web Console is slow after an upgrade due to SWIS v3 using a large amount of memory.

Account limitations applied to groups intermittently display unwanted nodes.

Some resources are not listed due to HEX-string values in the OIDs.

Saved changes to Network Atlas maps do not display when your Orion server time zone is set to any negative time zone, such as UTC-5.

You are prompted to log in when viewing reports. PDF reports have a screenshot of the Orion Web Console login page or an Unexpected website error.

Performance issues due to deadlock and locking in the OrionServers table.

Custom Object resources are very slow or time out when editing or creating them.

CPU is high for trap services.

Page loading times are high.

Cannot import custom properties for groups to a Worldmap.

When integrated with ServiceNow instances with a large number of customizations, alerts do not work as expected.

Devices do not poll when you are missing SNMP v3 credentials.

Automatic monitoring settings are reset to the default after the Configuration Wizard runs.

Cannot open the Advanced Configuration page.

When copying the default Node Details view, the Quality of Experience and Asset Inventory sub pages do not copy the appropriate resources.

SNMPv3 credentials are not correctly assigned to nodes.

The time does not update in the Orion Web Console.

The Managed Alerts page does not completely load, and you cannot filter alerts.

Alerts created with a disabled user do not work as expected, and the Active Alerts page may be blank or have an error.

ServiceNow integration stops working if you mass edit incidents.

Cannot advance to the next Manage SNMPv3 credentials page.

SNMPv3 credentials can be deleted or incorrectly updated when mass editing nodes that use different polling methods.

Cannot create ServiceNow incidents due to missing roles.

Limitations are not applied correctly to alerts.

Cannot add or search for domain accounts when using LDAP.

ServiceNow incidents re-active.

Volume added using WMI stop polling.

Network Atlas maps load slowly or not at all. You may receive an error similar to the following:

Operation in progress, waiting for a connection...

Device type 1.3.6.1.4.1.9.1.1852 is not completely recognized

Some features, such as the Real-Time Process Explorer, stop functioning on you additional polling engines with the following error:

The Job Engine password files are out of sync.

The Settings page is blank when the default document is disabled in IIS.

The ServiceNow incident resource does not display data.

HTML reports are embedded with What's New in the UI information.

When you monitor multi-core devices with WMI, the polled results are inconsistent and may return errors.

The Orion Service Manager opens with the following message:

Error starting service manager

New Cisco switches (C 2990CX) display an incorrect Machine Type.

The Custom Query resources does not page correctly.

Cannot open Quality of Experience resources in the Orion Web Console or Network Atlas.

L3 polling data is incorrect for some nodes.

The job engine for SNMP polling become unresponsive and polling does not complete.

Large spikes in the Data Transmitted metric on non-US English installations

SQL 2008 and 2008 R2 are no longer supported as your database server as of this release.

SolarWinds recommends that you upgrade directly to SQL 2016 at your earliest convenience.

You cannot install SolarWinds Orion products on Windows Server 2008 R2 as of this release.

SolarWinds recommends that you upgrade to Windows Server 2012, 2012 R2, or 2016 at your earliest convenience.

The current All Active Alerts resources is deprecated. The resource is replaced with the new, enhanced widget All Alerts. You can continue to use the deprecated, legacy resource.

The current Managed Nodes page is deprecated as of this release. A new version is available, but you can continue to use the legacy page.

SolarWinds recommends migrating to the new Managed Nodes page at your earliest convenience.