Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > Player Load spikes to more than 100%

Player Load spikes to more than 100%

Updated March 7, 2017


WPM Player load is spiking to more than 100% on the WPM Player.


WPM Player


Player SEUM-Users account.


Workaround 1:

  1. Check if the players are being played.
  2. If not, adjust the limitation of the seum-users.
  3. The Domain policy forbids non-administrator local accounts to log into the computer with the SEUM player.
  4. Modify the SEUM user account that is experiencing this issue to be a local admin (add to local administrators group). 
    1. Go to Control Panel > User Accounts > Manage User Accounts.
    2. Select the SEUM user > Properties > Group Membership.


Workaround 2:

The service does not have the correct passwords for the User Accounts in its configuration files.

  1. Open a Remote Desktop Session to the system with the problematic WPM Player.
  2. Open a Run Prompt > services.msc.
  3. Stop the following services:
    SolarWinds WPM Playback Player
    SolarWinds WPM Playback Player Proxy
  4. Open another Run Prompt > lusrmgr.msc.
  5. Go to Users > delete all "SEUM-User-xx" Accounts.
  6. Open another Run Prompt > appwiz.cpl.
  7. Find "SolarWinds Web Performance Monitor Transaction Player v2.2"
  8. Run a repair on this to recreate the User Accounts.


Workaround 3: The load could be genuine because of number of load taken by each transaction, this can be addressed by increasing the number of worker processes to share the load between transactions.

Refer to this KB for more info:



Last modified