Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Log Parser monitor shows unknown on Windows 2008 and script fails

Log Parser monitor shows unknown on Windows 2008 and script fails

Updated December 28, 2017

Overview

When using the Log Parser (Powershell) monitor, Total number of strings found component, against a 2008 R2 node and the file to be parsed is empty, does not contain a match, or has only one match in it, the component "Total number of strings found" says unknown. When that same template is applied against a Windows 2012 node, the component correctly works.

 

When the script is run on the 2008 node, it fails with one of the following errors:

  • If the file has 1 line: "Array assignment failed because index '1' was out of range." 
  • If the file has 0 lines: "Array assignment failed because index '0' was out of range." or may not return any result.

 

These are RuntimeExcept errors of IndexOutOfRange.

 

image.png

Environment

  • All versions of SAM
  • The logs to be parsed are on Windows 2008 R2
  • The file to be parsed is empty, has 0 or 1 line containing the search string in it

Cause 

Unknown

Resolution

The file must have 2 or more lines containing the string that you are trying to search for.

--or--

The log parser monitor works correctly on Windows 2012 and newer.

 

 

Last modified

Tags

Classifications

Public