Security Compliance

Invalid Namespace error when publishing or accessing the WSUS server in Patch Manager

This article addresses an error that displays in Patch Manager when running a task. Patch Manager uses two different methods for communication with Windows clients. WMI Providers and Patch Manager agents.

First published date

10/17/2018 7:12 PM

Last published date

3/19/2025 4:13 PM

Overview

In order for Patch Manager to communicate with the Windows Clients, it must have Client components installed which is either using WMI protocols or a Patch Manager agent.
WMI protocols use a dynamic port range and the full range must be open, or you run the risk of communication failures. WMI port range is 1024 to 65535.
The other form of communication Patch Manager can use is a Patch Manager agent which needs port 4092 open bidirectional. Below are some examples of errors indicating a PM to a windows client issue. 

Status: Failure
Message: InvalidNamespace Invalid Namespace
Status: PartialSuccess
Message: Operation on root failed. Access is denied


 

The MAC address retrieval using ARP resolution was not attempted for 10.9.10.15 because the ICMP ping failed.

Unable to retrieve NetBIOS domain name and computer name.

Successfully connected to the Microsoft Endpoint Mapper (Port 135)

Successfully connected to direct hosting NetBIOS over TCP-IP port 445 which is required for 'File and Print Sharing'

The computer (xyzmachine.domain.com) does not have the EminentWare WMI Providers installed.

Message: Invalid namespace

Successfully connected to WMI and retrieved operating and computer system information.SolarWinds Provider Required: True

Microsoft WMI Redistributable Required: False

Provisioning SolarWinds WMI Providers failed. Reason: handleremoteinstallation failed. Invalid Signature. ewException caught: [remoteinstallationclient::pushpackage failed. Invalid Signature. ewException caught: [remoteinstallationclient::pushfilecontent::pushcontent failed. Invalid Signature.], File: Remote Installation Client.cpp, Line: 1720 ], File: remote installation client cinterfaceimpl.cpp, Line: 427

Provisioning SolarWinds WMI Providers failed. Reason: handleremoteinstallation failed. Invalid Signature. ewException caught: [remoteinstallationclient::pushpackage failed. Invalid Signature. ewException caught: [remoteinstallationclient::pushfilecontent::pushcontent failed. Invalid Signature.], File: Remote Installation Client.cpp, Line: 1720 ], File: remote installation client cinterfaceimpl.cpp, Line: 427

Product section

Patch Manager

Cause

SolarWinds Client Components are not installed on the Windows client 
or the WMI port's full dynamic range is not open. 

Resolution

Manually install the WMI providers as per steps below:

  1. Log in to the Patch Manager server (Primary Application Server). 
  2. Navigate to:

    <PatchManager Install Folder>\Server\packages\EminentWare

    The installation folder should be located at:

    C:\\Program Files\SolarWinds\Patch Manager\Server\packages\EminentWare

  3. Copy the wmiproviders_version_number.exe file to the WSUS server.
  4. Run the installer on the WSUS server.

OR
You can create a WMI Providers WSUS installer package. 
1. Click on the WSUS Name on the left panel.
2 In the right actions panel click on deploy client components.
3. install and repair client components.
image.png
4. Install WMI providers
image.png

5 Create a WSUS installer package 
image.png
6. Click Finish.
Publish the newly created WMI providers package.
1. Expand Administration and Reporting. 
2 Expand Software publishing>SolarWinds Inc. Packages.
4 Publish the SolarWinds WMI providers 
image.png



Use Offline deployment method to deploy PM agents