Release Notes for the
"Stable" Release Channel

Software versions in this channel are updated about once a month. In this most conservative channel you receive the best tested versions. We recommend that you use PRTG's stable versions for live environments.

Please use the "Auto-Update" feature to update your PRTG installation: In the PRTG web interface, simply navigate to Setup | Auto Update. You can also obtain the latest version from the PRTG download page!

 

Go to Download Page

Manual: Using the "Software Auto-Update" Function of PRTG

Previous Versions and other Release Channels


calendar

November 25th 2019 – Version 19.4.54.1506


New

Sensors


WMI Disk Health

The new WMI Disk Health BETA sensor monitors the health of virtual or physical disks on your Windows servers. It shows the operational and health status of a disk. It does not matter which disk type, the sensor works with all kinds like SSD, SATA, or SAS, for example. The WMI Disk Health sensor shows detailed information about the operational status like degraded or predictive failure in the sensor message.

With this new sensor type, you will always have a quick and easy overview of the status of your disks.

WMI Storage Pool

The new WMI Storage Pool BETA sensor monitors a storage pool on your Windows servers. A storage pool consists of multiple disks and provides RAID functionality without real RAID hardware. This new sensor type shows the operational and health status of the storage pool, as well as free space, and provides detailed information about the operational status like stressed or relocating.

With the new WMI Storage Pool sensor, you will always have an overview of the status of your storage pool.

Important

Security


Server

This version includes an important security update for your PRTG core server. We recommend that you update as soon as possible. Please find more details in the email we sent to the email address provided in your license information. Special thanks go to Aleksandr Melkikh from Positive Technologies for pointing us to the right direction. (CVE-2019-19119)

Improved

Security


Access Rights

Users with restricted access rights to sensors now only see a sensor's relationship in the Similar Sensors Overview if their user account has access to both related sensors.

Sensors

We fixed a potential Remote Code Execution (RCE) vulnerability of the HTTP Transaction sensor. (CVE-2019-11073)

Server

We fixed a potential Remote Code Execution (RCE) vulnerability of the PRTG core server. Many thanks to Sittikorn Sangrattanapitak - Cybersecurity Researcher, Nuttakorn Tungpoonsup & Ammarit Thongthua - Secure D Center Research Team, Secure D Center Co.,Ltd. for reporting the issue.

Version Number

PRTG does not show the current version number in HTTP headers anymore to improve security by not providing attackers potentially relevant information. For the same reason, the page footer of the web interface now only shows the version number on pages that require a logged in user account.

Fixed

Sensors


MySQL v2

MySQL v2 sensors support user-defined variables in your SQL scripts again. This did not work in previous PRTG versions due to a change in the MySQL library, which added a new connection setting to allow user variables. The sensors showed the error message Fatal error encountered during command execution when running a SQL statement with user-defined variables.

Port

You can now also save the advanced Port sensor setting Goal into custom device templates. The goal of a Port sensor can be an open or closed port to define an up status.

SNMP Library

SNMP Library sensors again create each channel only once. If you selected more than 10 OIDs when adding the sensor in previous versions, the last channel of the sensor created for the first 10 OIDs was also created as first channel of the sensor added for the next 10 OIDs.

Fixed

Server


Cluster

Minor stability improvements for PRTG cluster installations

Data Purging

PRTG now correctly applies the data purging value for Historic Sensor Data even if you define a value that is greater than 1095 days (3 years). In previous versions, PRTG did not purge historic data anymore if you used a value above 1095 days. You can now define a maximum value of 9999 days.

Overload Protection

PRTG will only create one ToDo ticket and one log entry again when overload protection gets activated due to 100 failed logons since the last start of PRTG. In previous versions, PRTG was too noisy with an active overload protection, which could result in way too many tickets indicating that Web server is slowing down login attempts (Protective measure) in some cases.

Reports

  • PRTG now automatically removes temporary files and folders that are generated when running a report to not unnecessarily fill up the disk.
  • The reporter.exe that PRTG uses to generate PDF reports is now signed. This will help to prevent anti-virus software from flagging the exe, as well as you can be assured that the file is really from Paessler.

Search

The PRTG search function works properly again. In some cases, the search did not provide any results in previous PRTG versions and required a restart of the PRTG core server to work.

Sensor Messages

PRTG now correctly shows sensor messages in logs and notifications on status change (for example, due to a breached limit) even in certain corner cases. In previous versions, timing issues could result in logs and notifications just showing "OK" instead of the sensor message in such cases.

Fixed

WebGUI


Libraries

Libraries do not contain buttons to add devices, sensors, or to run an auto-discovery anymore. The buttons had no functionality anyway because libraries are designed for visualization, not interaction.

Maps

The object selector in the map designer to link a map object with an object from the device tree shows the whole tree again. In previous versions, objects at the bottom of the device tree were cut off so you could not select them.

