Submit a ticketCall us
Home > Success Center > Patch Manager > Patch Manager Documentation > Patch Manager Getting Started Guide > Troubleshoot SolarWinds Patch Manager

Troubleshoot SolarWinds Patch Manager

Table of contents
No headers
Patch Manager Getting Started Home

Last Updated: March 9, 2017

This section provides basic troubleshooting procedures for SolarWinds Patch Manager.  See Patch Manager Diagnostics for details about running the SolarWinds Patch Manager Full Diagnostics utility.

 

Issue How to troubleshoot
Error code 1064: could not start the EminentWare Data Grid Server Service See Troubleshoot Patch Manager error 1064 for details.
HTTP status 401 error when connecting to a WSUS server

This error can occur when you connect to a WSUS server from the Patch Manager server.

See Troubleshoot HTTP status 401 errors in Patch Manager for details.

Access Denied error when you connect SolarWinds Patch Manager to a remote computer

This error can occur when you deploy updates to remote systems or execute other tasks on a remote computer, such as opening Computer Explorer.

See Troubleshoot Access Denied Errors in Patch Manager for details.

Timeout error when you execute an Update Services task

Timeout issues can be caused by an unhealthy update server.

See Troubleshooting Timeout Errors in Patch Manager for details.

Invalid name space error from the SolarWinds Patch Manager server or managed systems

The Patch Manager server can generate an Invalid namespace error when User Account Control (UAC) prevents the server from communicating with the WSUS server. Managed clients can also receive this error when WMI Providers are not installed on these systems.

See Troubleshoot Invalid Namespace Errors - server or managed clients for details.

Error message stating that you exceeded the allowed license count

SolarWinds licenses Patch Manager according to the number of managed systems. Managed systems include all WSUS, ConfigMgr (SCCM), Patch Manager servers, as well as all managed clients.

The Primary Application Server (PAS) calculates the number of managed systems using the Managed Computers and Task History nodes located in the Patch Manager menu.

See Patch Manager Console: Exceeding Allowed License Count for details.

Error when performing an Advanced install with Microsoft® SQL Server 2012

The SQL Server name was not entered correctly during the installation.

See Error when installing Patch Manager on Microsoft SQL Server 2008 or 2012 for details.

API Mismatch error

This error occurs when Patch Manager servers are not running identical Microsoft Windows Server® operating systems.

If Windows Server Update Services (WSUS) is configured on a separate system with a different Windows Server operating system, install and enable the Automation Server role on that server to translate the API communications between the WSUS server and the Primary Application Server.

Incompatible installation type error

The Patch Manager installer does not support an installation on Web Only versions of Orion.

See Error: Incompatible installation type found for details.

Troubleshooting Microsoft installer error messages and failures

When you deploy a Microsoft Installer (MSI) package and the installation fails, troubleshoot the issue at the installer lever. For example, you can run the installer from the command line or troubleshoot MSI logging.

See Troubleshooting Microsoft Installer Error Message and Failures for details.

Troubleshooting WMI connections

When you target a remote system for a Managed Computer Inventory task, Patch Manager displays that system in the Enterprise > Managed Computers node.

Select a system in the center pane of this view to see useful information about the most recent WMI connection attempt.

 

Last modified

Tags

Classifications

Public