Troubleshoot Patch Manager
This section provides basic troubleshooting procedures for Patch Manager. See Patch Manager Logging and Troubleshooting for basic troubleshooting steps you can use in your Patch Manager deployment. See Patch Manager Diagnostics for details about running the Patch Manager Full Diagnostics utility.
|Issue||How to troubleshoot and resolve|
|Unable to retrieve the Update Server information||
See Patch Manager cannot retrieve the Update Server information for details.
Drive consuming too much space on the WSUS server hosting WSUS content
WSUS views display inaccurate information
WSUS connection timeout errors
These issues occur when the WSUS database or the disk storing WSUS content is full. As a result, the Patch Manager Web Console can timeout when you select any WSUS view.
To resolve these issues, use the Server Cleanup Wizard to remove all unnecessary updates based on rules. This procedure will free up space on your disk and help your WSUS server run at optimal performance.
See The complete guide to Microsoft WSUS and Configuration Manager SUP maintenance on the Microsoft Support website for additional methods to maintain your WSUS server.
|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 HTTP status 401 error when testing the WSUS connection to Patch Manager for details.|
|Access Denied error when you connect 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 Patch Manager server or managed systems||The Patch Manager server can generate an
|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, and 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 License Count exceeded error in Patch Manager 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.|