Multi-Edit

You can see and change Sensor Display settings again when you open the settings of one or more sensors via multi-edit.

Updating

The auto-update confirmation dialog window now immediately reacts when you click the Yes, install update now button.

Changed

API


JSON

The value of the notifiesx_raw field returned by the API call api/table.json?content=sensorxref is never null now and always the same value no matter which language. In previous versions, notifiesx_raw could be empty as well. If you use external tools or scripts that use the PRTG API, please keep this change in mind and adjust them if necessary.

Changed

WebGUI


Optional Downloads

The PRTG web interface now also shows download links for PRTG Desktop on the Welcome page and under Setup | Optional Downloads on PRTG instances hosted by Paessler.

Furthermore, we removed the PRTG Tools tab from the web interface section Setup | Optional Downloads. Of course, you still can download our free network tools on our website.

Changed

Clients


Enterprise Console

We no longer deliver the Enterprise Console with the PRTG installer. This change will not affect running Enterprise Console instances, but please note that they may stop working anytime in upcoming PRTG versions. We recommend that you switch to PRTG Desktop soon.

Note: The Enterprise Console might not be able to automatically connect to the PRTG server anymore after you have updated to version 19.4.54 and you receive the error message Server runs incompatible software version. In this case, exit the Enterprise Console as well as the Windows tray and run the Enterprise Console again. If it still cannot connect, run PRTG Enterprise Console.exe with the ignore flag. For more information, see the Knowledge Base article Enterprise Console doesn't connect to PRTG core server anymore after updating PRTG. What can I do?

Note: If you update from an older PRTG version, your Enterprise Console may show an error message asking you to update the Enterprise Console. This will fail because of the missing installer as of PRTG 19.4.54. For your convenience, you can still directly download the latest installer as well as the latest version of the Enterprise Console here and try to manually update: prtg_enterprise_console_54.zip
If you want to update the Enterprise Console on the PRTG core server, extract PRTG Enterprise Console.exe into your PRTG Network Monitor program folder and run it. On other systems, you can just run PRTG_Enterprise_Console_Installer.exe to update. Please note that this is a workaround to keep the deprecated Enterprise Console running if mandatory and may not work in every case.

Improved

Various


All Parts of PRTG

Various other minor fixes and improvements, updated user manual, updated language files

Note

Sensors


Python Script Advanced

PRTG version 20.1.55 that we will publish in January 2020 will include a new Python distribution because of the end-of-life announcement for Python 3.4. We already inform you now about the change because your custom Python scripts must be compatible with Python 3.7 when you update to PRTG 20.1.55.

You only need to consider the change if you are using the Python Script Advanced sensor. PRTG will also create a ToDo ticket with further information for you in this case.

Note

Security


Web Server

PRTG version 20.1.55 that we will publish in January 2020 will include a more strict web server security by default to keep PRTG as secure as possible. TLS 1.2 will be the new default web server connection security.

The change may affect you if your PRTG users or third-party systems use outdated versions of browsers or PRTG mobile apps, the Enterprise Console, or old automation tools that interact with the PRTG API. You will receive a ToDo ticket in PRTG with further information.

Note

Tools


PRTG Certificate Importer

There is a new version of the PRTG Certificate Importer available since December 12, 2019. The new version is compatible with PRTG 19.4.54 and later. Installer and executable are now signed to confirm their integrity. Additionally, we introduced a new versioning system that follows the PRTG versioning, so the current version of the PRTG Certificate Importer comes with version number 19.4.54.

For more details and to download it, please see PRTG Certificate Importer on our website.

calendar

October 29th 2019 – Version 19.4.53.1912


Blog article

PRTG Release 19.4.53 brings version 2 of the SNMP Fujitsu System Health Sensor

PRTG release 19.4.53 has been available in our stable channel for a few days now. Take some time and find out what's new in this version.
Read the complete blog post here



New

Sensors


SNMP Fujitsu System Health v2

The new SNMP Fujitsu System Health v2 BETA sensor monitors the status of a Fujitsu PRIMERGY server via iRMC. It might also work with the Fujitsu product lines PRIMEQUEST, ETERNUS, and CELSIUS if they have iRMC available. The sensor shows useful metrics for CPU usage, fans, memory modules, battery, and power supply of your Fujitsu servers. We are looking forward to hearing your feedback about this new beta sensor! Please send your feedback to [email protected].

Note: The new SNMP Fujitsu System Health v2 sensor replaces the original SNMP Fujitsu System Health BETA sensor and addresses the feedback we received from you about this sensor type. Please note that any previously deployed SNMP Fujitsu System Health sensors will immediately stop working upon updating to PRTG 19.4.53 or later. You need to add the new version of the sensor to continue monitoring your Fujitsu servers. To keep historic data, you can pause existing instances of deprecated sensors.

