I've updated Orion recently, which included upgrading WPM recorder/player to v3.0. I am aware that I'm going to have to replace my recordings, but for some reason, my new recordings on the same location are not working. They come back with an error "Probe process has failed with exit code -1". Don't suppose anyone knows why this might be? I've got the player set to Server initiated communication, which has been tested and comes back as working fine. The WPM is on the same server as the Orion services, and has an internet connection. The Recorder can display the page, and it saves the recording to the orion server without any errors. The monitor is created also without any errors.
Any ideas would be great!
Try to re-record the site using the WPM deprecated recorder.
Link about the new recorder and deprecated recorder: About WPM Recorders
I believe the WPM 3.0 uses the new Recorder.
Types of recorder
The 3.0 WPM Recorder offers a new user interface and portable browser engine support (via Google Chromium) that is not dependent on the locally installed operating system browser.
The Deprecated WPM Recorder is the same one provided in WPM 2.2.3 and earlier.
Use it to record transactions on websites that use Java applets, Microsoft Silverlight, and Adobe Flash technology.
See if this works after a few playbacks.
How do you guys use the old WPM 2.2 recording tool when running WPM 3.0? My 2.2 recorder app wants to force an upgrade to 3.0 immediately, if I skip the upgrade it doesn't open the 2.2 version.
Opened a ticket with support but thought you guys might be quicker
I remember something like that in the upgrade process but when it's all done, you'll definitely still be able to add both recorders. I have both on my workstation now. Just go to Admin >>Settings >> WPM Settings >> Manage Transaction Monitors and there should be a banner on top with links to download both.
We have this issue as well after upgrading to 3.0. This "Probe process has failed with exit code -1" only happens occasionally and we opened a ticket mid August. After collecting logs with support it was determined by the development team that it was a known bug with the current version. They recommended to upgrade to WPM 2019.4 (it looks like it is in RC now) or I would recommend using the legacy player if you can (and recorder).
Sounds like we need to ask the team to investigate that. Would you mind opening a ticket so we can gather some diags and troubleshoot the issue? Feel free to ping the ticket number back here and I will track internally as well. Thanks!
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.