SolarWinds uses cookies on our websites to facilitate and improve your online experience. By continuing to use our website, you consent to our use of cookies. For further details on cookies, please see our cookies policy.
Hide this message
Your VM Perplexities Called, and They Need You to Read This.
Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.
Get your free white paper.
Updated November 7, 2018
This section contains details about WPM issues you may encounter that prevent you from creating or playing back a recording. It includes known issues and workarounds that may help you get back on track. See also:
Installation
If upgrading from WPM 2.2.1, you may be prompted to install Microsoft .NET Framework 3.5 so the Orion Installer can remove WPM 2.2.1. Download .NET Framework 3.5 from the Microsoft Downloads site (© 2018 Microsoft Corp., available at https://www.microsoft.com/en-us/download/details.aspx?id=21, obtained on May 10, 2018) and run the Orion Installer again.
JavaScript-related messages
You may encounter the following JavaScript issues while performing actions in the recorder:
Press Ctrl+Shift while performing the problem action. This adds additional data to the recording that may allow access to the problematic element.
To avoid slow playback, use Ctrl+Shift only to record the actions that are causing problems.
"Object doesn't support property or method 'createEventObject'" message
Use X/Y mode to recreate a recording if the WPM Player can't find a web item on a page, or if you receive this message when for recordings that involve Java Applets, JavaScript frameworks (AngularJS, KnockoutJS, and so on), Flash, Silverlight, and sometimes SharePoint. See Error: Object doesn't support property or method 'createEventObject'.
Keyboard shortcuts do not work
Use mouse clicks instead of keyboard navigation in the webpage.
Links do not work during recording
Try to find an alternative method. For example, if the Compose email link on a page does not work, perhaps the same action can be accomplished by clicking the Inbox button.
Recorder is unresponsive
Restart the WPM Recorder program and recreate your recording.
"You must be a WPM Administrator" message
You may receive this message when creating a recording if you inherited 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. You can also check the PermissionValue in the [Solarwinds_APM].[dbo].[SEUM_WebUserPermissions] table. See also Troubleshooting Orion AD Issues .
WPM cannot include a certificate in a recording because the private key cannot be exported
To include a certificate in a recording, WPM exports that certificate with private key. If WPM cannot export the key, this message appears:
WPM cannot include the selected certificate in the recording because the private key cannot be exported. Import the certificate locally with a private key that can be exported or install the certificate on all computers where that recording will be played.
To make the primary key exportable for the certificate on the WPM recorder machine, install the website certificate on the machine where you are running the WPM recorder. For details, visit the SolarWinds Success Center and see this article: WPM cannot include the selected certificate in the recording because the private key cannot be exported. See also Client certificates in WPM recordings.
Use this checklist to help diagnose common problems with X,Y Capture Mode:
Image Matching on animated objects is not supported.
Player cannot play a transaction due to SEUM-User account permissions
When the WPM Player simulates an end user playing back transactions recordings, it employs an SEUM-User account for each WPM worker process. If you cannot playback a transaction from the Player's location, it may be because a SEUM-User account does not have permission for required resources, including logging into the local machine.
The original name for WPM was Synthetic End User Monitor (SEUM), a term that is still used in reference to user accounts. You may also see it in directory names and system messages.
Player symptoms include:
Recorder symptoms include:
A log entry similar to this one appears in the AgentWorker logs:
The WPM Player cannot play the transaction because the SEUM-User utilized for playback does not have permission for required resources, including logging in to the local machine.
To resolve this issue, add all SEUM-User accounts to the local Administrators group on the Player server. See Set permissions for SEUM-User accounts.
Here are some additional tips:
Disabling Windows authentication for players
If you encounter authentication problems when playing back recordings, check if the recorded web site uses Windows authentication for its login process. Some systems are set up to pass-through Windows credentials without prompting for a username and password. If you create a recording on such a computer, the username and password required for the website is not saved with the recording. This may result in an authentication problem when the recording is played back on a different computer.
To ensure that the recorder always asks for a username and password for websites protected by Windows authentication:
WPM transactions fail to play — ERROR LOGON TYPE NOT GRANTED - Logon Failure
To support WPM, a WPM worker process plays steps of transaction recordings, collects statistics and screenshots, and returns playback results to the WPM Player.
If the player service cannot start the WPM worker processes, you may receive the following message:
ERROR_LOGON_TYPE_NOT_GRANTED - Logon failure: the user has not been granted the requested logon type at this computer.
This message may appear if the security policy was changed that limited the "log on locally" permissions.
To troubleshoot this issue:
It is also important to check that the player service is running as "Local System" rather than logging in to a specific user account.
For more information, refer to:
Element not found during playback
If an element was not found during playback, recreate both the recording and the transaction.
WPM 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 close to the number of transactions assigned to the Player, it usually means that the Player is close to its capacity and is not able to play transactions fast enough. If a transaction is in the queue and a new playback request for the same transaction arrives, it is dropped because the queue cannot contain duplicate requests.
If the number of dropped requests increases significantly, it usually means that the player is not able to play transactions as fast as they are requested. You should remove some transactions from the player.
If SolarWinds SAM is also installed, use the SolarWinds Web Performance Monitor (WPM).apm-template to assess the status and overall performance of the WPM Player installed on the Orion server by using Windows Performance Counters.
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 be downloaded properly if a slow network connection exists 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. If SolarWinds SAM is also installed, use the SolarWinds Web Performance Monitor (WPM).apm-template to track the size of the internal WPM Player database.
WPM Player does not work after Windows 10 upgrade
After upgrading a remote machine to Windows 10 v.1607 or later, the WPM Playback service may not start. A "Player could not be registered — Please check firewall settings" message may appear even if the firewall is completely disabled. You may be prompted to authenticate certificates even though recordings include embedded application certificates. This issue can occur if a Windows 10 upgrade overwrites existing registry entries and prevents the WPM Playback service from starting.
C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player
C:\Program Files (x86)\SolarWinds\Orion\SEUM\Recorder
Additional troubleshooting resources for playback
Before contacting SolarWinds Support to troubleshoot failed playback, follow these steps to collect WPM Player logs.
Skip any files currently in use by WPM if prompted.
Run the application from the player location by right-clicking and selecting Run as administrator.
In the WPM section, set the DEBUG logger level for:
Agent Worker
Agent Worker – Browser
Agent Worker – Player
Use these settings for loggers:
File size: 50 MB
# of files: 50
Click Apply.
C:\Program Files\(x86)\SolarWinds\Orion\SEUM\Player\SolarWinds.SEUM.Agent.Worker.exe.config
C:\Program Files\(x86)\SolarWinds\Orion\SEUM\Player\SolarWinds.SEUM.Agent.Worker.exe.config
C:\ProgramData\Solarwinds\Logs\SEUM\AgentWorker.logs
C:\Program Files (x86)\SolarWinds\Orion\SEUM\SolarwindsDiagnostics.exe
to collect diagnostics to send to SolarWinds Support.If SolarWinds SAM is also installed, you can use the SolarWinds Web Performance Monitor (WPM).apm-template to track returned values for the AgentService.log, related to a WPM Player, including:
You must specify the correct arguments (including the path to the AgentService.log file) for this monitored component in the Script Arguments field. The default monitored path is: C:\Program Files (x86)\SolarWinds\Orion\SEUM\AgentService.log
.