PRTG Network Monitor

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! 

Download PRTG · Manual: "Software Auto-Update" · Previous Versions and other Release Channels

calendar

December 1st 2021 – Version 21.4.73.1656


New

Notifications


OPC UA

You can now use OPC UA notifications to forward PRTG alerts to your northbound systems like SCADA, DCS, or any other system that has an OPC UA server. By creating an OPC UA notification template, you can build meaningful error messages that PRTG sends to your OPC UA server. This supports you in seeing and reacting on issues in your network infrastructure as fast as possible.

Improved

Sensors


Business Process

Requesting data of the Business Process sensor via the API now returns values in value_raw fields in a better consumable way.

DNS v2

You can now define multiple filter values for the DNS v2 sensor to filter for more than one IP address, for example.

Modbus sensors

The sensor types Modbus RTU Custom and Modbus TCP Custom now provide a timeout setting. If the reply from the target device takes longer than the defined Receive Timeout (msec), the request will be aborted and the sensor stops trying to connect.

Changed

Sensors


Lookups

You can now easier identify sensors with a missing or broken lookup file. Sensors that have an issue with their lookups will change their status to warning with the message At least one channel uses a lookup that is not available or could not be loaded. (PE272) as of this version to indicate that the sensor cannot properly monitor. In previous versions, you only received a ToDo ticket in such cases but affected sensors kept their status.

Microsoft 365 Service Status sensors

The sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced support the new Microsoft 365 Service Health and Communications Graph API as of this version. This change is necessary to seamlessly continue monitoring your Microsoft 365 services because Microsoft soon will shut down the current API version that the sensors used until now.

Important: Both sensors now require the API permission ServiceHealth.Read.All to be able to retrieve data from Microsoft Graph and continue monitoring. For details, please see the Knowledge Base article How do I obtain credentials and set permissions for the Microsoft 365 sensors?

Please also note that the Microsoft 365 Service Status Advanced sensor cannot monitor subservices anymore and will show the message Channel is deprecated for affected channels. We will remove the channels in an upcoming PRTG version.

Scanning interval

We changed the default scanning interval for several newer sensor types that we introduced over the last couple of PRTG versions.

Fixed

Sensors


Microsoft Azure Virtual Machine

The Microsoft Azure Virtual Machine sensor now shows a down status with an appropriate error message if the target device is not reachable anymore, for example, due to changed credentials. In previous versions, the sensor incorrectly showed a misleading up status with 0 values in such cases. We also improved the general stability of the sensor.

Fixed

WebGUI


Channel Unit Configuration

The dropdown menu for the unit of Bytes (Bandwidth) in the Channel Unit Configuration settings is properly shown again. In Google Chrome and Edge, it was difficult to select the desired unit due to display issues in previous versions.

Lab

Sensors


AWS v2 sensors

We implemented various improvements for the experimental AWS v2 sensors.
  • The metric channel of the AWS Alarms v2 (BETA) sensor now shows a proper unit.
  • The AWS EC2 v2 (BETA) sensor now only creates the channels Disk Read, Disk Read Ops, Disk Write, and Disk Write Ops if they receive values.
    Note: Running sensors of this type will show a down status after updating to PRTG 21.4.73 due to this change. Please add affected sensors anew.
  • We added a lower error limit to the CPU Credit Balance channel of the AWS EC v2 (BETA) and AWS RDS v2 (BETA) sensors. Channel values below 1 will now trigger a down status because they indicate low performance.
  • We generally hardened the approach how AWS v2 sensors retrieve data to avoid gaps in the sensor data.

AWS EBS v2

You can try out the experimental AWS EBS v2 (BETA) sensor as of this version and monitor the status and performance of an AWS EBS volume.

FortiGate System Statistics

You can try out the experimental FortiGate System Statistics (BETA) sensor with this version. The sensor monitors the system health of a Fortinet FortiGate firewall and shows CPU and memory usage, as well as uptime, session statistics, and conserve mode activity.

Network Share

You can try out the experimental Network Share (BETA) sensor with this version. The sensor monitors the number of files and folders on a network share via SMB or CIFS, as well as its size and the age of oldest and newest files.

Redfish Power Supply

You can try out the experimental Redfish Power Supply (BETA) sensor as of this version. The sensor monitors the status of the power supply of your servers, the power efficiency, and various other parameters.

