Applications Systems

Transactions Unknown, Player not responding: The remote server returned an error: (400) Bad Request

Orion Server (Communication Error: The remote server returned an error: (400) Bad Request.). Unable to delete playback results. constraint failed FOREIGN KEY constraint failed

First published date

8/15/2019 8:58 PM

Last published date

2/21/2022 1:12 AM

Overview

Transactions from a specific can go unknown which is caused by a WPM Player Location not responding. 

Player location error: 
The remote server returned an error: (400) Bad Request

SEUM Agent Service logs (C:\ProgramData\SolarWinds\Logs\SEUM\):
ERROR SolarWinds.SEUM.Agent.DAL.AgentStorage - Unable to delete playback results.
code = Constraint (19), message = System.Data.SQLite.SQLiteException (0x800027AF): constraint failed
FOREIGN KEY constraint failed
 

Product section

Web Performance Monitor

Cause

Local storage is not working properly (s3db file).

Resolution

If errors are present then repair the player, proceed to rebuild the s3db file on the Player. If the issue persists, proceed to repair the Player. If the MSI is missing, damaged, or corrupted, then reinstall the player. Instructions in this order are below.
 

Rebuild the local s3db

  1. RDP to the Player not responding.
  2. Stop WPM Player service
  3. Backup the file C:\ProgramData\SolarWinds\SEUM\Data\ *.s3db (rename and add a .bak at the end of the filename).
  4. Restart service (it should recreate).
 

Repair

Start > Run > appwiz.cpl > Find the playback player > click-click > repair. 
 

Reinstall

Settings > All Settings > WPM Settings > Manage Locations > Add new location > download player 
(or https://your_server/Orion/SEUM/Admin/InstallerDownloader.ashx?installerType=Player)




See also
 • All Transactions are unknown on a specific player location in WPM
 • Transactions are unknown - Location not responding
 • WPM Transactions are unknown
 • How to Repair WPM