Network Management

Action execution failed because it can not access event log

When Executing Windows Event Log on a Remote Server, the following error message appears: Action execution failed because it can not access event log.

First published date

10/23/2018 7:45 PM

Last published date

10/18/2022 12:18 PM

Overview

When Executing Windows Event Log on a Remote Server, the following error message appears:

Action execution failed because it can not access event log.

 

Product section

Network Performance Monitor

Cause

The Business Layer (or Orion Module Engine) is performing the remote connection and it should have permissions to read and write to the remote Windows Event Log.

Resolution

Set the SolarWinds Orion Module Engine service ro run under a domain account which has admin permissions on the Orion and the remote server.

  1. On the Orion server, open Services Management console (services.msc).
  2. Locate SolarWinds Orion Module Engine service.
  3. Right-click on SolarWinds Orion Module Engine and select Properties.
  4. On the Log On tab, select This account: option and enter the credentials for an account that has admin privilege to both Orion server and the remote host.
  5. Simulate the Windows Event Log action and the result will now be successful.

Note:This is currently a limitation if the Orion server and the remote host are members of a different domain. You cannot change the Log on account of SolarWinds Orion Module Engine service using a domain admin of the remote host.