Applications Systems

WPM Player service stopped running

This article explains why WPM has stopped and will not run on the WPM server do to Active Directory (AD) is not configured on the server.

First published date

11/12/2018 1:50 PM

Last published date

5/18/2020 8:12 PM

Overview

When your WPM Player service stops running one of the common reasons is due to Active Directory (AD) not being set up on the server.

The steps below will walk you through how do address this.

Product section

Web Performance Monitor

Cause

The root cause of the issue is that WPM detected that there is no AD user configured on the server.

Resolution

Configure the value of numWorkerProcesses="" in the SolarWinds.SEUM.Agent.Service.exe file (by default at C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player) before configuring AD accounts.
If you set value of numWorkerProcesses="1" then only one AD account will be needed for this test purposes (but transactions cannot run in parallel way).
If it helps with starting the service then you can increase value of numWorkerProcesses="" and repeat the steps provided in this article. You just need to have the same amount of unique domain accounts as value of numWorkerProcesses.
Create the user - Configure Domain Accounts for SEUM worker processes Single Sign-On .
The service should run and run as expected.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.