Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Failover Engine (FoE) > Syslog or Trap Service fails to stop on a failover

Syslog or Trap Service fails to stop on a failover

Created by Justin Wyllys, last modified by MindTouch on Jun 23, 2016

Views: 66 Votes: 1 Revisions: 12

Overview

This article provides troubleshooting steps when the Syslog or Trap service fails to stop on a failover or switchover. 

Environment

  • FoE all versions

Cause

Unknown

Resolution

When a Syslog or Trap service  fails to stop on a failover or switchover, additional task in FoE needs to be created to force it to stop these services.

 

For Syslog services:

  1. Go to Applications > Tasks > Add
  2. Enter the following information:
    Name: Stop Syslog service
    Task Type: Pre Stop
    Command: TASKKILL /F /im SyslogService.exe
    Run as: local\SYSTEM (default)
  3. Click OK

 

For Trap services:

  1. Go to Applications > Tasks > Add
  2. Enter the following information:
    Name: Stop Trap service
    Task Type: Pre Stop
    Command: TASKKILL /F /im SWTrapService.exe
    Run as: local\SYSTEM (default)
  3. Click OK
Last modified
19:30, 22 Jun 2016

Tags

Classifications

Public