Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Log & Event Manager (LEM) > Error -2147189176 when running a LEM report

Error -2147189176 when running a LEM report

Created by David Clark, last modified by Jason Dee on Jul 18, 2016

Views: 125 Votes: 1 Revisions: 7

Updated 7/18/2016

Overview

The following error appears when running a report in LEM:

Logon failed. Error code: -2147189176

Environment

  • All LEM versions
  • All Windows versions

Cause 

This can occur due to any of the following reasons:

  • A password issue.
  • The installation was corrupted or the reports software was not installed using the Run as Administrator option.
  • LEM Reports was installed as a package with Crystal Run Time.
  • The configured hostname cannot be reached.
  • Reports does not have necessary privledges

Resolution

  1. On the LEM Web interface, go to Build > Users.
  2. Click + on the top right and select LEM User.
  3. In the Name field, enter reports and create a password.
  4. Change Role to Reports.
  5. Go back to reports and click gear icon > Configure > Managers. 
  6. Use the IP ADDRESS of the LEM and the username and password set in Step 3. 
  7. Click the green +, close the window and run the report. If the problem is not resolved, perform the following:
    1. Uninstall Crystal Run Time the Solarwinds Log and Event Reports software through Windows Programs and Features.
    2. Delete the corresponding folders from C:\Program Files (x86)\
      • Solarwinds Log and Event Reports 
      • Crystal
    3. Reinstall Crystal Run Time and  SolarWinds Log and Event Reports separately.
      Note: Right-click Run as Administrator when installing. 
    4. Repeat Steps 1 to 6
  8. Verify port 9001 Is not blocked.
  9. Try running reports with "Run as Administrator".
  10. Disable any anti-virus or anti-malware software you are running.

 

Last modified
08:44, 18 Jul 2016

Tags

Classifications

Public