Windows device status: RPC server is unavailable - Online help | EventLog Analyzer

Windows device status: RPC server is unavailable

The RPC server is unavailable error will be displayed in the device status field if there isn’t any communication between the EventLog Analyzer server and the respective machine from which the logs should be collected. This lack of communication might be due to any of the following reasons:
  1. The machine is disconnected from or not part of the network.
  2. The machine has shut down or stopped running.
  3. There isn’t a physical or virtual firewall.

Troubleshooting steps:

  1. Open the command prompt in the EventLog Analyzer server and ping the host from which logs should be collected. This will verify that there’s basic communication between the machines.
  2. Ensure that the following ports are open:

Rule description

Protocol
Port
Traffic direction (inbound or outbound)
WMI, DCOM, and RPC
TCP
135, 445, and 139
Incoming (for host)
WMI, DCOM, and RPC
TCP
49152 to 65534
Outgoing (for host)
WMI, DCOM, and RPC
TCP
135, 445, and 139
Outgoing (for server)
WMI, DCOM, and RPC
TCP
49152 to 65534
Ingoing (for server)

3. Check if the following rules are enabled in Windows Firewall. 
  1. COM+ Network Access (DCOM-In)
  2. Remote Event Log Management (NP-In)
  3. Remote Event Log Management (RPC)
  4. Remote Event Log Management (RPC-EPMAP)
  5. Windows Management Instrumentation (ASync-In)
  6. Windows Management Instrumentation (DCOM-In)
  7. Windows Management Instrumentation (WMI-In)
To enable any rule, open Windows Firewall > Advanced settings > Inbound Rules. Right-click the respective rule, then click Enable Rule.
Run WBEMTest to verify the WMI connectivity:
4. In the EventLog Analyzer server, click Start. Open Run, type wbemtest, then select OK.

Windows Management Instrumentation Tester


  1. In the Windows Management Instrumentation Tester window, click Connect.
  2. In the Connect window, enter the following:
    1. In the Namespace textbox, enter \\<machine_name>\root\cimv2, where machine_name is the hostname of the source machine.
    2. In the User and Password textboxes, enter the credentials that will be used to collect the logs, and click Connect.
Connect tab - Windows Management Instrumentation Tester
  1. If the connection is successful, that implies there are no issues with the credentials. If you encounter an error message, proceed further based on the error code displayed.
  1. 800706BA: RPC server is unavailable
  2. 80070005: Access denied
  3. 800706BE: RPC has failed
  4. 8007203a: The server is not operational

          • Related Articles

          • Windows agent status: Unavailable

            Establish a remote connection with the machine that the agent is installed on. Open a web browser and ensure that the EventLog Analyzer web UI is accessible. On the remote machine, open the file under C:\Program Files (x86)\EventLog ...
          • Windows device status: Access denied

            The Access denied error indicates that the user account dedicated for log collection does not have the necessary access and permissions to collect logs from the respective devices. There are two approaches to fixing the error: Using a domain admin ...
          • Mismatch in the Windows agent version

            Establish a remote connection with the machine where the agent is installed. Open the Registry Editor, then go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ZOHO Corp\EventLogAnalyzer\LogAgent and ensure that the agent version matches the ...
          • Windows: File Integrity Monitoring (FIM) issues

            Prerequisites: An agent needs to be deployed on the respective machine. Open the EventLog Analyzer GUI. Go to the Settings tab > Configuration > Manage File Integrity Monitoring. Configure the folders in the machine that should be monitored. Verify ...
          • Windows agent service is not running

            Establish a remote connection with the machine running the agent. Open services.msc and check if the ManageEngine EventLog Analyzer agent service is running. Open a web browser and ensure that the EventLog Analyzer web console is accessible. Open the ...