Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > The WPM Player is unable to play transaction

The WPM Player is unable to play transaction

Created by Roger Lofamia, last modified by Nigel on Nov 10, 2017

Views: 1,973 Votes: 2 Revisions: 4

Updated: November 10, 2017


This article describes the issue where playback is unable to play from the Player's location. The WPM installation process creates several service accounts named SEUM-User-*, and in some cases these users do not have enough permission to run the playback.



All WPM versions


WPM Player

  • Unable to play any transaction from some location, transaction is in unknown status;
  • Transaction which is working fine in Recorder doesn’t work in Player;
  • Transactions fails to play due to worker process errors on Player server;
  • Transaction is bouncing between Up and Down status.
  • Transaction for a site (for example Not Found but the recorder machine is able to play the recording. But during player playback, it fails and set to Down status.


  • Transition is played properly on Recorder (located on the same machine where Player is) but fails when played directly in Player.
  • When recording with WPM, the website Windows authentication works. But when deployed, it does not and the page returns "not authorized" page.


  • One of the following errors is appearing in AgentWorker logs:

2017-07-22 14:46:57,533 [PlaybackDispatcher] ERROR SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessLauncher - Error launching worker process.
System.Exception: Error launching worker process. Error: logon error. System error: 0x569

2017-07-22 14:46:57,533 [PlaybackDispatcher] ERROR SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - Unable to create worker process. Trying again.
SolarWinds.SEUM.Agent.Exceptions.AgentException: Unable to launch worker process 137f9db8-584d-4fa6-8f3b-35b07c15f883

2017-07-22 14:46:57,533 [PlaybackDispatcher] ERROR SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - Unable to create worker process after 3 retries.

2017-07-22 14:46:57,533 [PlaybackDispatcher] ERROR SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - No available user account to start new worker process.

Potential root cause error

The WPM Player cannot play the transaction because user which is used for playbacks has insufficient permission for required resources (i.e accounts doesn’t have permission to logon locally to the machine).


Add all of the SEUM-Users accounts (WPM service accounts) to the local Administrators group on the Player server.

How to add SEUM-User to local Administrators group

  1. Select Computer Management setting from the system menu, or open Run from the Start button and type the command: compmgmt.msc.
  2. Double-click Local Users and Groups, and double-click Users.
  3. Right-click on SEUM-User-1 and click Properties.
  4. Select the Member Of tab.
  5. Click Add, and enter the local Administrator's group name for this user. To find all of the available groups, click Advanced, and then click Find now – all groups will be listed. Select Administrators group and click OK.
  6. Press OK and OK again.
  7. Repeat steps 3-6 for each SEUM-User, and then click OK.
  8. In Computer Management, double-click Services & Applications node. and double-click Services.
  9. Right-click on SolarWinds WPM Playback Player Service and select Restart.
  10. Right-click on SolarWinds WPM Playback Player Proxy and select Restart if running.

Additional info

  • When Group Policy Objects (GPO) is used in the environment, you need to adjust those Local Security Policies to grant permission to Allow log on locally'for all "SEUM-Users" on local machine. Otherwise, changes in user configuration on local computer will be overwritten with every GPO update.
  • When GPO is applied then it often prevents the WPM services from using the SEUM-User accounts for certain task, such as creating the worker processes. Pay attention to which GPO is used and modify it for WPM requirements.
  • If adding SEUM-Users to the local Administrators group still doesn’t help in your environment, set up domain users for playback instead local users.
Last modified