Lab

New UI


Initial alpha release

We are working on a complete redesign of the PRTG web interface. The redesign is based on extensive user research and the feedback that we have received over the years. The user interface will be fully responsive and will follow the Web Content Accessibility Guidelines (WCAG).

Although the new UI is still missing many features, we decided to release the alpha version to give you the opportunity to try out the new UI, and to gather feedback during the early development process. Read all about the new UI here: I want to use the new UI and new API. What do I need to know?

Lab

New API


Initial alpha release

Our new RESTful API will enable you to easily automate your monitoring and to integrate it with other tools. Our goal is to build a comprehensively documented RESTful API that is consistent across all endpoints.

Although the new API is still missing many features, we decided to release the alpha version to give you the opportunity to try out the new API, and to gather feedback during the early development process. Read all about the new API here: I want to use the new UI and new API. What do I need to know?

Lab

Multi-platform probe


Initial alpha release

The new multi-platform probe will enable you to deploy PRTG probes on various platforms like Windows, Linux, and Docker. We are happy to now share the initial alpha version with you and gather your feedback during the early development process. You can already run a limited set of sensors on it but many features will follow later. Read all about the new multi-platform probe here: What is the Multi-Platform Probe and how can I use it?

Improved

Various


All parts of PRTG

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

Note

Sensors


Event Log (Windows API)

The Event Log (Windows API) sensor will no longer work due to security changes from Microsoft and will be discontinued. For details, please see Event Tracing and Windows NTLM Elevation of Privilege Vulnerability.

We recommend that you pause existing sensors to store historic data. To continue monitoring, use the WMI Event Log sensor.

calendar

October 26th 2021 – Version 21.4.72.1649


Improved

Security


Server

This version includes an important security update for the PRTG core server. An authenticated user with write access could leverage specifically crafted API calls to execute an arbitrary file on the PRTG core server system under the identity of the PRTG core server service. (CVE-2021-42253)

Sensors

We improved the parameter handling of several database sensors to prevent external tools from logging them. The change improves the security of the sensor types ADO SQL v2, Microsoft SQL v2, MySQL v2, PostgreSQL, Oracle SQL v2, and Oracle Tablespace.

Fixed

Sensors


Microsoft Azure SQL Database

We hardened the detection mechanism of the database type when adding a new instance of the Microsoft Azure SQL Database sensor. The sensor showed a down status upon creation in previous versions if the database type had changed from single database to elastic pool or vice-versa.

Microsoft Azure SQL Database

You can now define a scanning interval for a running sensor that is lower than the initial scanning interval that was set when creating this sensor. This was not possible for several newer sensor types before this PRTG version.

Fixed

Server


API

Switching inheritance off and on with the setobjectproperty.htm API call works again.

History

Cloning a device now adds an entry to the History tab of the parent group on which the device clone is newly created.

Probe connections

Probes now automatically retry to connect to the PRTG server when their initial login to the server failed. This prevents certain cases where the sensors on the probe remained in the unknown status after starting the PRTG server.

Stability

We implemented several minor stability improvements for the PRTG core server.

Startup

We fixed the case where missing entries in custom language files prevented the PRTG core server from starting.

Fixed

WebGUI


User accounts

You can mark the passhash in your user account settings in Firefox again to easier copy and paste it.

Lab

Sensors


AWS Alarm v2

You can try out the experimental AWS Alarm v2 (BETA) sensor as of this version and monitor your favorite metric and composite AWS alarms with this sensor type.

AWS RDS v2

We implemented several minor improvements for the experimental AWS RDS v2 (BETA) sensor.

HPE 3PAR Drive Enclosure

We fixed an issue with the experimental HPE 3PAR Drive Enclosure (BETA) sensor that could not handle certain data that HPE 3PAR devices may return. The sensor showed a down status with a parsing error in such cases.

HPE 3PAR Virtual Volume

We added five new channels to the experimental HPE 3PAR Virtual Volume (BETA) sensor that show the full total of used and reserved space. We also renamed the channels User Space Total and Snapshot Space Total to User Space Reserved and Snapshot Space Reserved to better indicate what they monitor. The new channel names only apply to newly added instances of this sensor type.

Improved

Various


All parts of PRTG

