Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Serv-U logs incorrectly parsed by LEM

Serv-U logs incorrectly parsed by LEM

Updated February 20, 2017

Overview

This article describes how to resolve an issue where LEM web console does not show any Serv-U connector logs, even though the connector is configured and started.

Environment

LEM 6.3.1

Cause 

The issue is caused by either of the following:

There are spaces in log file name

OR

Incorrect date suffix format selected.

Resolution

The log path where LEM is supposed to read the logs is actually correct and it matched LEM log path location but the format of the logs configured within Serv-U is not supported by LEM

  1. Login to ServU server and change the log format to match LEM supported format as follows:

    New File Name Interval: Monthly: yyyymmDD
  2. Do a test and LEM should be able to parse the Serv-U logs.

 

 

Last modified

Tags

Classifications

Public