Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Patch Manager > Top 10 Patch Manager customer issues

Top 10 Patch Manager customer issues

Updated February 17th, 2017

Overview

A list of the most frequent issues customers have with Patch Manager

Environment

SolarWinds Patch Manager

Detail

Notes On Issue 1:  Post Installation Deployment Guide

Covers steps for:

  • Adding WSUS
  • Configuring Inventory
  • Server Publishing Wizard
  • GPO configuration
  • Catalog and Synchronization

Notes On Issue 2: 0x800b0109 when attempting to deploy an update to a machine (typically seen from an endpoint device)

0x800b0109 when attempting to deploy an update to a machine (typically seen from an endpoint device)

Two Main Causes:
  • The WSUS Publishing certificate is not installed in the client system
  • The Group Policy setting Allow signed content from intranet Microsoft update service location is not enabled for this client system.

Notes On Issue 4:  Configuring Inventory and Running Reports

Two types of Patch Manager Reports requiring two types of Inventory:

  1. WSUS Reports - Information pertains to patching level and percentages of installed/failed/etc.  WSUS Inventory task updates this information.
  2. Configuration Management Reports - Information pertains to application installs (not Microsoft Patches) and other machine level census data (networking statistics, operating system information, files and regsitry).  Managed Computers Inventory populates this data in the Patch Manager Database.

Notes on Issue 5: Why is this update showing as Not Applicable?  I know it should be installed.

Why is this update showing as Not Applicable?  I know it should be installed.
  • This is a failure of the rules defined in the package – either the rule was made incorrectly or (and much more likely) the computer really is Not Applicable based upon either the Prerequisite or Applicability Rules evaluating as False.

See also:

Notes on Issue 6: Access Denied Issues

Additional configuration worth checking:

UAC (WMI can also raise these issues)
  • Use BUILT IN local Administrator account or disable UAC.
  • This can manifest itself in a number of ways – most commonly “access denied” or ““request for principal permission failed”

Notes on Issue 7: Invalid namespace when attempting to use WSUS Server Publishing Wizard/Verification Wizard 

Invalid namespace when attempting to use WSUS Server Publishing Wizard/Verification Wizard (can also be related to error 6 Access Denied Issues)

Notes on Issue 8: EminentWare Data Grid Server service not started - RPC error.

When launching the Administrative console for Patch Manager you may get an RPC error:

 

This relates to the EminentWare Data Grid Server service not being started.  Try to start the service, if you get an error, proceed below:

  • Error 1064 is common whenever there are changes to the service account running the Eminentware DataGrid Serivce. 
  • Error 1053 is common when there are issues connecting to the SQL database (permissions, networking, services on the server, configuration, etc).

Notes on Issue 9:  Unable to manage remote clients (networking issues)

If the task errors out the status will typically contain details as to the issue.  For ground up troubleshooting steps:

  1. Be sure you can ping from the Patch Manager Server to the client machine.
  2. Check for firewalls blocking ports:  Windows, A/V, physical, others
  3. Check Credential Ring for Domain Admin account
  4. wbemtest to verify general WMI connectivity.
  5. Verify the SolarWinds WMI providers are installed and match the Patch Manager server version.

Notes on Issue 10: API Mismatch

Two primary causes:

  1. Patching level mismatch.  During publishing if you select the option for "Verify WSUS version compatibility and required signing certificate is distributed" it will show the client and server API mismatch such as version 6.3.XXXX versus 6.3.YYYY.  If that is the case you will need to make sure that the Patch Manager and WSUS servers have the latest Microsoft updates.  If you see a 3.X API version versus a 6.X version you will need to review option 2 below.
  2. Operating System mismatch (example:  Patch Manager is on a 2012 server and WSUS is on a 2008 server).  During publishing if you select the option for "Verify WSUS version compatibility and required signing certificate is distributed" it will show the client and server API mismatch such as version 3.X API version versus a 6.X version you will need to install an Automation Server role or otherwise resolve the OS mismatch.

 

Last modified

Tags

Classifications

Public