In this File
Product name |
WhatsUp Gold |
|
Version |
v16.3 Service Pack 1 (v16.3.1) |
|
Release date |
July 29, 2015 |
|
The following released with WhatsUp Gold v16.3 Service Pack 1 (16.3.1).
WhatsUp Gold Features
Added Language Packs for the following languages:
For more information, see the WhatsUp Gold Language Pack page.
Defect ID |
Category |
Issues |
DEP-2402 |
User Interface |
Corrected a UI issue with the installer that caused the dialogs to display incorrectly when Windows configuration is modified to appear larger or smaller. |
DEP-2552 |
Installation |
Corrected an issue in which the licensing software failed during the WhatsUp Gold install process on Windows 2012. |
PFM-16540 |
Ports |
Corrected an issue in which high quantities of ports that lingered in the TIME_WAIT state for the Service Bus port (9713) exhausting the available ports on the system. |
WUG-7805 |
Devices |
Corrected an issue that caused WhatsUp Gold to lock up when end users attempted to access Device Status for a device to which he/she does not have the proper permissions to view. |
WUG-8297 |
Monitors |
Corrected an issue in which the conditions for a new WinEvent Passive Monitor were not saved successfully when two "Event ID" conditions, one based on a "<=" value and one based on ">=", were used. |
WUG-8397 |
Monitors |
Corrected an issue in which WMI formatted active monitors were not logging payload messages to the State Change Timeline. |
WUG-8417 |
Monitors |
Corrected an issue that caused the Ping Active Monitor(s) to incorrectly report DOWN and "Ping failed. Error=Invalid access to memory location" to be logged in the State Change Timeline. |
WUG-8959 |
Reports |
Corrected an issue that caused the Active Monitor Outage and Down Summary for Quarterly reports to show an inaccurate Down count of 0. |
WUG-12538 |
Monitors |
Corrected an issue in which an SNMP Active Monitor for Rate Change set to Down would incorrectly change to Up when the configuration dialog was reopened. |
WUG-12797 |
Monitors |
Corrected an issue in which a WMI Formatted active monitor using the %ActiveMonitor.Payload percent variable was not returning values. |
WUG-12811 |
Syslog Message Export |
Corrected an issue in which Syslog messages exported from WhatsUp Gold to Excel were not including the entire payload. |
WUG-12963 |
User Interface |
Corrected an issue in which the 'Message' column of the State Change Timeline was not correctly displaying double byte characters when using a Chinese operating system. |
WUG-12983/14930 |
Reports |
Corrected an issue causing an error to be generated if the start and end times selected are identical when exporting the Quarterly Availability Summary report to PDF with live links. |
WUG-13767 |
Devices |
Corrected an issue in which dynamic groups of devices based on IP address ranges fail due to IPv6 addresses. |
WUG-13890 |
Devices |
Corrected an issue which generated an error when attempting to view device properties for a device with a high number of IP addresses. |
WUG-14120/WVRT-2072 |
Reports |
Corrected an issue in which VMWare Current Utilization dashboard reports were available for all devices. This report only applies to standalone VMware Hosts and vCenter Servers. |
WUG-14786 |
Monitors |
Corrected an issue which could cause the Ping Active Monitor to fail and generate the following error: Ping x.x.x.x failed. Error=Win32 error = 11050. |
WUG-14825 |
User Interface |
Corrected a UI pagination issue that occurred when monitoring more than 500 devices in WhatsUp Gold. |
WUG-14878 |
User Interface |
Corrected a UI issue that prevented the entire 'Comment' column from being displayed or the hover text from appearing in the Active Monitors tab of the Device Properties dialog. |
WUG-14897 |
Discovery |
Corrected an issue that caused a Cisco L3 Router to be discovered as a Wireless LAN Controller. |
Multiple |
Internet Explorer 11 |
Corrected issues related to compatibility with Internet Explorer 11. |
This service pack does not require or introduce changes to the v16.3 operating system and virtual requirements.
This service pack does not require or introduce changes to the v16.3 database requirements.
This service pack does not require or introduce changes to the v16.3 Microsoft IIS requirements.
This service pack does not require or introduce changes to the v16.3 framework and accessibility requirements.
16.3.1 added support for Microsoft Internet Explorer v11.
This service pack does not require or introduce changes to the v16.3 supported virtual environment requirements.
This service pack does not require or introduce changes to the v16.3 wireless supported requirements.
This service pack does not require or introduce changes to the v16.3 Flow Monitor requirements.
This service pack does not require or introduce changes to the v16.3 poller requirements.
Note: WhatsUp Gold v16.3 Service Packs support direct upgrade installations from:
-WhatsUp Gold v15.x
-WhatsUp Gold v16.0.x
-WhatsUp Gold v16.1.x
-WhatsUp Gold v16.2.x
This release is a full install and may be installed without first installing WhatsUp Gold v16.3. Refer to the Installing and Configuring WhatsUp Gold guide for details about installation, upgrade, repair, and uninstall.
WhatsUp Gold version 15.0 and later provides integration with the WhatsUp Event Log Management central database. For access to the reports and data, you must also have WhatsUp Event Log Management products, specifically WhatsUp Event Archiver and/or WhatsUp Event Alarm, configured to send collected log data to a MS SQL Server. WhatsUp Gold accesses report data through stored procedures in the ELM database. For more information, see Using Event Log Management Reports in WhatsUp Gold.
Potential SQL Server Express installation errors
WhatsUpGold_User
account on the WhatsUp Gold server can cause a generic 503 Service Unavailable Error to be displayed after the WhatsUp Gold installation. To correct the error and verify/restore applicable settings, see Group Policy Object 503 Service Unavailable Error.WhatsUp
" instance)Configuring the firewall to allow WMI traffic
WhatsUp Gold uses Windows Management Instrumentation (WMI) to monitor and restart Windows Services. For each device that is assigned an NT Service Active Monitor, you must supply the Windows credentials. Also, when creating a Service Restart Action, you must supply Windows credentials for each Action. Credentials must have administrative permissions on the remote server. Local accounts with credentials that match remote accounts are no longer required to monitor remote servers.
Credentials are configured in the WhatsUp Gold Credentials Library and used in several places throughout WhatsUp Gold. They can also be associated to devices in Device Properties > Credentials, or through Bulk Field Change for Credentials.
The use of WMI could have some implications if target devices are behind a firewall. To successfully monitor and/or restart NT Services, you need to modify firewall settings so that:
For more Troubleshooting information, see the Troubleshooting section in the application Help or refer to the WhatsUp Gold Support Site.