Security Compliance

Certificate error message displays when logging in to Patch Manager

This article addresses a certificate error message that displays when you log in to Patch Manager. Error: Patch Manager Server Certificate Validation Private key is inaccessible for user account

First published date

10/30/2018 2:13 PM

Last published date

5/18/2023 10:55 AM

Overview

The following error message is displayed when you launch to Patch Manager MMC console, indicating that the Patch Manager certificate is not valid:
 

Warning:
"Patch Manager Server Certificate Validation Result: Failed"
Error: "Private key is inaccessible for user account '<Some_Account>'"
 

Product section

Patch Manager

Cause

  • The account used for the EminentWare Data Grid Server service cannot access the Patch Manager certificate.
  • After you execute setuphelper.exe to validate the Private key permissions, there is a mismatch in the Primary Application Server.
  • If you are using a service account, a GPO might policy might be blocking access to the Local Trusted Root store. (© 2018 /n Software, available at https://www.secureblackbox.com  obtained on November 21, 2018)

Resolution

1. Verify EminentWare Data Grid Server service account format
  1. Open Windows Services (services.msc)
  2. Locate EminentWare Data Grid Server service and righ click on it
  3. Select Properties > Logon tab, and make sure the account is entered in the NetBIOSDomain\username format if using a service account, and for the local account it should be .\username or ServerName\username
2. Verify Permissions on EminentWare certificates / private keys
  1. Open MMC Snap-in
  2. Select File > Add/Remove Snap-in > Certificate, and follow the wizard adding the Local Computer Store.
  3.  Locate EminentWare CA and EminentWare Server certificates in the Trusted Root CA store.
    1. Drag and drop the certificates into the Personal store.
    2. Right click each certificate and select All Tasks > Manage Private Keys.
    3. Verify that the EminentWare DataGrid Server service account has full permissions to the private key. Note, if using a service account the name would be username@domain which is fine here.
    4. Move certificates back to the Trusted Root CA store from the Personal store.
  4. If using a service account for Eminentware Service - a GPO policy might be blocking access to the Local Trusted root store (© 2019 n software, inc., available at www.secureblackbox.com, obtained on May 29, 2019) - use domain admin account to test this hypothesis. Refer to Change the account or password used for the Patch Manager service


If the above steps do not clear the error, perform the following steps:

  1. Open MMC console
  2. Click File > Add Remove/Snap-in > Add Certificates.
  3. Select Computer account and click Next.
  4. Click Finish, and then click OK.
  5. Go to Trusted Root Certification Authorities > Certificates.
  6. Delete EminentWare Certificates.
  7. Remove deviceID and CADeviceID from the HKLM\SOFTWARE\EminentWare\Data Grid Service registry
  8. Open SQL Management Studio and clear the record for PAS from dbo.gc_device and dbo.device for the Primary and Automation databases. <-- NOT NEGOTIABLE, NEEDS TO BE DONE

    If this step fails with an error, you may need to uninstall and reinstall Patch Manager.

  9. Run regedit.exe and go to HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service\Roles\Application\Data. Delete the MEkey and MPKey
  10. Open a command prompt as administrator > Navigate to X:\Program Files (x86)\SolarWinds\Patch Manager\Server where X is install drive > and run
    setuphelper /provisionserver /type primary
  11. Reset the Patch Manager password and all other users passwords in the credential area of the Patch Console.
    1. Go to Patch Manager System Configuration > Security and User Management.
    2. Select Credentials and then click Change Password.
  12. Go to Patch Manager System Configuration > Patch Manager Servers.
  13. Click Patch Manager Server Wizard.
  14. Register the Primary Server.
If an additional Automation server exists, re-provision the Automation Server.
  1. Run 
    mmc.exe
  2. Click File > Add Remove/Snap-in... Add Certificates.
  3. Select Computer account, and click Next.
  4. Click Finish, and then click OK.
  5. Go to Trusted Root Certification Authorities -> Certificates and delete EminentWare Certificates.
  6. Remove deviceID and CADeviceID from the HKLM\SOFTWARE\EminentWare\Data Grid Service registry
  7. Open SQL Management Studio. 
  8. Clear the record for Automation from dbo.gc_device and dbo.device on the Primary and Automation databases  <-- NOT NEGOTIABLE, NEEDS TO BE DONE
  9. Run:
    setuphelper /provisionserver /type automation
  10. Reset the password in Patch Manager.
    1. Go to Patch Manager System Configuration > Security and User Management.
    2. Select Credentials and then click Change Password.
  11. Go to Patch Manager System Configuration > Patch Manager Servers.
  12. Click Patch Manager Server Wizard.
  13. Register the Automation Server.

If this procedure does not resolve the issue and the service is running as a domain account, log in to the Primary Application Server to run the setup helper using that account.