Various other minor fixes and improvements, updated user manual, updated German language file

calendar

September 21st 2021 – Version 21.3.71.1416


New

Sensors


Beckhoff IPC System Health

The new Beckhoff IPC System Health sensor monitors the system health of a Beckhoff Industrial PC (IPC) via OPC UA. It shows available memory, CPU load, the temperature of CPU and mainboard, as well as the status of the RAID controller.

We initially released this sensor type as experimental sensor in PRTG 21.2.67.

Modbus RTU Custom

The new Modbus RTU Custom sensor connects to a Modbus RTU server and monitors up to five values returned by the device. With this sensor type, you can monitor, for example, temperature, humidity, and more inside a rack in your datacenter so that you can ensure your equipment operates within the defined ranges.

We released this sensor type as experimental sensor in PRTG 20.4.64 and implemented your feedback over the last couple of PRTG versions.

Improved

Sensors


MQTT Subscribe Custom

You can now create sensor channels from the value type Delta (counter) to calculate the difference between the last and the current value with the MQTT Subscribe Custom sensor. With this option you can monitor the power consumption of your heat pump, for example, to know if it is operating efficiently.

Improved

Server


API

The API call api/health.json now additionally returns the number of State objects, which corresponds to the number of currently logged in PRTG user accounts. We also added api/health.json to the public API documentation in the PRTG user manual.

Reports

PRTG now generates your PDF and HTML reports much faster compared to previous versions. You will especially notice this performance improvement when running reports with a lot of sensors and historic data on large installations.

Fixed

Sensors


Common SaaS

The Twitter channel of the Common SaaS sensor now supports response code 426. In previous versions, the sensor occasionally showed a warning status with the message Twitter API not available - HTTP/1.1 426 Upgrade Required if Twitter returned this code.

DNS v2

You can add the DNS v2 sensor via auto-discovery again.

EXE/Script sensors

We updated the sample PowerShell scripts that we deliver for EXE/Script sensors to work with the enabled PowerShell Security Enhancement setting. The scripts now use write-output instead of write-host. We also encourage you again to accordingly adapt your own scripts to write-output to successfully run your custom PowerShell sensors with enabled security enhancement.

Flow and Packet Sniffer sensors

PRTG now properly handles whitespaces in group names and captions when you change the default groups and channels for Flow and Packet Sniffer sensors (via CustomFlowRules.osr, for example). In previous version, whitespaces led to a disabled Save button on the Settings tab of Flow and Packet Sniffer sensors.

HPE 3PAR sensors

We fixed an issue with HPE 3PAR sensors that could cause the probe to stop monitoring if you had a certain number of running HPE 3PAR sensors on this probe. All sensors on the affected probe showed the unknown status in such cases. We also improved the stability of HPE 3PAR sensors in case of reconnects where the sensors previously were not able to recover from the down status in some cases.

The issues affected the HPE 3PAR Common Provisioning Group sensor, as well as the experimental sensor types HPE 3PAR Drive Enclosure (BETA) and HPE 3PAR Virtual Volume (BETA).

Modbus sensors

We fixed connection issues of Modbus TCP Custom and Modbus RTU Custom sensors that appeared in the previous PRTG stable version 21.3.70. Modbus sensors were not able to connect to the target server if the initial attempt failed and showed a permanent down status with the error message The sensor could not retrieve data from the server or similar.

NetApp LUN

The NetApp LUN sensor now shows 0% bytes free if the used size exceeds the allocated size, just like the NetApp in its own interface. In previous versions, the sensor showed a completely incorrect value in such cases.

VMware Virtual Machine (SOAP)

Newly created VMware Virtual Machine (SOAP) sensors now have the Alarm when VM is powered off setting enabled by default.

Sensor creation

The progress bar in the Working... dialog window that appears when you start adding certain sensor types now also properly visualizes the progress for various sensor types that we implemented over the last couple of PRTG versions.

Fixed

Security


User accounts

Paused PRTG user accounts cannot resume other paused user accounts via the API anymore.

Version number

PRTG no longer displays the current version number in the footer of the startup screen in the web interface. This improves security by not providing attackers potentially relevant information on a page that does not require a login.

Fixed

Server


Cluster

Sensors on failover nodes in status Down (Acknowledged) show timestamps and names of the acknowledging user accounts in the sensor message again.

