Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Patch Manager > Resolve server certificate errors in Patch Manager

Resolve server certificate errors in Patch Manager

Updated October 11, 2016


This article provides brief information and steps to resolve a certificate error.


Example error in MMC Console log file when accessing the PM console, even though the certs there with correct permissions. This error appeared when the customer moved EW DB to new SQL Instance.

2018/04/05 16:04:44:530 PID: 8744 TID:  4456 [ERROR] EminentWareRootScopeNode::ConnectToServer() failed. Message: ConsoleSession::FillOutSessionInfo() call failed. The root ca or the server cert couldnt be found

DataPortal_Insert method call failed


All Patch Manager versions



  1. Verify the Private Key permissions on the EminentWare CA and EminentWare Server certificate's private keys.
    1. Open the Microsoft Certificate Console (mmc) snap-in for the local computers certificate store. 
    2. Dragging and dropping the EminentWare CA and EminentWare Server certificates into the Personal store from the Trusted Root Publishers certificate store.
    3. Right-click on each cert in turn and selecting All Tasks->Manage Private Keys insure the EminentWare DataGrid Server service account has full control to the private key.
    4. Give the account full control and copy the updated cert back to the Trusted Root Publishers certificate store by dragging and dropping.
    5. If the permissions needed updating, verify if the the permission changes have helped, if not continue with the steps below.
  2. Insure the account configured to start the EminentWare DataGrid Server service is set in the form DOMAIN\AccountName.
  3. If the above steps haven't helped, run the following command on your server to re-create your certificates and repair the certificate private key file access control list: 

C:\Program Files\SolarWinds\Patch Manager\server\setuphelper.exe /provisionserver /type primary 

Last modified