Security Compliance

WSUS API Mismatch error in Patch Manager

This article describes how to troubleshoot WSUS API Mismatch error that is displayed in the SolarWinds Patch Manager MMC Console.

First published date

10/17/2018 10:16 PM

Last published date

3/31/2022 2:59 AM

Overview

When you try to publish updates to any managed computers, an API Mismatch error might display in the SolarWinds Admin Console.

This error is more common if PM and WSUS installed on two separate servers with different OS versions. In some cases it is also seen in setups where the the servers have same OS version as well.

Product section

Patch Manager

Cause

https://thwack.solarwinds.com/resources/b/product-blog/posts/patch-manager-architecture---deploying-automation-role-servers WSUS server and the server hosting the Primary Application Server (PAS) are running different Windows Server operating system versions.
One of the Servers missing a WSUS related patch

Resolution

For cause 2: ensure the two server have same WSUS specific patches installed. For example, in one case KB4484071 was installed on WSUS server but not on Patch manager - both running Server 2008 R2.

For cause 1: In order to resolve this specific issue an Automation Server must be installed on WSUS servers that do not have same Windows operating system as the Primary Application Server (PAS). During the Install and configure an Automation Server for WSUS of the Automation Server on the WSUS, the server will be automatically provisioned with the Automation Server role.

Post Automation Server Installation Steps(optional)

To check that the correct provisioning has occurred open regedit.exe on the WSUS server and go to: HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service\Roles\Automation
Check to see if the Enabled DWORD_REG is set to 0x00000001 (1)
Go to the Patch Manager Console and confirm this:
Patch Manager(Console)>Patch Manager System Configuration>Patch Manager Servers>Management Servers>Automation Server Monitoring(tab)
If at this point you do not see that the server provisioning is set correctly to be an Automation Server uninstall Patch Manager installation on the WSUS and go back through the installation steps for setting up an Automation Server

Decide whether or not Automation Routing Rules are necessary

Automation Routing Rules are used to control which server is committing the action. If routing rules are not in place, the default round-robin will control where the actions are being executed from. In the further reading section below, there are more details on how these alternate roles work and how they can be controlled using the routing rules.

Further Reading

Automation servers can be set up for more than this purpose, further reading on additional Automation Server Roles can be found here:

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.