User accounts

User accounts that are member of an Active Directory or single sign-on user group now open the defined homepage of their primary user group when they log in for the first time. In previous versions, they always started on the default welcome page.

Lab

Sensors


AWS ELB v2

We added several new sensor channels for various metrics of application and network load balancers to the AWS ELB v2 (BETA) sensor.

AWS RDS v2

You can try out the experimental AWS RDS v2 (BETA) sensor as of this version. The sensor monitors various metrics of your RDS instances and will be the successor of the existing Amazon CloudWatch RDS sensor.

Local Folder

  • We added the option to define whether the Local Folder (BETA) sensor monitors only the specified folder (default) or all subfolders as well. You can define this behavior with the Recurse Subfolders setting.
  • You can filter for specific files that you want to monitor. Enable the Filter by File Name setting, define if you want to include or exclude specific file names and file types, and so keep an eye on your most important files.
  • You can now filter files by age. With this option you can monitor, for example, the success of certain automatic processes that create or modify files.
  • We added a timeout setting, which is useful for larger filesystems to avoid a potential probe overload, and prevent defining UNC paths, which are not supported by the sensor.

Redfish Virtual Disk

You can try out the experimental Redfish Virtual Disk (BETA) sensor as of this version. The sensor monitors the virtual disks of your Redfish capable servers and shows capacity and status.

REST Custom v2

The REST Custom v2 (BETA) sensor now supports XML in addition to JSON and you can use XPath to define the sensor channels.

Improved

Various


Languages

We updated the German language file and implemented some minor improvements for French and Russian.

All parts of PRTG

Various other minor fixes and improvements, updated user manual

calendar

August 17th 2021 – Version 21.3.70.1629


New

Sensors


HPE 3PAR Common Provisioning Group

The new HPE 3PAR Common Provisioning Group sensor monitors the capacity of a common provisioning group (CPG) on an HPE 3PAR storage system. It shows the overall state of the CPG, as well as free, allocated, and used logical space, snapshot space, and user space.

We released this sensor type as experimental sensor in PRTG 21.1.65 and implemented your feedback over the last couple of PRTG versions.

Microsoft Azure SQL Database

The new Microsoft Azure SQL Database monitors metrics of an Azure SQL Database (single database or elastic pool) in a Microsoft Azure subscription. It can show, for example, CPU and disk usage, number of deadlocks, DTU and eDTU usage and limits, and sessions in percent.

We released this sensor type as experimental sensor in PRTG 20.4.64 and implemented your feedback over the last couple of PRTG versions.

Microsoft Azure Storage Account

The new Microsoft Azure Storage Account sensor monitors the storage account in a Microsoft Azure subscription and shows latency, traffic, and capacity metrics, as well as the number of request breakdowns.

We released this sensor type as experimental sensor in PRTG 21.1.65 and implemented your feedback over the last couple of PRTG versions.

Improved

Sensors


Microsoft 365 sensors

You can now create device templates that include the sensor types Microsoft 365 Service Status and Microsoft 365 Service Status Advanced. This enables you to add these sensors via auto-discovery.

Modbus TCP Custom

We implemented session sharing for the Modbus TCP Custom sensor and the experimental Modbus RTU Custom sensor. Session sharing reduces the load on the monitored system compared to previous PRTG versions where each sensor created its own connection to the Modbus gateway.

OPC UA Custom

The OPC UA Custom sensor now supports up to 10 channels so that you can monitor up to 10 values returned by specific OPC UA node IDs with one sensor of this type.

WMI Event Log

The WMI Event Log sensor now supports filtering by multiple event IDs.

Zoom Service Status

You can now create device templates that include the Zoom Service Status sensor. This enables you to add sensors of this type via auto-discovery.

Fixed

Sensors


MySQL (v1)

Still existing instances of the deprecated sensor type MySQL (v1) work again and continue monitoring upon updating to PRTG 21.3.70 or later. In PRTG versions 21.2.68 and 21.3.69, they showed a down status with the error message parameter -sslmode is missing. Please note that we strongly recommend that you replace all sensors of the deprecated type MySQL (v1) with the MySQL v2 sensor.

SNMP Custom Table

Adding SNMP Custom Table sensors with an identification column other than table_index or ifindex properly works again. In previous versions, the sensors showed a down status after creation with error code PE247 in such cases.