Improved

Security


Login

We improved the security of the password recovery function on the PRTG login page. PRTG will not provide any information about user accounts anymore when you request a new password.

Sensors

We updated the Npcap library that Packet Sniffer and Packet Sniffer (Custom) sensors use to monitor your traffic. The Npcap version (0.992) distributed with previous PRTG versions included a security issue with an ACE vulnerability (CVE-2019-11490).

Note: Under certain circumstances, the PRTG update process may stop when trying to install Npcap and Windows shows the error message A LWF & WFP driver installation tool has stopped working. In this case, please manually stop npcapoem.exe (for example, via the Windows Task Manager) to continue the PRTG update process. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/86904.

Fixed

Server


Active Directory

PRTG automatically clears the cache for Active Directory integration again. In previous versions, the hourly clearing of the cache did not work so old passwords still worked after changing them until you logged in with the new password or manually cleared the cache.

Cloning

Clones of flow sensors (NetFlow, IPFIX, jFlow, sFlow) are now able to automatically receive data after you have resumed them. If you clone a flow sensor to the same probe, the clone will keep the IP selection as defined in the sensor settings to receive flow packets. If you clone a flow sensor to a different probe, the clone will receive flow packets on all available IP addresses of the probe by default.

Dependencies

You can save settings again even if PRTG detects an invalid Dependency Type on the same page, for example, if a sensor is not existing anymore that was selected as dependency type for the current object. In previous versions, you were not able to save the settings in this case—even if you just renamed the object—because data validation failed and you received the message Error (Bad Request) when saving.

Device Tree

We fixed an issue where the PRTG core server was not able to load the device tree anymore. This happened in rare cases if there were inconsistent or pending internal tree states.

Logging

We fixed an issue where PRTG did not correctly recognize the size of log files in corner cases. The issue could result in a steadily increasing log file size instead of making a copy and recreating the file, so that log files could still become very large in such cases.

Notification Triggers

We improved the performance of the Notification Triggers tab. Actions like adding or removing notification triggers provide feedback considerably faster than in the previous PRTG versions 19.3.51 and 19.3.52.

PRTG Status

The PRTG Status page shows the correct value for StateObjects again.

Scanning Interval

Objects now show the selected scanning interval even if you have deleted this interval from the Monitoring settings.

Shutdown

We improved the shutdown process of the PRTG core server. In certain cases, ending the dependency thread took very long. This could result in a failing automatic restart because the check for successful termination of the PRTG server service could not be performed in such cases.

Fixed

WebGUI


Maps

The map object Device Tree (S) now shows the correct color for the status Down (Acknowledged), just like all other device tree map objects.

Tables

We improved the layout of data tables on sensor overview pages by making the alignment of columns more consistent. The Channel column is always left-aligned as before, all other columns are now right-aligned.

Improved

Various


All Parts of PRTG

Various other minor fixes and improvements to all parts of PRTG, updated user manual, updated German language file

Note

Sensors


Python Script Advanced

PRTG version 20.1.55 that we will publish in January 2020 will include a new Python distribution because of the end-of-life announcement for Python 3.4. We already inform you now about the change because your custom Python scripts must be compatible with Python 3.7 when you update to PRTG 20.1.55. You only need to consider the change if you are using the Python Script Advanced sensor. PRTG will also create a ToDo ticket with further information for you in this case.

As of PRTG 20.1.55, the path that PRTG uses for Python is %programfiles%\PRTG Network Monitor\python3\ on 32-bit (x86) systems, and %programfiles(x86)%\PRTG Network Monitor\python3\ on 64-bit (x64) systems.

Note

Clients


Enterprise Console

We do not officially support the Enterprise Console with PRTG version 19.4.53 or later anymore. Please note that your Enterprise Console may stop working in upcoming versions without further notice due to changes to the PRTG server. Please use PRTG Desktop as successor of the Enterprise Console.

calendar

October 10th 2019 – Version 19.4.52.3515


Fixed

Notifications


Summarized Notifications

PRTG can send summarized notifications again. In previous PRTG versions 19.3.51 and 19.3.52, PRTG only sent the first notification but not the following summarization. The issue affected all notification summarization options of your notification templates.

calendar

October 1st 2019 – Version 19.3.52.3502


Blog article

All You Need to Know About PRTG Release 19.3.51 and 19.4.52

The PRTG release version 19.4.52 has been available for installation in the stable channel for a few days now. Maybe you already have the version in use, or you are planning the update. As regular...
Read the complete blog post here



New

Sensors


WMI Battery

The new WMI Battery BETA sensor monitors status and available capacity of batteries that are connected to Windows devices. Additional channels of this new sensor type show voltage, time estimations until the battery is full or empty depending on the status charging or discharging, and an overall battery health value.

