Security Compliance

Error displays after upgrading Patch Manager

This article describes how to troubleshoot an error that displays in the Patch Manager Admin Console after you upgrade the application.

First published date

10/26/2018 9:42 PM

Last published date

10/26/2018 9:42 PM

Overview

After you upgrade Patch Manager server and run the Patch Manager Admin Console, the following error displays in the console:

ewException caught: [Communication failure. The RPC server is unavailable. Destails:dgsrpcinterface::executeportaloperation() failed.], File: EminentWare.Core.Client.RPC.cpp, Line: 483

The same error has been noticed after applying MS security KB patches and rebooted the Patch manager server.

Product section

Patch Manager

Resolution

Determine if the error occurs while running a task or launching the Patch Manager Admin Console.

Error displays while running a task 

  1. Log in to the Patch Manager Admin Console as an administrator. 
  2. Expand Patch Manager System Configuration > Patch Manager Servers and select Application Servers.
  3. Select the application server role assigned as the Primary Application Server. 
  4. Click the Patch Manager Server Wizard in the Actions pane.
  5. Select Edit an existing Patch Manager Server's configuration settings and click Next.
  6. Select the Primary Application Server from the Server Name drop-down menu and click Next.
  7. Make sure the Include this Patch Manager server in the default round-robin pool check box is selected, and click Next.
  8. Click Finish.
  9. Repeat the task again that generated the error.

Error displays when launching the Patch Manager Admin Console 

If the error was after applying MS Security KB patches, identify the patch and uninstall it. If that's not an option, then follow the rest of the steps below:

  1. Download a copy of Patch Manager from the Customer Portal. 
  2. Extract and run the installer on the Patch Manager server.
  3. Select and run the option to repair Patch Manager. 
    The installer reviews and repairs your current configuration. No user intervention is required. 
  4. Click Next through the Repair and complete the repair.
  5. When completed, open the Patch Manager Admin Console and ensure the error does not display in the console.

If you continue to have the same error, then log a ticket with Solarwinds Support.