Troubleshoot WPM

Use this section to resolve common issues and acquire almost details to collect if you lot demand to contact SolarWinds Support.

This topic includes the post-obit sections:

  • Determine if FIPS Mode is enabled
  • Troubleshoot Web Transaction Recorder issues
  • Troubleshoot WPM Player issues
    • Troubleshoot WPM Browser problems during playback
  • Collect diagnostic logs for WPM playback problems
  • Monitor WPM logfiles with SolarWinds SAM

You tin likewise:

  • Review WPM System Requirements and configuration details in the WPM Getting Started Guide.
  • Search for solutions in the SolarWinds Success Eye, which likewise includes a WPM Troubleshooting Guide.
  • Look for related discussions in the SolarWinds online IT community, THWACK.

Make up one's mind if FIPS Mode is enabled

If your organization adheres to the Federal Information Processing Standard (FIPS) and FIPS mode is enabled on the Orion server, WPM may behave differently.

For example, recordings and transactions created in before versions of WPM may fail on remote systems where FIPS is now enabled. Some deportment may fail, such as steps that involve certificate hallmark. CPU and retentivity usage may be impacted on remote systems, resulting in Down transactions.

Before troubleshooting WPM issues on a remote arrangement, determine if FIPS mode is enabled past checking for a FIPS mode icon at the bottom of the Web Transaction Recorder window:

Another way to cheque for FIPS mode is to examine logs.

  1. Log into the remote system.
  2. Enable VERBOSE logs.
  3. Start the Web Transaction Recorder.
  4. Navigate to the default log directory, C:\ProgramData\SolarWinds\Logs\SEUM\
  5. Examine the WPMRecorder.log.
  6. Check for the post-obit entry: FIPS mode enabled

To learn more most this US Government standard, see:

  • Enable FIPS for Orion Platform products
  • Enable FIPS manner for WPM on remote systems

Troubleshoot Web Transaction Recorder issues

Pingdom integration issues

You can create recordings for use as Transaction Checks in SolarWinds Pingdom, as described in Integrate WPM with SolarWinds Pingdom. If you run across bug with those files, review requirements and note these details:

  • Web Transaction Recorders must exist continued to your Pingdom account via an API token with Read-Write access, equally described in the WPM Getting Started Guide.
  • This functionality is not supported in FIPS-enabled environments.
  • Pingdom supports WPM recordings up to 60 seconds long. To shorten recordings, remove extraneous steps and actions. Alternatively, y'all can salvage it to Pingdom but note that cloud probes will timeout after 1 minute.
  • The following Spider web Transaction Recorder actions are not currently supported by Pingdom:
    • Document authentication
    • Proxy authentication
    • File Download
    • File Upload
    • Prototype Friction match
    • Press key
  • If you need to change steps in a Transaction Bank check created in WPM, apply the Web Transaction Recorder to edit steps. You lot can use the Bank check Editor in Pingdom to add intervals, regions, and tags in Pingdom, or prepare alerts, but steps tin can only exist edited in WPM.

If messages about the Pingdom API token appear:

  • Confirm that the token was entered correctly when the Web Transaction Recorder was configured.
  • Log into your Pingdom account to confirm that:
    • The API token is still valid.
    • Read/Write permissions were granted to the API token.

Need assistance? WPM and Pingdom support is provided past carve up teams. For help working with WPM features such every bit the Web Transaction Recorder, contact SolarWinds Support. For help with Pingdom features, such every bit intervals, regions, tags, or alerts, see Pingdom Support.

Recording file size considerations

SolarWinds recommends limiting the size of recordings to 1 MB. Avoid including unnecessary steps and actions in recordings. Recordings over i MB can event in:

  • Slow playback.
  • The disability to:
    • Save recordings to the Orion server, or
    • Create transaction monitors.
  • Delayed WPM Role player communication with the Orion server.
  • OutofMemory exceptions from the SolarWinds Information Service (SWIS).

Work with JavaScript-related messages in the Deprecated WPM Recorder

You may come across the JavaScript issues while performing actions in the Deprecated WPM Recorder:

  • JavaScript carte du jour items are not recognized.
  • Clicks on <div> structures are not recognized.
  • OnMouseOver events are not recognized.

Press Ctrl+Shift while performing the problem action, to add actress data to the recording that can be used to identify the root cause.

To avoid slow playback, use Ctrl+Shift to record simply actions that cause problems.

SolarWinds recommends using the latest Web Transaction Recorder to create all recordings. The Deprecated WPM Recorder is beingness phased out of WPM.

Keyboard shortcuts practice not work

Use mouse clicks instead of keyboard navigation in the webpage.

The middle and right mouse buttons are disabled when using the Web Transaction Recorder.

Links do non work during recording

Try to detect an culling method. For case, if the Compose email link on a page does non work, perhaps the same action can be accomplished by clicking the Inbox button.

Recordings cannot cosign proxy servers

If FIPS mode is enabled, add wait times to steps that traverse proxy servers. You can as well check proxy settings on Web Transaction Recorders.

