This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

WPM issues after HotFix2 applied

rinat.kirimov over 3 years ago

After we applied HotFix2, our WPM transactions fail to play. Looking at the logs, it seems that the transaction completes but its status on Web console is 'unknown'. The only entry I see in the logs that looks like an error is this:
2020-12-18 15:04:33,215 [SolarWinds.SEUM.Agent.Worker.exe][13] DEBUG SolarWinds.SEUM.PingdomRunner.Player - Failed to kill Chromium process ID: 0
System.ComponentModel.Win32Exception (0x80004005): Access is denied
at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.Kill()
at SolarWinds.SEUM.PingdomRunner.Player.TryKillChromium(Int32 chromiumProcessId)

I double-checked and SEUM accounts are in the Administrators group. I can see the steps played in the transaction logs as SEUM-user-#. It worked before HotFix2 and nothing else changed in the environment.

Top Replies

rinat.kirimov over 3 years ago in reply to katieb +1

Support confirmed that this is a bug in the latest WPM release. So, we are just (im)patiently waiting on the fix now.

0 katieb over 3 years ago

rinat.kirimov we have seen in some WPM upgrades custom changes to the config files get overwritten to default settings. Give that a look first and if nothing looks off you should submit a support ticket. They will be able to help you out.
Cancel
Vote Up 0 Vote Down

Cancel
0 rinat.kirimov over 3 years ago in reply to katieb

Thanks for the reply. I know the support is pretty slammed nowadays, so I figured I'd post here in hopes some other users may have a similar issue.
Cancel
Vote Up 0 Vote Down

Cancel
0 rinat.kirimov over 3 years ago in reply to rinat.kirimov

Comparing config files between 2020.2.1.6402 and 2020.2.2.6824 they look different.
Here are some more relevant(I think) logs:
DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - No workers running in interactive session. Releasing interactive session.
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - } ShutdownWorkerProcess exited
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - { ShutdownWorkerProcess entered
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - Shutting down worker process e631dd72-c5dc-4d1d-8051-217b93905744
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - { OnWorkerProcessRemoved entered
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.Agent - Process e631dd72-c5dc-4d1d-8051-217b93905744 removed
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.Agent - Unable to find process to recording mapping for process e631dd72-c5dc-4d1d-8051-217b93905744 to fire ProcessRemoved event
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessManager - } OnWorkerProcessRemoved exited
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessWcfProxy - Shutting down worker process e631dd72-c5dc-4d1d-8051-217b93905744
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessWcfProxy - Aborting communication channel for worker e631dd72-c5dc-4d1d-8051-217b93905744
2020-12-18 21:55:44,671 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessWcfProxy - Stopping WorkerProcess registration service at: net.tcp://localhost:17777/seum/agent/e631dd72-c5dc-4d1d-8051-217b93905744
2020-12-18 21:55:54,674 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessLauncher - Closing underlying process
2020-12-18 21:55:54,690 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessLauncher - Unloading user profile
2020-12-18 21:55:54,846 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.WorkerProcessManagement.WorkerProcessLauncher - Profile unloaded ok.
2020-12-18 21:55:54,846 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.Helpers.WebCacheHelper - Start clean up WebCache directory: C:\Users\SEUM-User-1\AppData\Local\Microsoft\Windows\WebCache\
2020-12-18 21:55:54,846 [PlaybackDispatcher] DEBUG SolarWinds.SEUM.Agent.Helpers.WebCacheHelper - Cannot find cache directory C:\Users\SEUM-User-1\AppData\Local\Microsoft\Windows\WebCache\
Cancel
Vote Up 0 Vote Down

Cancel
0 katieb over 3 years ago in reply to rinat.kirimov
rinat.kirimov You can check two more things before going to support.... Take a look at the WPM Player local DB size. If it is something rather large, say over 100 MB you can try to stop the Playback Player service - remove the local DB and start the service again (C:\ProgramData\SolarWinds\SEUM\Data\AgentStorage.s3db)
Or you can take a look at the WPM Player debug logs and search for something like:
There is more results than fits into one batch. Setting date to 11/20/2020 07:08:08 so remaining results can be retrieved later.
If found, same actions would be taken here as you would if the DB size was too large.
If you don't find either of those items, you will need to reach out to support.
Cancel
Vote Up 0 Vote Down

Cancel
0 rinat.kirimov over 3 years ago in reply to katieb

Support confirmed that this is a bug in the latest WPM release. So, we are just (im)patiently waiting on the fix now.
Cancel
Vote Up +1 Vote Down

Cancel