Applications Systems

WPM transactions fail after upgrade to 2025.4 and above when using domain accounts with Orion Agent

After upgrading to SolarWinds WPM 2025.4 and above, transactions may fail on WPM Players that use domain accounts and are deployed on the same machine as the Orion Agent. The issue is caused by insufficient permissions for the domain accounts on the SEUM log folder.

First published date

12/11/2025 5:54 PM

Last published date

6/10/2026 10:06 PM

Overview

Customers may observe that WPM transactions go down or fail to execute after upgrading to version 2025.4 and above. This occurs when WPM Players are configured to use domain accounts (instead of the default local SEUM-User accounts) and are installed on the same machine as the Orion Agent, main Orion Server, or Additional Polling Engines.

The failure is due to the domain accounts lacking write access to the C:\ProgramData\SolarWinds\Logs\SEUM folder. The error message displayed in the Web Console is: "Probe process has failed with exit code 1." No new logs are generated in the SEUM folder, making diagnosis challenging. 

A screenshot of a computerAI-generated content may be incorrect.

Product section

Web Performance Monitor

Cause

After the upgrade, domain accounts used by WPM Player do not have the necessary write permissions to the SEUM log folder (C:\ProgramData\SolarWinds\Logs\SEUM). This prevents the creation of log files and causes transaction failures. The issue does not affect installations using the default local SEUM-User accounts. 

Resolution

To resolve this issue, please upgrade to SolarWinds Platform 2026.2 and above.  

As a workaround to resolve the issue, manually grant Full Control permissions to the domain accounts used by WPM Player:

  1. Navigate to C:\ProgramData\SolarWinds\Logs.
  2. Right-click on the SEUM folder and select Properties.
  3. Go to the Security tab and click Edit.
  4. Click Add, then enter the names of the domain users used by WPM Player.
  5. Select the Full control checkbox under the Allow column for each added account.

  1. Apply the changes.

No service restart is required. Transactions should succeed on the next playback.

 

Note:
This issue can also occur on fresh installations if the WPM Player is switched from local SEUM-User accounts to domain accounts on machines with the Orion Agent installed.