Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Trap/Syslog service shutting down automatically

Trap/Syslog service shutting down automatically

Updated November 24, 2016

Overview

This article overviews a potential solution when your Trap Viewer / SysLog Services are not staying in a Running state after migrating your SolarWinds Application Server to a new Hostname/IP.

Environment

Any Orion using Centralized Licensing (At least Core 2016.2)

Cause 

This is due to the Centralized Licensing reading the first entry of the dbo.OrionServers table, which may reference your old application server.

You can verify what server has the license, by navigating to Settings -> All Settings in the Orion Web Console. Then click the "License Manager" at the bottom of the page. The App Server that the license is associated with will be listed here. If this is incorrect, follow the steps in the resolution below.

Resolution

  1. Open Orion Database Manager.
  2. Right click and select the [dbo].[OrionServers] table.
  3. If the old server entry exists here, click the "Enable Table Editing" button, right click, and delete the row
    Note: A backup of this table may be a good idea in case you need to roll back any changes.
  4. Restart Orion Services.
  5. Check the License Manager page. The correct server should now be associated with the license.

 

Last modified

Tags

Classifications

Public