Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Web Performance Monitor (WPM) > Agents no longer work after migrating WPM to another polling engine

Agents no longer work after migrating WPM to another polling engine

Created by Harry Griffiths, last modified by MindTouch on Jun 23, 2016

Views: 654 Votes: 2 Revisions: 5


Agents are no longer responding after migrating WPM to another polling engine.


All WPM versions


The agents are still pointed to the old engine.

To verify this issue matches this article, please run this query in Database Manager to verify the engine ID information.

  1. Go to Volume:\Program Files (x86)\SolarWinds\Orion\DatabaseManager.exe.
  2. Right Click and open it as administrator.
  3. Click Add Default Server.
  4. Expand your Orion Database.
  5. Right Click and Click New Query.
  6. Copy and Paste the Below Query:
SELECT TOP 1000 * FROM [dbo].[AllEngines]

To see what engineID was assigned before to those agents clear the query and copy and paste the below in:

SELECT TOP 1000 * FROM [dbo].[SEUM_Agents]


  1. Verify the newly created and correct engine ID.
  2. Copy and paste the below query in Database Manager, replacing X with the old and new values.
  3. UPDATE [dbo].[SEUM_Agents]
    SET PollingEngineID = X
    WHERE PollingEngineID = X
    SET PollingEngineID = X, the NEW polling engine ID.
    WHERE PollingEngineID = X, the OLD polling engine ID.
    For example, 1 is  the old engine ID and 2 is the new poller that was migrated to:
    UPDATE [dbo].[SEUM_Agents]
    SET PollingEngineID = 1
    WHERE PollingEngineID = 2



Last modified