With FIPS manner enabled, recordings cannot validate HTTPS SSL certificates

If FIPS fashion is enabled, you may meet recordings that cannot validate HTTPS certificates and navigate to an IP address, even if a valid certificate is installed. Error messages similar to the following may appear: "In that location is a problem with this website's security certificate. Install a valid certificate on all machines where the recording and related transactions will be played dorsum."

This issue relates to how the Web Transaction Recorder handles Subject Alternate Proper name (SAN) values in server certificates. By default, the IP Address is used as the DNS Name entry blazon in Chrome because domain addresses are more static than IP Address values.

To inquiry possible workarounds, encounter:

  • SSL cert does not work with IP address for SAN (© 2021 Stack Exchange, Inc., available at superuser.com, obtained on February 1, 2021)
  • IP addresses in SubjectAltName in SSL website certificates fail for some browsers (© 2021 TriathalonMike, available at www.michaelm.info, obtained on February 1, 2021)
  • Internet X.509 Public Fundamental Infrastructure Certificate and Document Revocation List (CRL) Profile (Net Engineering Chore Force, bachelor at ietf.org, obtained on February 1, 2021)

Spider web Transaction Recorder is unresponsive

Restart the recorder and recreate your recording.

"You lot must be a WPM Ambassador" bulletin appears

This message may appear if a recording inherits Admin permissions as part of an Active Directory (AD) group. To resolve this issue, add the AD account as a user in the Orion Web Console.

To review account permissions in the Orion Web Console, click Settings > All Settings > Manage Accounts.

See the Orion Platform Administrator Guide for details about Agile Directory. Run into also How the Deprecated WPM Recorder handles business relationship permissions in the Success Center.

The Deprecated WPM Recorder cannot include a certificate in a recording because the private key cannot exist exported

To include a certificate in a recording, WPM exports that certificate with private fundamental. If WPM cannot export the key, this message appears:

WPM cannot include the selected certificate in the recording because the individual key cannot exist exported. Import the document locally with a individual primal that tin exist exported or install the certificate on all systems where that recording volition be played.

To make the individual key exportable for the certificate on the remote arrangement that hosts the recorder, either Import the certificate locally with a private central that can exist exported, or install the document on all systems where that recording volition exist played. For details, click here.

Alternatively, add certificates to the Windows Trusted Root Certificates list on remote systems that host the Web Transaction Recorder and WPM Player service. If Windows and other browsers trust a certificate, WPM recordings and transactions will also.

Troubleshoot X,Y Capture Mode

Use this checklist to help diagnose common bug with X,Y Capture Mode:

  • Try adding steps to a recording to better identify the action where playback failed. Past doing this, you lot suspension down the transaction to multiple steps then yous tin can examine the screenshots to find the action that caused an issue.
  • Run the transaction in the recorder and ensure that all necessary items load during playback. The object to be clicked must be in place and active earlier the click action is executed.
  • If page content loads slowly, insert a Wait activity before the XY activity. This allows content to load completely earlier executing the XY action.
  • Endeavor to re-tape the recording on the same system where the WPM Player service is installed.
  • If using a proxy that requires authentication, ensure proxy credentials are properly captured in the recording and/or the WPM Player where the recorded transaction is played is configured to use Active Directory accounts. See Manage SEUM-User accounts in WPM.
  • If playback fails on the Image Match activity, try the following:
    • Check zoom settings for the remote system's Bone. Set Windows Display settings for "Scale and layout" to the default value, 100%.
    • Examine the screenshot folio to see if the image appears.
    • Image Match may exist affected past font smoothing settings. Avoid using Image Match on an expanse that includes text.

      Prototype Friction match is not supported on animated objects.

The Deprecated WPM Recorder can't count duration time on web pages with automated redirects

If a transaction recorded in the Deprecated WPM Recorder involves navigating to a web folio that includes an automatic redirect to another page, the time spent navigating to the showtime web page may not be included in calculated in the overall duration fourth dimension.

To capture accurate durations when creating a recording that involves navigating to web pages that redirect to another spider web page:

  1. For the step that redirects to some other spider web page, correct-click and select Preserve navigation request from the shortcut bill of fare.
  2. When prompted to verify that you want to preserve navigation requests, click Aye.

If you enable this pick, navigation may take longer to complete than it would if this option was disabled.

An Hallmark Required dialog box appears during recording or transaction playback

An Authentication Request dialog box may appear while creating a recording or playing back a WPM transaction that involves a website. This can occur if:

  • The SEUM-User account used by the Web Transaction Recorder or WPM Worker procedure cannot admission the website.
  • The browser's Internet Properties are configured to prompt for user names and passwords and/or the website URL is not in the list of trusted sites.

In that location are several ways to resolve this outcome:

  • Adapt domain permissions.
  • Add the website equally a trusted site for domain accounts.
  • Create a Chromium allowlist.
  • Use a Grouping Policy Object (GPO) to extend permissions for domain accounts.

Encounter as well Manage SEUM-User accounts in WPM and Use domain accounts as SEUM-User accounts.