Fixed

Server


Active Directory

We fixed an issue with the login of Active Directory user accounts. If the display name or full name of a user in the Active Directory contained certain special characters like, for example, ampersand (&), a newly introduced security mechanism blocked the login in the last PRTG version 21.3.69. This also affected PRTG user accounts with two or more consecutive whitespaces in login or display name.

Cluster

Failover nodes in a PRTG cluster now keep the password of the PRTG System Administrator user account when you have changed it. In previous versions, the administrator password on failover nodes always reverted to default upon updating the PRTG server.

Important: The PRTG default login with password prtgadmin will not work on failover nodes anymore upon updating to PRTG 21.3.70 or later. Please use the PRTG Administration Tool on the failover node to generate a new password. See also the Knowledge Base article Change to requirements for login to the failover node.

Device templates

We fixed an issue with certain sensor types like the SNMP HPE ProLiant Memory Controller sensor that, if included, prevented a successful creation of device templates. The created template did not appear in the list of device templates in such cases.

Single sign-on

We fixed an issue with external callback URLs for the endpoint handling that included uppercase letters. In such cases, you could not login into PRTG via single sign-on and received the error message The URL you are using to connect to PRTG is not enabled for single sign-on.

Time zones

Status messages of down (acknowledged) and paused sensors now show the time zone of the user account instead of the server time. In the logs, the messages are displayed in server time.

Fixed

WebGUI


Home page URL

Home page URLs with URL parameters that you define for PRTG user groups work again. In previous versions, parameters were removed from the URL so that the you did not land on the defined home page when you logged in into the PRTG web interface.

Internet Explorer

Adding new notification triggers and displaying existing triggers in Internet Explorer 11 works again.

Lab

Sensors


AWS EC2 v2 and AWS ELB v2

We added comprehensible region names to the channels of the experimental AWS EC2 v2 and AWS ELB v2 sensors.

Local Folder

We introduce the experimental Local Folder (BETA) sensor with this version. The sensor monitors the number of files and folders in a local folder on the probe device, as well as its size and the age of oldest and newest files.

Redfish System Health

You can try out the experimental Redfish System Health (BETA) sensor as of this version. With this sensor, you can monitor the system health of servers in your datacenter using the Redfish protocol from your servers' management controllers like Lenovo XClarity, HPE iLO, or Dell iDrac.

Improved

Various


Languages

We updated and improved all language files.

All parts of PRTG

Various other minor fixes and improvements, updated user manual

calendar

July 6th 2021 – Version 21.3.69.1333


New

Sensors


Veeam Backup Job Status Advanced

The new Veeam Backup Job Status Advanced sensor monitors the status of a specific backup job that runs on the Veeam Backup Enterprise Manager. The sensor monitors the status of the backup job, the duration, the time since the last run, and if the backup job is scheduled.

We released this sensor type as experimental sensor in PRTG 21.1.65 and received valuable feedback that we implemented over the last couple of PRTG versions. In addition to the functionality that the sensor already had in the last PRTG version, we resolved two more issue for this release.
  • Adding a new Veeam Backup Job Status Advanced sensor works more reliably now. In certain scenarios, you could not add the sensor and received the error message An error occurred. The queried field is empty.
  • We added the new lookup value None so that the sensor can now handle the combination job status idle and job result none. Previously, the sensor showed a down status with the error message An error occurred: Bad optional access in such cases.

Improved

Sensors


Dell EMC Unity Enclosure Health v2

The Dell EMC Unity Enclosure Health v2 sensor now can also monitor Power Consumption in a dedicated channel.

Modbus TCP Custom

  • You can now select single bits of input and holding registers to monitor them with the Modbus TCP Custom sensor. This is useful for monitoring Modbus devices that report the on/off status of several inputs as one register, for example.
  • You can now create sensor channels from the value type Delta (counter) to calculate the difference between the last and the current value. With this option you can monitor the power consumption of your heat pump, for example, to know if it is operating efficiently.
We also implemented these features for the experimental Modbus RTU Custom (BETA) sensor.

MQTT Subscribe Custom

The MQTT Subscribe Custom sensor now supports up to 10 channels so that you can monitor up to 10 values from a subscribed MQTT topic with one sensor of this type.

