Documentation forWeb Performance Monitor

WPM 2020.2.5 Release Notes

Release date: March 25, 2021

Updated April 8, 2021

These release notes describe new features, improvements, and fixed issues in SolarWinds Web Performance Monitor (WPM) 2020.2.5. They also provide details about upgrades and workarounds for known issues.

WPM 2020.2.5 is a service release. For more information, see the following documents:

Looking for release notes from earlier versions? See Previous Versions.

These release notes provide the following details:

New features and improvements in WPM

WPM 2020.2.5 includes security improvements related to Orion Platform 2020.2.5, as described in the Orion Platform 2020.2.5 Release Notes.


New customer installation

To install WPM, review system requirements and use the SolarWinds Orion Installer, which you can download from the SolarWinds Customer Portal. See the Orion Platform Products Installation and Upgrade Guide to learn how to prepare your environment.

After installing WPM on the Orion server, you can deploy Web Transaction Recorders and the WPM Player service to remote systems to get an accurate sampling of your websites and services from the viewpoint of your end users. See the WPM Getting Started Guide for details.

How to upgrade

To prepare for the upgrade:

  1. Read these Release Notes.
  2. Confirm that all servers comply with WPM 2020.2 System Requirements.
  3. (Optional) Back up any custom code, such as modified SolarWinds .css files or added .js files.

In addition, note the following details:

  • SolarWinds recommends using the latest version of WPM and the Orion Platform, including hotfixes and service releases. For more tips, see Secure Configuration for the Orion Platform.
  • If migrating the primary WPM application to a new server during an upgrade, update EngineIDs for SEUM agents.
  • If upgrading from WPM 2.2.2 or earlier, upgrade to WPM 2.2.3 first, and then upgrade to the latest version.
  • Transactions based on recordings created in WPM 2.2—2020.2 may behave differently if FIPS mode is enabled.
  • When upgrading WPM Players on remote systems, the following Windows settings are adjusted:
    • Net.Tcp Port Sharing Service: The Startup Type is set to Manual on the Orion server and any Additional Polling Engines (APEs). On remote systems, the Startup Type is set to Automatic.
    • SolarWinds WPM Playback Player service: A dependency with the Net.Tcp Port Sharing Service is added.

To upgrade your entire Orion deployment, including all Orion Platform products and any scalability engines:

  1. Run the SolarWinds Orion Installer.

    Alternatively, click Settings > My Orion Deployment to upgrade from within the Orion Web Console.

  2. Update Web Transaction Recorders and WPM Players on remote systems. See the WPM Getting Started Guide.
  3. If you migrate the primary WPM application to a new server during an upgrade, update EngineIDs for SEUM agents also.

Fixed issues

Case Number Description

00643143

The Web Transaction Recorder supports editing SSO credentials in recordings that include authorization URLs with customer ports. After upgrading WPM, "User account is locked or disabled" errors do not appear.

00602999, 00616227

When upgrading from WPM 2.2.3 or earlier, the Configuration Wizard finishes without "Database configuration failed" and "Services configuration failed" errors.

00689582, 00691910, 00703910

SolarWinds.SEUM.Common.dll, SolarWinds.SEUM.Agent.Common.dll, and SolarWinds.SEUM.Agent.dll were updated to resolve communication delays and "Unable to create worker process" messages in AgentService.logs on remote systems that host WPM Players. The default location for these files is C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\.

To learn about fixed issues in the Orion Platform, see the Orion Platform 2020.2.5 release notes.


Known issues

Return to top

Issue Notes
Transactions played back on the WPM Player have a smaller screen size than when created in the Deprecated WPM Recorder. Recordings created in WPM 2.2.3 and earlier don’t store original screen sizes. For a workaround, click here.
Transactions based on recordings created in the Deprecated WPM Recorder that involve certificates may cause a WPM Player to crash on Windows Server 2016 Standard, Windows Server 2019 Standard, or Windows 10 v. 1607 or later. Click here for a workaround that adds the monitored page as a trusted site.
The Deprecated WPM Recorder doesn't count duration time on web pages with automated redirects. If a recording navigates to a web page that includes a redirect to another web page, the time spent navigating to the first web page is not included in the overall duration time. Click here for a workaround.
Web Transaction Recorder may stop responding if invalid credentials are provided. If you enter invalid credentials for a recording to which multiple authentications were applied, the Web Transaction Recorder may switch to an unusable state that displays a "Digest" graphic.
If using Image Match with Basic Authentication, dynamic iFrame pages appear blank during action-by-action playback. In the Web Transaction Recorder, if you navigate to a dynamic iFrames page while using Image Match with Basic Authentication and click the Play action-by-action tool, the page that WPM tries to authenticate does not display any content.
Some WPM pages and widgets aren't compatible with Internet Explorer (IE) 11. Warning messages may appear when using IE 11 with features introduced in WPM 2020.2 or later. Use Chrome, Firefox, or Microsoft Edge for the optimum WPM experience in the Orion Web Console.
Invalid time calculated for steps with implicit navigation in the Web Transaction Recorder. Recordings that include implicit navigation (for example, navigate to a page and download images with delays of up to 5 seconds each), the time calculated for the implicit steps may not be accurate.
Page titles do not appear in the Recorded Steps pane of the Web Transaction Recorder when using links to navigate to different tabs on the same page. This occurs if WPM cannot access the window.opener property of the Windows UI, so the web page title is not captured in the recording. As a workaround, enter a URL to switch to a new tab on the same page, instead of clicking a link.
WPM Player service restarts and reconnects after agent communication exceptions If the WPM Player service is overloaded, fatal exceptions can cause the service to restart as it dispositions WPM worker processes. Click here for a workaround.
After exporting a recording with Image Match steps from the Deprecated WPM Recorder, error occurs when you try to save the file. To work around this issue, save the file before you export it.
Transaction monitors switch to Unknown, agents stop working, and WPM Players cannot be deployed or updated. Use the Orion Service Manager to restart services. Click here for details.
If you connect a Web Transaction Recorder to your Pingdom account, and the API token is later deleted, a list of recent recordings may not appear the next time you open the recorder. An error similar to the following may appear: Failed to execute get: Error: Request failed with status code 401.

As a workaround, remove both the Orion server and Pingdom configurations from the system hosting the recorder, and then connect the recorder to the Orion server and Pingdom accounts again.

After assigning a transaction to a new WPM Player hosted on a Windows Server 2019 machine, the WPM Browser.exe task hangs. As a workaround until this issue is resolved, move transactions to a host machine running a different supported OS.

End of life notices

See the End of Life Policy to learn more about life cycles for SolarWinds products.

EoL Announcements EoE Effective Dates EoL Effective Dates

August 25, 2020

End-of-Life (EoL) announcement – Customers on WPM 2.2.3 and earlier should begin transitioning to the latest version of WPM.

November 25, 2020

End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WPM 2.2.3 and earlier will no longer be actively supported by SolarWinds.

November 25, 2021

EoL – SolarWinds will no longer provide technical support for WPM 2.2.3 and earlier.


Legal notices

Return to top

© 2021 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.