Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Web Performance Monitor (WPM) > Opening a WPM Transaction in the Orion Web Console Produces the error Exception has been thrown by the target of an invocation

Opening a WPM Transaction in the Orion Web Console Produces the error Exception has been thrown by the target of an invocation

Updated November 9, 2017

Overview

Opening a WPM Transaction produces the error:

Unexpected Website Error 
Exception has been thrown by the target of an invocation

Environment

  • WPM 2.2.1

Cause 

The cause of this issue is that the player that the transaction is assigned to isn't assigned to an existing polling engine ID. This issue would be most common after migrations.

Resolution

  1. Open a Remote Desktop Session to the Orion Server.
  2. Open Database Manager.
  3. Click Add Default Server.
  4. Expand the Orion Database.
  5. Find the Engines table > Right-click > Query Table.
  6. Click Execute Query.
  7. Find the SEUM_Agents table > Right-click > Query Table.
  8. Click Execute Query.

    In the SEUM_Agents table, the entry for PollingEngineId should match an existing, active polling engine in the engines table. If it doesn't match an existing engine then update it with the following:

 

  1. Click on the SEUM_Agents table.
  2. Click Enable Table Editing.
  3. Update PollingEngineID to the correct engine ID for the WPM Player.
  4. Restart the Orion Module Engine on the Orion Server.
  5. Restart the WPM Playback Service on the related WPM Player machine.

 

After you perform the steps above, clicking on the transaction in the Orion Web Console should no longer produce the error.

 

 

Last modified

Tags

Classifications

Public