SNMP sensors

PRTG can now perform more SNMP v3 requests at the same time, so that monitoring with SNMP v3 sensors is more stable compared to previous versions.

Improved

Security


Active Directory

PRTG now validates all fields that are imported from Active Directory when creating a new user account to close a potential XSS vulnerability. (CVE-2021-29643)

Fixed

Sensors


Microsoft Azure sensors

We improved the stability of the Microsoft Azure sensors. In previous versions, the sensors had connection issues in some cases, which resulted in wrong down and warning states.

DNS v2

The Records Resolved channel of the DNS v2 sensor correctly uses a lookup with the states yes and no again. Add the sensor anew to resolve the issue with the Records Resolved channel.

Microsoft 365 Service Status sensors

We hardened the Microsoft 365 Service Status sensor and the Microsoft 365 Service Status Advanced sensor against unknown service states that Microsoft 365 may return. In such cases, the sensors previously showed a down status with the message error.generic[invalid map key].

SNMP Printer

We improved the stability of the SNMP Printer sensor. In rare cases, the sensor showed a down status with the message No such instance (SNMP error # 223) after some time when monitoring certain types of printers.

Fixed

Server


API

API calls for tables with content=probenodes return all probes again.

Auto-Discovery

Devices now keep their settings even after running an auto-discovery on this device. Previously, the first auto-discovery on a device occasionally overwrote your manually configured settings like names, icons, or tags.

Graphs

The graph on the 2 days tabs of sensors shows the correct downtime again. In previous versions, the 2 days tab showed a wrong downtime in various cases, for example, always 0% even if there was a downtime reported and correctly shown in the data table. The percentage values on the y-axis of 2 day graphs are also back again.

Single sign-on

Logging in with single sign-on now also works if you use an Azure AD group name (sAMAccountName) with upper-case letters as SSO Group Access Claim. We also fixed the misbehavior that PRTG logged out SSO user accounts after some time.

Fixed

WebGUI


Maps

We fixed a display issue on maps that affected channel gauges on View Map tabs. Sometimes, the gauge values of previously opened sensor pages erroneously appeared in gauge map objects instead of the real values until the page was refreshed.

Lab

Sensors


AWS EC2 v2

You can try out the experimental AWS EC2 v2 (BETA) sensor as of this version. The sensor monitors the performance of an Amazon EC2 instance and will be the successor of the existing Amazon CloudWatch EC2 sensor.

Note: If you use the same IAM policy that you use for the Amazon CloudWatch EC2 sensor, you must update it. For more information, see the Knowledge Base: How do I set permissions for the Amazon Web Services (AWS) API key to use certain sensors in PRTG?

AWS ELB v2

You can try out the experimental AWS ELB v2 (BETA) sensor as of this version. The sensor monitors the performance of an AWS ELB load balancer and will be the successor of the existing Amazon CloudWatch ELB sensor.

HPE 3PAR sensors

We implemented session sharing for the HPE 3PAR sensors. Session sharing reduces the load on the monitored system compared to previous PRTG versions where the sensors logged in to the HPE 3PAR system with every scan.

REST Custom v2

We fixed the Custom Headers of the REST Custom v2 sensor. In the last PRTG version, sending custom HTTP headers did not work correctly.

SNMP Rittal CMC III Hardware Status

We introduce the experimental SNMP Rittal CMC III Hardware Status (BETA) sensor with this version. The sensor monitors the hardware status of a Rittal CMC III processing unit and shows the status of every attached external sensor.

Improved

Various


All parts of PRTG

Various other minor fixes and improvements, updated German language file, updated user manual

Changed

Sensors


DNS sensor

The DNS (v1) sensor is now deprecated as we previously announced. DNS (v1) sensors that you added in previous versions will continue to monitor after updating to PRTG 21.x.69, but you cannot add sensors of this type anew. Please use the new DNS v2 sensor instead.

Note

Sensors


SNMP sensors

In some cases, SNMP sensors show SNMP error 2011 after updating PRTG to version 21.3.69 with the message Could not create SNMP Session (-3000)-2011. The error may occur if the latest updates for the Visual C++ Redistributable Package are missing on the probe system.

For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/89831.

This third party content uses Performance cookies. Change your Cookie Settings or

load anyways

*This will leave your Cookie Settings unchanged.