Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Log & Event Manager (LEM) > LEM 5.3.1 Release Notes

LEM 5.3.1 Release Notes

Created by Caroline Juszczak, last modified by Caroline Juszczak on Mar 29, 2017

Views: 3 Votes: 0 Revisions: 4

 

Revised: January 31, 2012

These release notes provide additional guidance for SolarWinds Log & Event Manager (LEM) v5.3.1.

 

Features and Improvements

This version of SolarWinds Log & Event Manager provides the following improvements, organized by functional area:

  • Console
  • Manager
  • nDepth Log Storage/Search
  • Agent and USB-Defender
  • Reports
  • MSSQL Auditor
  • New and Updated Connectors

Console

 

  • Fixed an issue that affected Check Point certificate and USB Defender Local Policy uploads to the LEM Manager.1
  • Fixed issues related to the Data Simulator in Evaluation mode not stopping.2
  • Fixed an issue in which the 5.3 Console changed the way it grouped filter conditions when it was restarted.3
  • Fixed an issue that required users to delete and re-add their LEM Manager a second time upon first configuring their LEM Console.4

 

Manager

 

  • Fixed an issue in which the LEM Manager did not recognize LEM Agent global automatic update settings.5
  • Fixed an issue related to built-in Groups not working in Rules.6
  • Fixed several issues related to LEM Manager and Agent connectors for database products such as SQL, PostgreSQL, and MySQL.7
  • Fixed an issue in which CMC command viewsysinfo did not show uptime for approximately 2 days.8

nDepth Log Storage/Search

 

  • No changes from 5.3.

Agent and USB-Defender

 

  • Fixed several issues related to LEM Manager and Agent connectors for database products such as SQL, PostgreSQL, and MySQL.7
  • Fixed an issue that prevented the USB Defender Local Policy tool from starting.9
  • Fixed several issues that caused the Apache Access and IAS RADIUS connectors to create unnecessary non-Agent nodes.10
  • Fixed an issue that caused the IIS, IISFTP, ISA, and Trend ISWVA connectors to only be compatible with logs that rotated every hour.11
  • Fixed an issue that prevented the Remote Agent Installer from installing USB Defender from computers running Windows 7 or Windows Server 2008.12

 

Reports

 

  • Fixed the USB-Defender report (2003-09-050).13

MSSQL Auditor

 

  • No changes from 5.3.

New and Updated Connectors

SolarWinds LEM version 5.3.1 includes 44 new connectors and several improved connectors.

Installing and Upgrading SolarWinds Log & Event Manager

The following sections provide required information for installing and upgrading Log & Event Manager.

  • Installing Log & Event Manager
  • Supported Versions
  • Upgrading Log & Event Manager

Installing Log & Event Manager

SolarWinds Log & Event Manager consists of a virtual appliance (referred to as "Manager" and "Appliance"), a desktop Console, and the LEM Reports application. The LEM virtual appliance requires VMWare ESX/ESXi with vSphere 4.0 or later. The LEM Console is an Adobe AIR application, compatible with Windows, Mac OS, and Linux. Log & Event Manager Reports is Crystal Reports-based and requires Windows.

For more information on installing Log & Event Manager, please refer to the Log & Event Manager QuickStart Guide.

Supported Versions

SolarWinds supports Log & Event Manager Versions 5.2 and later, and TriGeo SIM versions 5.0 and later.

Upgrading Log & Event Manager

The following section provides critical notes regarding how to complete an upgrade to the latest version of Log & Event Manager, regardless of your current version.

Detailed upgrade instructions are available in the Log & Event Manager Upgrade Guide.

Let Agents Reconnect During Incremental Upgrades

When you are preforming incremental upgrades, like upgrading from v5.0 to v5.2 in order to upgrade to v5.3.1, we recommend you let your LEM Agents reconnect to the upgraded LEM Manager after each step.

Download the Latest Connector Update Package After You Upgrade

All LEM upgrades include a connector update, but we often update the stand-alone Connector Update package between releases as well. To ensure you have the latest version of all of the LEM connectors, download the current Connector Update package here.