To prevent the Authentication Asking dialog box from actualization, grant sufficient permissions for:

  • The domain accounts utilized by the Web Transaction Recorder to capture steps that involve the problematic website.
  • The domain accounts used past the WPM Actor service to play steps in a recorded sequence.

Add together websites as trusted sites for domain accounts

Another fashion to avoid the Authentication Required dialog box is to add the website that requires authentication as a trusted site for the domain accounts used by WPM for transactions.

  1. Open a remote desktop (RDP) session for the domain account.
  2. Use the [Windows logo key + R] keyboard shortcut to open the Run dialog box.
  3. Type inetcpl.cpl and click OK to open the Internet Properties dialog box.
  4. Switch to the Security tab and click Local Intranet > Sites > Advanced.
  5. In the Local intranet dialog box, type the website URL and click Add together.
  6. Click Shut > OK > OK to close the dialog box.
  7. Navigate to the website you lot added to verify the updated configuration.

Use a Chromium allowlist to specify legitimate sites for domain accounts

Another method is to employ a Chromium allowlist. Instead of adding trusted sites for each domain account, create an allowlist that includes legitimate sites by editing the Windows Registry.

SolarWinds strongly recommends that yous back up your Windows Registry before modifying it. You should only edit the registry if yous are experienced and confident in doing then. Using a registry editor incorrectly tin can cause serious issues with your operating system, which could require you to reinstall your operating system to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

To create a Chromium allowlist:

  1. On systems that host the Web Transaction Recorder and WPM Histrion Playback service, add this key to the registry: HKLM\Software\Policies\Google\Chrome\AuthServerWhitelist
  2. Append the registry key with the website URL, as shown in this example: HKLM\Software\Policies\Google\Chrome\AuthServerWhitelist="world wide web.google.com"

Extend permissions for domain accounts with a GPO

You can too use a GPO to provide permission for domain accounts used by WPM and then they don't crave extra authentication to access websites.

  1. Open GPMC on your Domain Controller.
  2. Create a GPO or utilize an existing GPO linked to the Organizational Unit of measurement (OU) that contains the domain accounts used in WPM.
  3. Under User Configuration, expand Policies > Windows settings > Net Explorer Maintenance > Security.
  4. Double-click Security Zones and Content Ratings, then chose Import the current security zones and privacy settings.
  5. Click Go along, and then click Modify Settings.
  6. In the Internet Properties dialog box, switch to the Security tab and click Local intranet, click Sites, and add together the websites you want domain accounts to be able to access.

Admission iFrames in a different domain from the parent web application

By default, capturing coordinates in inline frames (iFrames) is not direct supported in WPM 2019.4 or afterward due to timing issues. WPM blocks Ten,Y clicks inside iFrames that are in unlike domains than the parent web application. Afterwards loading a folio from a dissimilar domain into an iFrame, clicks that occur inside that iFrame will non exist highlighted during playback and text verification will fail.

To learn about workarounds and adjusting default settings for iFrame handling, run into Capture coordinates in iFrames.

Recordings created in the Web Transaction Recorder that utilise Image Match for pattern images are likewise large

Select only pocket-sized regions or portions of the image to meliorate playback performance. Images that exceed 1 MB may cause the following issues:

  • SolarWinds Information Service (SWIS) OutOfMemory exceptions
  • Saving recordings to the Orion server may fail
  • Creating a transaction based on a recording may fail due to crashes or communications failures.
  • General WPM performance issues, including Orion Spider web Console functionality, the Spider web Transaction Recorder, and the WPM Player.

Additional tips for using Image Friction match with pattern images include:

  • Avoid using Image Friction match for an paradigm that appears over text displayed past the web application.
  • Exercise not utilize Image Friction match for an image that appears over a GIF, JPEG, PNG, or other lossy format epitome types. Deportment may fail randomly due to the lower precision of those formats.
  • Image Lucifer activeness doesn't piece of work over Inline Frame (iFrame) elements due to scrolling limitations.

Disable Windows hallmark when playing recordings

If hallmark issues occur when playing dorsum recordings, check if the recorded website uses Windows authentication for its login process. Some systems are set upward to pass-through Windows credentials without prompting for a username and password. If you create a recording on such a arrangement, the username and countersign required for the website is non saved with the recording. This may result in an authentication problem when the recording is played back on a dissimilar organization.

To force a recorder to e'er prompt for a username and password for websites protected by Windows authentication:

  1. Log into the system that hosts recorder with a local user account instead of a domain account.
  2. Open Internet Explorer and click Settings > Cyberspace options.
  3. Switch to the Advanced tab, clear the Enable Integrated Windows Authentication check box, and save your changes.

  4. Restart Internet Explorer.

Troubleshoot WPM Player bug

