Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > WPM error: Remove locations not responding

WPM error: Remove locations not responding

Updated March 11th, 2016


WPM v2.0


Remove locations not responding. There are three remote players that are not working in Orion Web Performance Monitor (WPM). The following error message is displayed after running diagnostics for the issue –
ERROR SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - Error creating user account for Agent.
 System.DirectoryServices.AccountManagement.PrincipalOperationException: Logon failure: the user has not been granted the requested logon type at this computer.
 ---> System.Runtime.InteropServices.COMException: Logon failure: the user has not been granted the requested logon type at this computer


SEUM-USERS are not added to local administrators group.


Add local SEUM users to local administrators group on each player to start reporting location. Do the following steps to add local SEUM users to local:
  1. Right click My Computer, go to Manage.
  2. Scroll down to Configuration > Local Users and Groups > Groups.
  3. Double click Administrators.
  4. Click Add. Make sure that the location (middle box) is set to the server name and not the domain. Do not type anything in the box, and click Advanced instead.
  5. Click Find now. You should see the seven SEUM-USER-# accounts in the bottom pane. 
  6. Select all of them and then click OK.  
  7. Select OK again.
  8. Restart WPM playback service onthat machine, and wait 5-10 minutes and see if the transaction will then play properly.
          Note: Make sure to monitor everything in the player. Monitor the player for 24 hours to verify if group policies get applied overnight.
Last modified