The sensor makes it possible for you to see the level of batteries in your IT infrastructure at a glance. PRTG alerts you as soon as a battery threshold is breached. You can even generate reports to get to know how much time laptops spend charging, for example.

Please note that the sensor is in beta status and only works if the required WMI battery classes are available on the monitored device. We welcome any feedback about the sensor and what you are trying to monitor. Please send your feedback to [email protected], thank you!

Improved

WebGUI


Device Icons

We added new device icons for several vendors. PRTG will automatically add suitable icons to devices detected via auto-discovery if possible. Of course, you can also manually select any device icon in the device settings, section Additional Device Information. The new set includes icons for the following vendors.
  • Juniper
  • Barracuda
  • Fortinet
  • PaloAlto
  • Kentix
  • Watchguard
  • Oracle
  • Westermo
  • Sophos
  • MikroTik
  • Qnap
  • Cybernetics
  • Brocade
  • Axis Cameras
  • Nimble Storage
  • Checkpoint (Firewalls)
  • Ruckus
  • Kemp
  • Aruba
  • Sonoff
  • Adtran

Improved

Sensors


SNMP Dell PowerEdge Physical Disk

Newly added SNMP Dell PowerEdge Physical Disk sensors now include the enclosure ID in the sensor name if available. For example, a sensor name can be Physical Disk 1:0:0:16, where the first of four numbers is the enclosure ID (here: 1). If there is no enclosure ID available, there will be three numbers in the sensor name, for example, Physical Disk 0:0:16. This improvement will help you to easier find the disk you are looking for in PRTG.

Fixed

Security


PRTG Core Server

We fixed potential reflected XSS vulnerabilities with medium severity on the PRTG core server. The potential vulnerabilities affected tag filters, object IDs, and the contact support/feedback page. Please note that the fixed vulnerabilities required a logged in PRTG user account to be exploited.

Sensors

We fixed a potential Denial of Service (DoS) vulnerability of the HTTP Full Web Page sensor. Please note that the fixed vulnerability required a logged in PRTG user account with elevated rights to be exploited. (CVE-2019-11074)

Fixed

Sensors


Event Log (Windows API)

You can filter for more than two event IDs with the Event Log (Windows API) sensor again. In the previous version, the input validation of the event ID field in the sensor settings did not properly work when you entered a comma-separated list of more than 2 IDs.

Exchange (PowerShell) sensors

Exchange (PowerShell) sensors now correctly close the runspace. In previous versions, Exchange (PowerShell) sensors sometimes showed a down status with the error message Fail to create a runspace because you have exceeded the maximum number of connections allowed. The fix applies to all Exchange (PowerShell) sensor types, Exchange Backup (PowerShell), Exchange Database (PowerShell), Exchange Database DAG (PowerShell), Exchange Mail Queue (PowerShell), Exchange Mailbox (PowerShell), Exchange Public Folder (PowerShell).

EXE/Script sensors

EXE/Script and EXE/Script Advanced sensors again support the special characters round brackets "()", dot ".", and comma "," in the Parameters field. This allows you to pass arrays from the sensor to the script.

Sensor Factory

We fixed an issue where, in rare cases, modifying the spike filter in combination with Sensor Factory sensors caused issues with the PRTG core server, resulting in gray sensors, for example.

SNMP Cisco System Health

  • We improved the stability of SNMP Cisco System Health sensors. The sensor can handle packet loss and delays better now due to request retries that properly work again. This will prevent the sensor from occasionally showing down states with error message Queries for the following channel IDs returned no data: %s (code: PE269) in many cases.
  • SNMP Cisco System Health sensors get correct names and units again after sensor creation. In previous versions, all channels except for the first one were only named by the index of the OID in certain cases.

SNMP HPE BladeSystem sensors

Channels of SNMP HPE BladeSystem Blade and SNMP HPE BladeSystem Enclosure System Health sensors will not be saved into custom device templates anymore. We changed it this way because dynamic sensor channels often lead to empty channels when they are created by custom device templates.

SNMP Poseidon Environment

You can add SNMP Poseidon Environment sensors again. The field validation in the settings when adding the sensor did not correctly work and prevented you from creating the sensor.

SNMP Traffic

  • Adding SNMP Traffic sensors now also works when you use the ifName OID [1.3.6.1.2.1.31.1.1.1.1] in the Port Name Template of the SNMP Compatibility Options. In previous versions, you were not able to add SNMP Traffic sensors in this case and got an access violation.
  • If you monitor interfaces with a lot of traffic, for example, 10 GB interfaces, and choose the Data option Display in percent of maximum in the settings of an SNMP Traffic sensor channel, PRTG will now automatically add an appropriate value to the Maximum (kbit/s) field. In previous versions, you had to manually configure a maximum value on which the percentage calculation is based in this case because the setting did not appropriately handle Int64 values.