If you encounter transaction playback issues on remote systems that host the WPM Player Playback service (for case, if transactions have longer than usual or don't play at all), start with these basic troubleshooting steps:

  • Confirm that remote systems meet WPM Player specifications in the WPM System Requirements.
  • Check the WPM Player configuration. Run into Deploy WPM Players to remote systems.
  • Try using a different browser.
  • Flush the browser cache.
  • Leverage browser debug tools. For example, printing F12 in Chrome to open the Developer Tools (DevTools) pane.
  • Verify that SEUM-User accounts have adequate permissions.
  • Use the Orion Service Director to restart WPM agent services.
  • Disable screenshot captures during transaction playback.

Tips to troubleshoot WPM Thespian issues that begin after an upgrade

Here are examples of issues y'all may come across after upgrading WPM:

  • Transactions assigned to a WPM Player location switch to Unknown status.
  • The SolarWinds WPM Playback Actor service enters a retry loop when attempting to spawn a new WPM Worker process. Each attempt is cited in C:\ProgramData\SolarWinds\Logs\SEUM\AgentService.log.
  • A WPM Actor location appears equally Downwards in the Orion Platform, or the status intermittently switches betwixt Up and Down.
  • "Location non responding" entries appear in SEUM.Jobs.log files typically stored C:\ProgramData\SolarWinds\Logs\SEUM\.

If navigation to a URL takes besides long or times out, open the browser DevTools tab to determine if the SSL portion consumes well-nigh of the navigation asking. If so, the following details may exist helpful:

  • Bank check if the WPM Player location has a pure Internet connexion, of if communication is blocked by a firewall.
  • Advice delays may be related to the Automatic Root Certificates Update component (© 2021 Microsoft Corp., available at docs.microsoft.com, obtained on June 24, 2021). This component checks the list of trusted government on the Microsoft Windows Update Website. A list of trusted root Certification Government (CAs) stored on the local computer. When an awarding is presented with a document issued past a CA, information technology checks the local copy of the trusted root CA list.
    • If the certificate is not in the listing, the Automatic Root Certificates Update component contacts the Microsoft Windows Update Spider web site to come across if an update is available.
    • If the CA was added to the Microsoft list of trusted CAs, its certificate is added to the trusted certificate store on the computer.

    When an application is presented with a certificate issued by a CA, it inspects the local copy of the trusted root CA list. If the document is not in the list, the Automatic Root Certificates Update component checks the Windows Update website for available updates. If the CA was added to the Microsoft list of trusted CAs, its certificate is automatically added to the trusted certificate store on the organisation hosting the WPM Player.

    You tin use the Windows CAP12 Diagnostics Event Viewer to determine which sites are blocked and so disable the firewall rule that blocks them. (© 2021 Microsoft Corp., available at social.technet.microsoft.com, obtained on June 24, 2021)

  • When the WPM Playback Histrion service spawns a WPM Worker process to run a transaction footstep, the service waits for a specific corporeality of time for the worker procedure to establish inter-process communication by opening a WCF channel. That time is limited in dissimilar means, in unlike versions of WPM.
    • In WPM 2020.2.four and before, the timeout was hardcoded at 30 seconds. If the WPM Playback Histrion service exceeded the timeout, some other worker procedure was spawned. Customers that could not upgrade were brash to disable Automatic Root Certificate updates.
    • In WPM 2020.ii.five and later on, a workerConnectTimeout value was added to the SolarWinds.SEUM.Agent.Service.exe.config file on remote systems, typically stored in C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player. The default timeout is at present xc seconds, as represented by the workerConnectTimeout value: 90000.

  • Root CA Trusted List (CTL) bug tin can prevent a worker process from opening a WCF aqueduct if the process cannot utilise the local enshroud of CTL for reasons such as:

    • The CTL cache at the organisation level expired and cleared, or
    • The cache is empty because the WPM Role player location lost its cyberspace connection.

WPM Players upgrades fail

See Upgrade WPM Players on remote systems for troubleshooting tips, which include examining the following file if an upgrade fails:

C:\ProgramData\SolarWinds\Logs\SEUM\InstallerPlaybackPlayer.log

The WPM Actor Settings tool or the SolarWinds Domain Account Configuration Tool displays the following message: Unable to load actor settings from Agent Service. An error occurred while sending the request.

Starting in WPM 2020.2.6, the SolarWinds WPM Playback Histrion service must be running to back up both of these WPM tools. Launch the Orion Service Director from the Windows Starting time menu to restart that service, if necessary.

Transactions with wait times cause timeout errors.

If a transaction includes wait times for text validation or Image Match only timeout errors occur during playback, you can extend the request timeout value for an entire Web Transaction Recorder or WPM Thespian Playback service. Run across Configure WinHTTP request timeouts.

Screenshots consume excess space on the Orion database server.

During transaction playback, WPM Worker processes capture a screenshot for each stride in a transaction.

  • Screenshots for failed steps are sent to the Orion database so they tin can be included in related WPM alerts. To display those screenshots in the Orion Web Panel, navigate to the Transactions Details view and scroll to the Screenshots of Last ten Stride Failures widget.
  • Screenshots for successful steps are saved to a SQLite database on the organization that hosts the WPM Player Playback service. If you examine transaction steps in the Orion Web Console (as described above), agent workers transfer related screenshots to the Orion database server for employ in widgets.

For each organisation that hosts a WPM Actor, yous tin can arrange screenshot settings in config files stored in C:\Program Files (x86)\SolarWinds\Orion\SEUM\Actor, by default.

  • SolarWinds.SEUM.Amanuensis.Worker.exe.config
    • saveScreenshotsToLocalDirectory="false"
  • SolarWinds.SEUM.Agent.Service.exe.config
    • saveScreenshotsToLogDirectory="false"
    • includeCurrentScreenshotInResults="fake"
    • includeFailedScreenshotInResults="truthful"

See also Include a screenshot in an electronic mail alert for a failed transaction step.

The internal database on the WPM Role player expands and blocks playback on a remote system.

As transactions play at scheduled intervals, WPM saves screenshots and playback results to a SQLite database on the remote organisation. Depending on the number and complexity of assigned transactions, the database file tin can grow rather large in the following default location: c:\ProgramData\SolarWinds\SeUM\Data\AgentStorage.s3db

If the file size grows too large (for example, over 2 GB), playback results may non be correctly transferred to the Orion server. This can happen due to a slow network connection between the Orion server and the WPM Player. The file will continue to grow because results are generated faster than they are downloaded from Player.

To resolve this issue, you can:

  • Edit screenshot settings in SolarWinds.SEUM.Amanuensis.Service.exe.config on the remote system.
  • Arrange database retention settings for the SQLite database on the remote organization
  • Edit scheduled intervals for transaction playback in the Orion Web Console.

If your surround includes SolarWinds SAM, you can employ the SolarWinds Web Performance Monitor (WPM).apm template to monitor the size of the internal WPM Player database.

WPM Player cannot play a transaction due to SEUM-User business relationship permissions.

When the WPM Player simulates cease-user activeness past playing dorsum transactions, information technology employs a SEUM-User account for each WPM worker process that occurs in the transaction. If you cannot playback a transaction from the Player'south location, it may be because a SEUM-User account does not have permission for required resources, including logging into the local system.

SEUM-Users must belong to the local Ambassador group on the system hosting the WPM Player that will utilise them. To learn more, see Manage SEUM-User accounts in WPM.

Player symptoms include:

  • Cannot play whatsoever transaction from some location, with the transaction in Unknown status.
  • A transaction plays dorsum fully in the recorder only not in the thespian.
  • Transactions fails to play due to WPM worker process errors on the player's server.
  • Transaction bounces betwixt Up and Down status.

Recorder symptoms include:

  • Transition plays on the recorder (located on the same organisation where Player is) only fails when played directly in player.
  • When recording with WPM, the website'south Windows authentication works. But when deployed, it does non and the page returns "not authorized" page.

A log entry similar to this one appears in the AgentWorker logs:

The WPM Player cannot play the transaction because the SEUM-User business relationship utilized for playback does not take permission for required resource, including logging in to the local organization.

To resolve this outcome, add all SEUM-User accounts to the local Administrators group on the Player server.

Here are some additional tips:

  • By default, the WPM Histrion on the Orion server includes ii SEUM-User accounts and WPM Players deployed to remote systems include 7 accounts. You tin add up to 15 SEUM-User accounts, simply the recommended limit is 12, based on aspects of the host organisation such as CPU and RAM.
  • When using GPO in an environs, adjust Local Security Policies to grant permission to Allow log on locally for all SEUM-User accounts on the local arrangement. Otherwise, changes in the user configuration on the local organisation are overwritten with every GPO update.
  • When GPO is practical, it may prevent WPM services from using the SEUM-User accounts for certain tasks, such every bit creating WPM worker processes. Pay attending to which GPO is used and alter it for WPM requirements.
  • If you see WPM transaction steps with a "Not played all the same" status on the Transaction Details folio, this may be related to domain policy access rights to the WPM Role player, or incorrect passwords for user accounts in configuration files. See this commodity in the SolarWinds Success Center.
  • If adding SEUM-Users to the local Administrators group nevertheless doesn't help in your environment, set up upward domain users for playback instead local users. Encounter Use domain accounts as SEUM-User accounts.
  • If y'all meet an Hallmark Required prompt when playing back transactions, run across this article.

WPM transactions fail to play — Fault LOGON TYPE NOT GRANTED - Logon Failure

To support playback, WPM worker processes play steps of transaction recordings, collect statistics and screenshots, and render playback results to the WPM Histrion. If the WPM Playback Player service cannot first WPM worker processes, yous may receive the following bulletin:

ERROR_LOGON_TYPE_NOT_GRANTED - Logon failure: the user has not been granted the requested logon blazon at this computer.

This bulletin may appear if a security policy was changed to limit "log on locally" permissions.

  1. Verify that the SEUM-User business relationship has permission to log on locally.
  2. If necessary, change limitations for user accounts.

The WPM Playback Actor service should run every bit "Local Organisation," non nether a specific user account.

"Element not found during playback" message

If an element is missing during playback, you can try to edit the original recording. If that doesn't work, you may need to recreate both the recording and existing transactions based on the recording.

WPM Role player drops queued items.

The SEUM agent has an internal queue that it uses for transaction playback requests that cannot be immediately executed because there are no free WPM worker processes. If the number of items in the queue is shut to the number of transactions assigned to the Player, it normally means that the Player is close to its chapters and is not able to play transactions fast enough. If a transaction is in the queue and a new playback asking for the aforementioned transaction arrives, it is dropped because the queue cannot contain duplicate requests.

If the number of dropped requests increases significantly, it may betoken that the WPM Player cannot play transactions equally fast every bit they are requested. Considering reducing load past removing some transactions from the WPM Player.

If your environment includes SolarWinds SAM, yous can utilize the SolarWinds Web Performance Monitor (WPM).apm-template to monitor the WPM Role player installed on the Orion server. Run into Monitor WPM logfiles with SolarWinds SAM.

Internal WPM Player database exceeds capacity.

Depending on the number and complexity of assigned transactions, the size of the internal WPM Player database that stores playback requests, results, and screenshots can grow rather large. This file is located at C:\Program Files (x86)\SolarWinds\Orion\SEUM\Data\AgentStorage.s3db.

If the file grows too large, (for example, over 2 GB), playback results may not exist downloaded properly if a irksome network connection exists between the Orion server and the WPM Actor. The file will continue to grow because results are generated faster than they are downloaded from Player.

If your environment includes SAM, you tin can utilize the SolarWinds Web Performance Monitor (WPM).apm-template to monitor the WPM Player database. See Monitor WPM logfiles with SolarWinds SAM.

The Player Load Pct widget on the Transaction Locations page shows the load percentage of a system hosting an individual WPM Player is at 100%.

Per the Scalability Engine Guidelines for SolarWinds Products, SolarWinds recommends limiting the number of monitored transactions assigned to a WPM Player to 12 or less. However, note that many factors can touch on the load on transaction locations that host WPM Players, including:

  • The complexity of assigned transactions.
  • The length of playback for each transaction.
  • The length of intervals between each transaction playback.
  • The processor speed and RAM bachelor on the system hosting the WPM Player.
  • The amount of SEUM-User or domain accounts involved in playback. See Manage SEUM-User accounts.

Y'all can bank check the WPM Player load on a remote organization in the Player Load Percentage widget, as described in Display transaction locations in WPM.

WPM Role player does not work later Windows 10 upgrade.

After upgrading a remote system to Windows 10 5.1607 or later, the WPM Playback service may not kickoff. A "Thespian could not be registered — Please bank check firewall settings" message may appear fifty-fifty if the firewall is completely disabled.

Yous may be prompted to cosign certificates even though recordings created in the Deprecated WPM Recorder include embedded awarding certificates. This issue can occur if a Windows x upgrade overwrites existing registry entries and prevents the WPM Playback service from starting.

  1. First, verify the following conditions:
    • SEUM-User accounts exist on the target organisation.
    • The target system is part of a domain that supports Active Domain accounts.
    • The WPM Histrion is configured to use Active Domain accounts.
  1. Back upwardly all histrion and recorder configuration files with a *.config suffix in these default folders:
    • C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player
    • C:\Programme Files (x86)\SolarWinds\Orion\SEUM\Recorder
  1. Reinstall the WPM Role player and restore *.config files, if necessary.

On macOS systems, configuration files are stored here: /Contents/Resources/WPM Recorder.exe.config

All WPM transactions on a remote arrangement switch to an Unknown land.

If you remove the WPM Player from a system, transactions enter an Unknown land. Deploy a WPM Actor to the remote system to begin running transactions again. Player settings should friction match the settings previously used by WPM.

WPM screenshots are smaller than the size of the Deprecated WPM Recorder window.

Transactions created with the Deprecated WPM Recorder do not shop the size of the webview in recordings, fifty-fifty if you enlarge the webview before creating a recording. The WPM Player uses a default window size during playback. Utilize the new Web Transaction Recorder instead.

As a workaround for the Deprecated WPM Recorder, start recording and enable XY, Capture Mode briefly earlier disabling information technology. Then create your recording as you normally would; WPM should recall the screen size.

  1. Resize the webview to the desired size.
  2. Click Record to start capturing steps.
  3. Type about:bare in the address bar and click OK to navigate to a bare page.
  4. Click Ten,Y Capture Style to enable it.
  5. Click anywhere in the top left corner of the webview.
  6. Click X,Y Capture Fashion again to disable it.
  7. Enter the URL where you want to tape steps and click OK.
  8. Create your recording.

WPM Actor Playback service cannot play transactions due to lack of permissions.

Group policies and user permissions can block the SolarWinds WPM Player Playback service from running transactions. This assumes local SEUM users are local administrators of the remote system that serves as the player location. Group policies that are known to cake transactions include:

  • Allow log on locally
  • Run all admins in admin approval style

Bank check the local grouping policy on the remote system to determine if:

  • "Allow log on locally" is prepare to Disabled, or
  • "Run all admins in admin approval mode" is set up to disabled.

To suit settings and so the WPM Player service can log on locally:

  1. Log into the remote system.
  2. From the Windows Start menu, open up the Local Security Policy app.
  3. Aggrandize Local Policies and click User Rights Consignment.
  4. Double-click Allow log on locally.
  5. Click Add User or Grouping.
  6. (Recommended) Add all SEUM users to the local 'Administrators' group.
  7. Click OK and so OK to save your changes and close the Properties window.

To adjust User Account Command (UAC) settings:

  1. Log into the remote system.
  2. Open the Local Security Policy app.
  3. Aggrandize Local Policies and click Security Options.
  4. Curlicue downward and double-click "User Business relationship Command: Run all administrators in Admin Approval Mode".
  5. On the Local Security Setting tab, click Enabled so click Apply.
  6. Restart the system.

Transactions based on recordings that include AngularJS neglect during playback.

Transactions created from recordings that involve Angular JS and the Route AngularJS service may fail during playback if the AngularJS structural framework lacks required resources, as consumed past WPM worker processes.

SolarWinds recommends the post-obit workarounds for this situation:

  • Increase CPU and RAM resources on the remote system that hosts the WPM Actor service.
  • Change the numWorkerProcesses value to 1 in the post-obit file:
    C:\Programme Files (x86)\SolarWinds\Orion\SEUM\Player\SolarWinds.SEUM.Agent.Service.exe.config.

    Restart the WPM Playback Actor service to apply the new configuration. This limits simultaneous worker processes on the WPM Player so only 1 transaction plays at a time and frees resources for use past AngularJS.

Alternatively, schedule transactions assigned to the WPM Player and then that but one AngularJS step occurs during scheduled playback time. Restart the WPM Playback Actor service to utilise the new configuration.

WPM Players migrated to new systems don't work.

See Troubleshoot WPM Player migration in the WPM Getting Started Guide. Related Success Center articles include:

  • Transactions not playing after upgrading
  • WPM Player is unable to play transaction
  • WPM transaction is slow or fails during playback in Orion Web Panel just works in WPM Recorder.
  • WPM transactions are Unknown and System.UnauthorizedAccessException appears in Agent Service Log

SolarWinds.SEUM.Agent.Worker.exe errors occur during playback:

If you receive the following bulletin, restart the system that hosts the WPM Player:

[SolarWinds.SEUM.Agent.Worker.exe][3] ERROR SolarWinds.SEUM.PingdomRunner.Player - ERROR, System.IO.IOException: The directory proper noun is invalid.

If that doesn't resolve the issue, verify that the TEMP or TMP surround variable for the SEUM-User-# or domain account used to run the worker process exists.

Troubleshoot WPM Browser issues during playback

Here is an overview of the WPM Browser procedure that supports transaction playback:

  • A WPM worker procedure triggers a probe to start the following applications that work together to collect playback statistics:
    • WPM Browser.exe
    • chromedriver.exe
  • When a transaction finishes, the probe shuts down the two applications and passes playback results to the WPM worker procedure.
  • The worker process stops the probe procedure and passes results to the WPM Player service, which adds results to the local database on the remote system.
  • The WPM Role player service reads stored playback results and passes them to Orion server for analysis.

Annotation the following details well-nigh the WPM Browser, which replaced the Chromium browser in WPM 2019.4.1:

  • This procedure is related to the post-obit files:
    • Process: C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\ChromiumProbe\WPM Browser\WPM Browser.exe
    • Configuration: C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\ChromiumProbe\WPM Browser\WPM Browser.exe.config
  • To troubleshoot look fourth dimension issues in text validation or Paradigm Match steps, try adjusting timeout settings for the WPM Browser.

Changes made to the WPM Browser config file apply to all transactions played on the host organisation.

Adjust the WPM Browser configuration

As mentioned earlier, WPM triggers a probe to start the WPM Browser.exe process that runs scheduled transactions and collect playback statistics.

If you run across WPM Browser problems such as excess CPU consumption, yous can use various Chromium command line switches to command the startup of the WPM Browser, too as the ChromeDriver process that collects logs virtually transaction playback.

This involves adding a line to the agentWorkerConfiguration section of the following file:

C:\Plan Files (x86)\SolarWinds\Orion\SEUM\Role player\SolarWinds.SEUM.Agent.Worker.exe.config

The following example shows a probeExtraArgs command with various command line switches:

- probeExtraArgs="--enableWebDriverLogging --scriptExecutionTimeoutS 120 --extraSwitches &quot;--enable-logging=stderr --log-level=0 2&gt; &amp;i&quot;"

If you add that line to SolarWinds.SEUM.Agent.Worker.exe.config, WPM passes the following probeExtraArgs values to the probe that initiates transaction playback: :

  • enableWebDriverLogging: Switch ChromeDriver.exe logging levels to Verbose to collect extra information for troubleshooting. Related log files are stored in this default folder: C:\ProgramData\SolarWinds\Logs\SEUM\ChromeDriver_[*].logs.
  • scriptExecutionTimeoutS: Set a timeout after which any script executed past ChromeDriver volition fail. The default value 30 seconds.
  • extraSwitches: First the WPM Browser with Chromium control line switches.

To learn more about command line switches, review the adjacent department. For reference, see Listing of Chromium Command Line Switches (© 2021 Peter Beverloo, bachelor at https://peter.sh, obtained on October six, 2021).

How to format values for the extraSwitches command

Chromium command line switches are passed to the probe as text values so it's important to utilise proper formatting. To protect a set up of values in an extraSwitches command line, surround them with the &quot; HTML entity instead of standard quote symbols ("). Use a single space to separate each set of values.

In this excerpt of the before probeExtraArgs example, --enable-logging=stderr --log-level=0 two&gt;&amp; is the value protected by the &quot; HTML entity:

--extraSwitches &quot;--enable-logging=stderr --log-level=0 2&gt;&amp;1&quot;

Collect diagnostic logs for WPM playback problems

Before contacting SolarWinds Back up to troubleshoot playback issues, follow these steps to collect details that tin reduce the time required to resolve your issue.

The default location for WPM log files in Windows is C:\ProgramData\Solarwinds\Logs\SEUM. Click here to discover WPM log files in macOS. Yous tin can likewise gather macOS crash reports (© 2020 Apple Corp., available at support.apple tree.com, obtained on December fourteen, 2020).

To collect diagnostic logs on Windows systems:

  1. (Recommended) In the Orion Spider web Console, unmanage all transactions at the WPM Player location or move assigned transactions to some other WPM Player location.
  2. Log into the Orion server or the remote arrangement, depending on where playback issues occur.
  3. To reduce the size of diagnostics files, articulate all files and folders in the WPM log directory located at C:\ProgramData\Solarwinds\Logs\SEUM

    4. Skip any files currently in utilise by WPM, if prompted.

  4. On Windows systems, run the SolarWinds Log Adjuster. Click Start > SolarWinds Orion > Log Adjuster, so gyre to the WPM department.
    • For a transaction based on a recording created in the new Web Transaction Recorder, enable DEBUG for these rows:
      • Agent Worker - Browser
      • Amanuensis Worker - Player
    • For a transaction based on a recording created in the Deprecated WPM Recorder, enable DEBUG for these rows:
      • Agent Worker (deprecated)
      • Agent Worker (deprecated) - Browser
      • Agent Worker (deprecated) - Player

  5. (Optional) Use the enableWebDriverLogging command line to switch ChromeDriver.exe logging levels to Verbose, equally described in Troubleshoot WPM Browser issues during playback. Related log files are stored in this default folder: C:\ProgramData\SolarWinds\Logs\SEUM\ChromeDriver_[*].logs.

  6. Wait an hour, or every bit much time as needed for the transaction to fail at to the lowest degree once.

  7. To collect diagnostics on Windows systems, you tin either:
    • Run Orion Diagnostics from the Windows First Menu,
    • Run C:\Program Files (x86)\SolarWinds\Orion\SolarwindsDiagnostics.exe, or
    • In the Orion Web Console, navigate to the My Orion Deployment page, switch to the Diagnostics tab, and then click Collect New Diagnostics.
  8. To avoid disk infinite issues, return to the SolarWinds Log Adjuster to turn off DEBUG. Click Reset to default > Apply.
  9. Export the recording you are having problem with.
  10. In the Orion Spider web Console, navigate to the Transaction Details view, take a screenshot of the Transaction Details widget, and save information technology to a PDF file.

  11. Submit a SolarWinds Back up ticket that includes a ZIP file with the following items:
    • WPM diagnostic logs
    • The recording y'all are having trouble with.
    • Credentials used for the recording, if applicable.
    • A screenshot of the Transaction Details widget.

Locate Web Transaction Recorder log files on macOS systems

To find Web Transaction Recorder log files on a macOS system:

  1. In the Finder window, navigate to the Applications location
  2. Right-click the WPM Recorder icon to open its context menu.

  3. Click Evidence Parcel Contents.

Note the post-obit details nigh default macOS file locations:

  • The recorder configuration file is located hither: /Contents/Resources/WPM Recorder.exe.config
  • The recorder log file is located here: ~/Library/Logs/WPM Recorder/WPMRecorder.log

You tin can also gather macOS crash reports (© 2020 Apple tree Corp., available at back up.apple.com, obtained on Dec xiv, 2020).

Monitor WPM logfiles with SolarWinds SAM

If your deployment includes SolarWinds SAM, you tin can utilise the SolarWinds Spider web Performance Monitor (WPM) application monitor template to track returned values for the AgentService.log for a specific WPM Player, including:

  • Full: The full number of errors in the log file.
  • New: The number of newly found error strings.
  • Last_Message: The last error message and its position in the log file.

Be sure to specify the correct path to the AgentService.log file in the Script Arguments field for the template. The default path is: C:\Programme Files (x86)\SolarWinds\Orion\SEUM\AgentService.log.

For an overview, watch Understanding Application Templates.