Submit a ticketCall us
Home > Success Center > Log & Event Manager (LEM) > nDepth Error: Search ended prematurely

nDepth Error: Search ended prematurely

Created by Interspire Import, last modified by Justin Rouviere on Mar 17, 2017

Views: 28 Votes: 1 Revisions: 16

Overview

When searching for nDepth, the following error appears below the search bar:

Error: General Error: Search ended prematurely

Environment

All LEM versions

Cause

The error might occur due to the following reasons:

  • If you are using a LEM Desktop Console version that is different from the version of your LEM virtual appliance.
  • If you are able to perform a query with no conditions, there might be a problem with how your query is constructed.
  • There may be a problem with a part of your database or your connection to it.
  • The LEM is running low on resources or had an error which was resolved by restarting the manager service.

Resolution

There are different causes why this error occurs and below are ways on how it can be resolved:

  • If you are using the LEM Desktop Console, verify that the version you are using is the same as your LEM virtual appliance. Your Desktop Console version can be verified by clicking on the SolarWinds logo in the top left corner and your virtual appliance version can be verified under Manage > Appliances. Alternatively, you can try connecting via the web console and search again.
  • Clear any search conditions and click Search again. If the search completes and displays results, there may be a problem with how your query is constructed.
  • Change the time range to Last 10 min and click Search again. If the search completes with this time frame but not with the time frame you were using previously, there may be a problem with a part of the database. If this problem occurs, please contact SolarWinds Support.
  • If the error persists on every search after trying the steps above, restart the Manager service.

 

Restart the Manager service on your LEM appliance  

  1. Connect to your LEM virtual appliance using either the vSphere console view, or an SSH client such as PuTTY.

  2. If you are using an SSH client, log in to your LEM virtual appliance using your CMC credentials.

  3. At the cmc> prompt, enter manager.
  4. At the cmc::cmm prompt, enter restart.
  5. Press Enter to confirm your entry.
    Note: Restarting the Manager service will make your LEM Manager unavailable for about one minute. However, no data is lost during this process.
  6. Enter exit twice to leave the CMC interface.

 

Last modified
12:14, 17 Mar 2017

Tags

Classifications

Public