For instructions to apply the LEM Connector Update package, see How to apply a LEM connector update package or the Log & Event Manager Upgrade Guide.

 

Known Issues

The following sections provide information related to previously unmentioned, known issues in Log & Event Manager.

  • You Must Install a New License After Upgrading from Versions Prior to v5.3
  • Log & Event Manager Appears Incompatible with vSphere 5.0
  • Uninstallation Errors After 5.3 Agent Upgrade
  • Issues Displaying IP/Hostnames from Agents
  • McAfee On-Access Scan Prevents the Upgrade Script from Extracting the Upgrade Files

You Must Install a New License After Upgrading from Versions Prior to v5.3

Log & Event Manager v5.3 included a new license for all LEM customers. Please access your activation key from the SolarWinds Customer Portal, and activate your LEM Console from Manage > Appliance > License. If you receive an error ("Error retrieving license information"), check your license key and network connection, or use the manual activation feature from the SolarWinds Customer Portal.

If you are upgrading from a functional v5.3 LEM appliance, you have already completed this step.

Log & Event Manager Appears Incompatible with vSphere 5.0

vSphere 5.0 is missing a file needed to deploy SolarWinds LEM, which makes it appear the two products are not compatible. VMware is working on a permanent solution to this issue and the immediate workaround, along with the file needed for the fix, is providedhere.

Agent Uninstallation Errors After 5.3 Agent Upgrade

Customers attempting to uninstall an agent that was originally installed on a previous version may receive one of two errors:

  • A popup with Exception "java.lang.IllegalArgumentException...": Resolved by using the Remote Agent Uninstaller rather than Add/Remove Programs.
  • A JVM launcher error: Resolved by running the current Agent Installer, then uninstalling the Agent.

Issues Displaying IP/Hostnames from Agents

Due to the changes in the Java Runtime Environment and licensing functionality, some agents may appear with a new IP and/or hostname combination. We've attempted to ensure this is the same IP/hostname that connects to the appliance, but it is possible that this detection is less reliable on some platforms.

On Unix/Linux platforms, there is a known issue in the Java Runtime Environment that makes this detection even less reliable.

Workaround: Enter the expected/desired values in the /etc/hosts file. The Agent will then use and transmit those values to the appliance.

McAfee On-Access Scan Prevents the Upgrade Script from Extracting the Upgrade Files

The upgrade script fails and returns the error, cp: cannot stat '/tmp/smb/Upgrade/x64jar': No such file or directory when McAfee On-Access Scan prevents it from extracting the upgrade files.

Workaround:

  1. Open McAfee On-Access Scan Properties
  2. Click the Blocking tab.
  3. Clear Block the connection when a threat is detected in a shared folder.
  4. Click OK.
  5. Rerun the LEM upgrade.

 

Development and Support ID Fix Table

The following table provides the internal Development ID numbers and external support ID numbers for customer-reported issues resolved in this release.

Issue Link Support ID number Development ID number
1 285223
28594
CMANAGE-398
2 N/A COPSCENTER-269
COPSCENTER-270
COPSCENTER-295
3 00108467
00108521
CMONITOR-943
4 N/A CMANAGE-397
5 N/A AGENT-114
6 285593 MGR-442
7 N/A AGENT-133
CORE-99
8 N/A APPLIANCE-451
9 290211 CMANAGE-398
AGENT-134
10 282424
00108602
MGR-427
TOOL-659
11 284738
285403
CORE-97
12 298219 FB97417
13 290438 REPORT-43

 

Version History

Click the links below for the release notes for previous versions of SolarWinds Log & Event Manager.

 

Legal

Copyright© 1995-2012 SolarWinds, Inc. all rights reserved worldwide. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of SolarWinds All right, title and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its licensors. SolarWinds®, the SolarWinds logo, TriGeo®, ipMonitor®, LANsurveyor®, and Orion® are among the trademarks or registered trademarks of the company in the United States and/or other countries. All other trademarks contained in this document and in the Software are the property of their respective owners.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS OR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Microsoft®, and Windows 2000 Server®, Windows 2003 Server®, and Windows 2008 Server® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Last modified
15:43, 29 Mar 2017

Tags

Classifications

Public