The WPM Player is unable to play transaction

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.

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 Google.com) Resource Not Found but the recorder machine is able to play the recording. But during player playback, it fails and set to Down status.

Recorder

• 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.

Logs

One of the following errors is appearing in AgentWorker logs:

ERROR SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessLauncher - Error launching worker process.
System.Exception: Error launching worker process. Error: logon error. System error: 0x569

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

ERROR SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - Unable to create worker process after 3 retries.

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. You may also check the Local Group Policy on the Player Machine and verify in the User Rights Section that SEUM-Users or a group they are:

• added to "Allow log on locally"
• added to "Allow log on through Remote Desktop Services"
• not added in "Deny access to this computer from the network"
• not added in "Deny log on as a batch job"
• not added in "Deny log on as a service"
• not added in "Deny log on locally"
• not added in "Deny log through Remote Desktop Services".

How to add SEUM-User to local Administrators group

1. RDP to your Player location.
2. Go to Computer Management (start > Run > compmgmt.msc) > Local Users and Groups > Groups.
3. Double-click the Administrators then click Add.
4. Click the Locations to set it to local computer (select the computer name). Then click Ok.
5. Click Advanced > Find Now.
6. Select all the SEUM users and click OK (shift-click to select all).
7. Save

Additional Information

• 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.