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
Last published date
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
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
- Open Windows Services (services.msc)
- Locate EminentWare Data Grid Server service and righ click on it
- 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
- Open MMC Snap-in
- Select File > Add/Remove Snap-in > Certificate, and follow the wizard adding the Local Computer Store.
- Locate EminentWare CA and EminentWare Server certificates in the Trusted Root CA store.
- Drag and drop the certificates into the Personal store.
- Right click each certificate and select All Tasks > Manage Private Keys.
- 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.
- Move certificates back to the Trusted Root CA store from the Personal store.
- 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:
- Open MMC console
- Click File > Add Remove/Snap-in > Add Certificates.
- Select Computer account and click Next.
- Click Finish, and then click OK.
- Go to Trusted Root Certification Authorities > Certificates.
- Delete EminentWare Certificates.
- Remove
deviceIDandCADeviceIDfrom theHKLM\SOFTWARE\EminentWare\Data Grid Serviceregistry - Open SQL Management Studio and clear the record for PAS from
dbo.gc_deviceanddbo.devicefor the Primary and Automation databases. <-- NOT NEGOTIABLE, NEEDS TO BE DONEIf this step fails with an error, you may need to uninstall and reinstall Patch Manager.
- Run regedit.exe and go to
HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service\Roles\Application\Data. Delete theMEkeyandMPKey - 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
- Reset the Patch Manager password and all other users passwords in the credential area of the Patch Console.
- Go to Patch Manager System Configuration > Security and User Management.
- Select Credentials and then click Change Password.
- Go to Patch Manager System Configuration > Patch Manager Servers.
- Click Patch Manager Server Wizard.
- Register the Primary Server.
- Run
mmc.exe
- Click File > Add Remove/Snap-in... Add Certificates.
- Select Computer account, and click Next.
- Click Finish, and then click OK.
- Go to Trusted Root Certification Authorities -> Certificates and delete EminentWare Certificates.
- Remove
deviceIDandCADeviceIDfrom theHKLM\SOFTWARE\EminentWare\Data Grid Serviceregistry - Open SQL Management Studio.
- Clear the record for Automation from
dbo.gc_deviceanddbo.deviceon the Primary and Automation databases <-- NOT NEGOTIABLE, NEEDS TO BE DONE - Run:
setuphelper /provisionserver /type automation
- Reset the password in Patch Manager.
- Go to Patch Manager System Configuration > Security and User Management.
- Select Credentials and then click Change Password.
- Go to Patch Manager System Configuration > Patch Manager Servers.
- Click Patch Manager Server Wizard.
- 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.