SQL v2 sensors

We fixed an issue with SQL v2 sensors where the impersonation with Windows or database credentials prevented the sensor to read the file with the SQL query if the impersonated user had no access to the query files. The error message in this case was Parameter -query is missing. The fix applies to the sensor types ADO SQL v2, Microsoft SQL v2, MySQL v2, Oracle SQL v2, Oracle Tablespace, PostgreSQL.

SSL Certificate

The SSL Certificate sensor properly compares wildcard CN/SAN (Common Name/Subject Alternative Names) and SNI (Server Name Identification) again. In previous versions, the sensor showed a down status with the message CN/SAN do not match in this case.

SSL Security Check

If you create a device template that includes SSL Security Check sensors, running an auto-discovery with the template will now actually create SSL Security Check sensors. In previous versions, the auto-discovery erroneously added Port sensors in this case.

Windows Updates Status (PowerShell)

The Windows Updates Status (PowerShell) sensor will create more than one channel again if it can retrieve according data. The change will especially improve the sensor if the target device runs on Windows 10, Windows Server 2016, or later.

SNMP sensors and System Information

We implemented a minor stability improvement for the SNMP engine of PRTG. SNMP sensors as well as System Information tables retrieving data via SNMP can handle NUL in response strings again. For example, System Information tables showed the message Error: SNMPERR_GENERR (SNMP error #-1) with a timeout while waiting in WorkEnter in previous versions when receiving NUL strings.

Optional Sensor Channels

Sensors again only create optional channels if the channels are intended to be created. In the previous PRTG version 19.3.51, sensor types like, for example, SNMP Traffic and Ping erroneously created additional channels even if you did not select the according options in the Add Sensor dialog.

Spike Filter

Spike filters that you can optionally set apply to the tabs 30 days (Graph 2) and 365 days (Graph 3) again, as well as to historic data reports. In the previous PRTG version, the filter only worked for live data and the 2 days graph and table.

Fixed

Notifications


Notification Delivery

We removed the Test SMTP Settings button in the Notification Delivery settings on PRTG instances that are hosted by Paessler. As PRTG hosted by Paessler customer, you use the email infrastructure of Paessler so that testing the SMTP delivery settings is not necessary for you.

Notification Templates

PRTG user accounts with read/write rights and write or full access rights to a notification template can now change the user group as the recipient of an email, push, or SMS notification.

Logged in read/write users can see and select all user groups they are member of, as well the currently selected user group in the Send to User Group field of a notification template. In the Send to User field, read/write users can see and select all user accounts from all user groups they are a member of, as well as the currently selected user account.

SMS Notifications

  • Sending SMS notifications via custom SMS providers works again with both number conventions, plus (+) or 00 followed by country code and number. In previous versions, the plus sign was not correctly encoded so SMS messages could not be delivered.
  • We made SMS delivery via custom URL more robust. Due to a missing semicolon (;) behind content-type in the HTTP header, SMS delivery failed in certain cases with a bad request error.

Fixed

Reports


PDF Layout

We fixed an issue with PDF reports that erratically caused big gray boxes in generated reports.

PDF Stability

We implemented stability improvements for PDF reports with many sensors, especially regarding timeouts with the error message Error creating PDF report: [timestamp] navigate error: timed out waiting for response from chrome.

Fixed

Libraries


Node Types

Libraries again only show a subtree if you select Show a subtree of the device tree in the library as Node Type for a library node. In previous versions, library nodes additionally showed an unordered list of sensors included in the subtree.

Usability

The buttons to collapse and expand library nodes are now also available in the smallest view (S).

Fixed

Server


Data

We fixed an issue where values of primary sensor channels with negative channel ID were not displayed in some data tables, for example, the Traffic Total channel of SNMP Traffic sensors (channel ID -1). The value of this channel was missing in headers of historic data reports and as Last Value in Cluster Node tables, for example, when set as primary channel in the last PRTG version.

Logging

  • We fixed an issue with log files that became very large in rare cases and filled up the disk on the PRTG server. Log files now cannot grow bigger than 64 MB. PRTG will create a second file if this size is reached with a maximum of two copies of the same log file.
  • The Sensor Factory sensor writes less log messages than in the previous PRTG preview version and behaves as before again. Two lines of INFO logs for each sensor scan was a bit too much and unnecessarily filled up the PRTG core server log depending on your Sensor Factory sensor usage scenario.

Memory

We fixed an issue where in certain cases the PRTG server showed a too high memory consumption on large installations with, for example, several thousand sensors. The PRTG server will also use less memory than before when cloning hundreds of objects in the device tree at the same time.

PRTG Core Server

We removed an unnecessary readlock on the PRTG server that could lead to a deadlock with an unintended PRTG server restart in rare cases. Another readlock we fixed was caused by calculations of the Sensor Factory sensor and could prevent the PRTG server to restart.

PRTG GUI Starter

Opening the PRTG web interface with the PRTG GUI Starter now also works if you have set the connection security of your web server to High security (TLS 1.1, TLS 1.2). The PRTG GUI Starter is only used if you open PRTG via the shortcut PRTG Network Monitor that is created by default on your server during the PRTG installation.

Fixed

WebGUI


Dependencies

It is not possible anymore to configure a sensor to be its own dependency. Having a sensor as its own dependency resulted in a situation where a sensor endlessly paused itself when it switched to a down status without the possibility to resume the sensor.

Gauges

The gauge of a sensor's primary channel now always shows the unit for the minimum value. In previous version, the unit for the minimum value was missing if the minimum was 0 and the channel had a custom unit.

Multi-Edit

You can now acknowledge one or more down states on the Alarms tab of probes using the multi-edit menu, as well as open the settings of one or more probes.

Tables

We fixed some layout issues of meta-scan tables in sensor settings so that especially large tables are displayed in a better way.

Firefox

Opening the context menu in the PRTG web interface via right-click now even works if you use Firefox on macOS.

Internet Explorer 11

We fixed some more layout issues that occurred when accessing the PRTG web interface with Internet Explorer 11. For example, the Save button was cut off on some pages, the Hide and Show buttons for master dependencies in the dependencies graph were missing, and tickets sometimes occupied more space than given to them.

Changed

Server


Probes

Connecting remote probes now automatically downgrade to the correct version if the PRTG core server runs an older version than the probe.

Tags

It is not possible anymore to add the same tag to one object in PRTG more than once.

User Accounts

It is not possible anymore to create user accounts with a login name that includes the special characters " / \ [ ] : ; | = , + * ? > <

Note: User accounts that already existed before the update to PRTG 19.3.51 and have a login name that includes one of the outlined special characters will still be able to login after the installation of version 19.3.51. However, affected user accounts will not be able to change and save their account settings without changing the login name.

Improved

Various


All Parts of PRTG

Various other fixes and improvements to all parts of PRTG, updated user manual, updated German and Japanese language files

Note

Sensors


SNMP Fujitsu System Health

The upcoming PRTG version 19.4.53 will include a new, significantly improved SNMP Fujitsu System Health sensor. We already inform you now about the change because any previously deployed SNMP Fujitsu System Health sensors will immediately stop working upon updating to PRTG 19.4.53 or later and need to be added anew.

Note

Outdated Windows Versions


Outdated Windows Versions

It is not possible anymore to install PRTG on the outdated operating system Windows XP. This is a side-effect of changing the PRTG license check to a 64-bit binary. Please make sure you install PRTG on an officially supported operating system.

Note

Known Issues


Summarized Notifications

In the current version, PRTG does not send summarized notifications. You will receive the first down notification in any case but not the following summarization. We recommend that you choose the option Always notify ASAP, never summarize until we provide a fixed version if you strongly rely on potentially summarized notifications and do not want to miss any information.

Status: resolved with PRTG 19.4.52.3515

calendar

September 10th 2019 – Version 19.3.51.2830


Improved

Sensors


Active Directory Replication Errors

The Active Directory Replication Errors sensor now supports different Active Directory naming contexts. When you add the sensor, you can now choose between Configuration (default), Schema, DomainDnsZones, Domain, and ForestDnsZones as Naming Context to check your Windows Domain Controller for replication errors. In previous versions, the sensor always used Configuration as naming context.

Improved

Notifications


Notification Delivery

PRTG will now provide clearer communication in logs and tickets when an SMS notification fails due to a missing definition for an SMS provider in the Notification Delivery settings.

Notification Triggers

You can now directly create a new Notification Template while editing or defining a Notification Trigger without leaving the notification trigger tab. Click the plus symbol (+) in the dropdown list of a trigger to create a new notification template for the notification trigger.

Improved

Server


Active Directory

We improved the login process for Active Directory (AD) users by explicitly requesting read-only access.

Device Templates

If you create a new device template, you now only need to define a name for the template. You do not have to provide a file name anymore, PRTG will automatically create the corresponding template file with the extension .odt.

PRTG Core Server

Performance and memory footprint improvements for the PRTG core server, as well as several other improvements and fixes

Reporter

We added enhanced logging to the new reporter engine to be able to better help you in case of issues when generating reports.

Improved

Security


Maps

We fixed a potential XSS vulnerability in the context of maps. Thanks to Dmitry Galecha from Positive Technologies for reporting the issue.

Notifications

Passwords of Execute Program notifications, webhooks for Slack and Microsoft Teams notifications, as well as the AWS Secret Access Key of Amazon SNS notifications are now masked on the History tab of according notification templates in the PRTG web interface. Notification templates are only accessible for PRTG administrator users and read/write users with access rights for a particular notification template.

We found the issue in internal tests, it was not public before. If your PRTG installation is affected, you will receive a Todo ticket in PRTG. Please follow the instructions there.

Sensors

Passwords of the following sensor types are now also masked in log files when you enable the debug option: FTP Server File Count, HTTP XML/REST Value, SIP Options Ping, Citrix XenServer Host, Citrix XenServer Virtual Machine, IPMI System Health

Improved

Language Files


Language Files

Major update for all language files with around 585 improved strings per language. We especially focused on consistency of translations throughout PRTG.

Fixed

Sensors


Event Log (Windows API)

You can filter for two event IDs with the Event Log (Windows API) sensor again. In previous versions, the input validation of the event ID field in the sensor settings did not properly work when you entered a comma-separated list of IDs.

Note: With this version, it is not possible to filter for more than two event IDs. We plan to fully support filtering for multiple IDs again for the next PRTG version 19.3.52.

EXE-based Sensors

Sensors that require .NET version 4.7.2 now actually show the required version number 4.7.2 in the error message if the .NET framework version 4.7.2 is not available on the probe system. The full error message is This sensor requires the .NET Framework version 4.7.2 (code: PE104)

For more details, please see this Knowledge Base article.

Flow Sensors

It is possible again to clone flow sensors and devices on which flow sensors are running (for example, NetFlow sensors). In previous PRTG versions, you received Error (Not Found) when cloning flow sensors.

Note: To receive data with a flow sensor clone, please open the Settings tab of the sensor and click Save.

SNMP Traffic

  • The SNMP Traffic shows an according sensor message again when the Traffic Total channel breaches a defined limit. The fix also works for sum channels with ID -1 of other traffic sensors.
  • If you multi-edit two or more SNMP Traffic sensors, the connection-dependent buttons to select or deselect interfaces will not be available anymore. The buttons do not make sense for running SNMP Traffic sensors and had no functionality.

VMware Datastore (SOAP)

The VMware Datastore (SOAP) sensor now also properly works if the name of the monitored datastore starts or ends with host. In previous version, the sensor showed a down status with the error message The object '[name]' has already been deleted or has not been completely created in such cases.

Fixed

Probes


Memory Leak

We fixed a small memory leak on the PRTG probe system. The memory leak was caused by SNMP sensors that use SNMP bulk walks with more than 20 channels.

Probe Connections

We improved the stability of remote probe connections to the PRTG server. In some scenarios, customers encountered frequent disconnects of remote probes with the previous PRTG version 19.2.50.

Note: In certain cases, there may still occur issues with probe connections. We are working on further stability improvements for upcoming releases.

Probe GID

PRTG now always blocks connection attempts of deleted or rejected remote probes if there is an according entry in the Deny GID field of the Probe Connection Settings. The entry was not correctly saved in previous versions when using the French language file, Other language versions were not affected

Fixed

Server


Cluster

Sending support bundles from failover nodes works again.

Dependencies

We fixed an issue with dependencies where in certain cases devices and sensors did not resume automatically from paused by dependency. This happened, for example, after changing the dependency type from "Master object for parent" to "Use parent".

Device Tools

Opening the Service URL of a device via Device Tools now even works if the service URL contains an ampersand (&).

Geo Maps

Locations that you newly define for devices and groups in PRTG show up at the corresponding location in geo maps again.

PRTG Core Server

We fixed an issue with the PRTG core server that was not able to start and remained stuck in Loading Graph Cache if the configuration file contained an invalid speed trigger value. This happened in a few cases by error after cloning sensors with defined with speed triggers.

Raw Data Buffer

We fixed an issue that resulted in a full raw data buffer (see the according channel of the Core Health sensor) in certain scenarios with the previous PRTG version 19.2.50. This could happen, for example, when having many remote probes connected. The issue could also cause a loss of monitoring data with many sensors in unknown status.

User Accounts

It is possible again to change the settings of a user account at any time. Previous PRTG versions erroneously showed the error message A user with this login name already exists. Login names have to be unique. in certain cases when changing user settings. This especially happened for user accounts that you integrated via Active Directory.

Fixed

WebGUI


Access Rights

Primary groups of read/write user accounts in PRTG again automatically get write access to libraries, maps. reports, notification templates, and schedules that they create. This way, the new object remains visible after a page fresh for the user who created it.

Breadcrumbs

We implemented some minor improvements for the consistency of breadcrumbs and their translations.

Contact Support

PRTG user accounts with read/write rights can now also open the contact support form via Setup | Contact Support in the main menu bar.

Dark Theme

Historic data graphs keep their dark theme appearance again when you use the scroll and zoom buttons.

Homepage URL

Changing the PRTG Homepage URL in your account settings or via Make This My Homepage in the main menu bar on a PRTG hosted by Paessler instance now actually takes effect.

Hover Popups

  • PRTG will open the correct tab again when you click a graph in a hover popup.
  • We fixed the layout of graphs in hover popups for Internet Explorer 11.

Reports

  • PRTG can now generate reports and screenshots for the support bundle even if port 9222 is blocked on the PRTG core server. This did not work in the previous PRTG version 19.2.50 after the initial change to Chromium as reporter engine.
  • We fixed the validation of manually defined date ranges in report settings that showed some issues when using Google Chrome and the date format DD.MM.YYYY (24h or AM/PM) in PRTG 19.2.50. The date validation in general works more consistently now.

Search

Text that you are searching for in PRTG is correctly displayed again even if your search contains special characters or whitespaces. Search results were not affected by the issue.

Tags

Tags can now contain certain special characters like ampersand (&) and percentage (%) without causing issues with the PRTG web interface when you filter for such a tag.

Welcome Page

The ticket count on the PRTG welcome page again shows the correct number of open tickets that are assigned to you.

Fixed

Various


All Parts of PRTG

Various other fixes and improvements to all parts of PRTG, updated user manual

Changed

Sensors


Loopback Adapter

PRTG will not install a loopback adapter as part of the Npcap library for Packet Sniffer sensors anymore. When enabled, the adapter could lead to unwanted side-effects on other services, for example, DHCP servers.

Changed

Tree Version


Tree Version Update

The configuration file of this version is not downwards compatible with previous PRTG versions.

Note

Known Issues


Enterprise Console

The Enterprise Console will show two error messages when you close it: MM Operation after uninstall. and Runtime error 204

The messages do not have negative impact. You can ignore them and just close the message windows.

Status: Will not be fixed. Please note that we will stop officially supporting the Enterprise Console with PRTG 19.4.53. Please use PRTG Desktop as successor of the Enterprise Console.

Optional Sensor Channels

Some sensor types create optional channels that were not intended to be created. For example, SNMP Traffic sensors create all channels from settings section Additional Channels even if they were not selected in the Add Sensor dialog. The Ping sensor creates channels for minimum and maximum ping time, as well as the packet loss channel, even if you select the option Send one single Ping when adding the sensor.

The issue does not have functional impact as long as you do not set one of the erroneously created channels as primary channel. In this case, the sensor may switch to the unknown status. Please note that channels cannot be deleted anymore once they are created, so we recommend that you wait for the next PRTG version if you plan to add sensors of these types without optional channels.

Status: resolved with PRTG 19.3.52.3502

Reports

Big reports with thousands of sensors occasionally time out and are not successfully created. The message in this case is Error creating PDF report: [timestamp] navigate error: timed out waiting for response from chrome

Status: resolved with PRTG 19.3.52.3502

Spike Filter

In the current version, the spike filter only applies to graphs and tables for live data and 2 days (Graph 1 in graph settings). It is not possible with PRTG 19.3.51 to remove spikes from graphs and tables for 30 days (Graph 2), 365 days (Graph 3), and historic data reports.

Please note that this is a display issue, monitoring data is not affected. As soon as you update to a fixed version, all historic data will be correctly displayed again, respecting optionally set spike filters.

Status: resolved with PRTG 19.3.52.3502

Summarized Notifications

In the current version, PRTG does not send summarized notifications. You will receive the first down notification in any case but not the following summarization. We recommend that you choose the option Always notify ASAP, never summarize until we provide a fixed version if you strongly rely on potentially summarized notifications and do not want to miss any information.

Status: resolved with PRTG 19.4.52.3515

Note

PRTG 19.3.51.2725


PRTG 19.3.51.2725

Please note that we took PRTG version 19.3.51.2725 (released on July 31) offline on August 5 as a precaution because some customers reported serious issues after the update to this version. Affected customers reported 100% CPU load and many sensors in gray Unknown status due to a full graph cache recalculation that PRTG must do from time to time.

We found the reason for the misbehavior and were able to resolve the issue. PRTG 19.3.51.2830 includes a fix for this, as well as three other fixes compared to 19.3.51.2725. If you are running the withdrawn version 19.3.51.2725, please update as soon as possible.

Active Directory Replication Errors Sensor

The Active Directory Replication Errors sensor now uses the naming context Configuration as default. This is also the naming context that the sensor used in previous version. With the support of different naming contexts introduced in PRTG 19.3.51.2725, the default was Domain, which, in certain cases, resulted in sensors of this type that did not find the replication neighbor anymore after the update.

Auto-Discovery Groups

Adding an auto-discovery group or editing the settings works properly again. In PRTG 19.3.51.2725, several IP selection methods caused an access violation when saving the settings.

Updating

We fixed an issue where, in rare cases, updating from older PRTG versions like, for example, 17.3.33, failed because of the tree version update in combination with certain history entries in the PRTG configuration file.