What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Windows Updates Status (Powershell) sensor is failing with error 0x80244007

Votes:

0

My former working Windows Updates Status (Powershell) sensors fail with Exception calling "Search" with "1" argument(s): "Exception from HRESULT: 0x80244007". What is going on?

error error-messages prtg sensors windows-2012-r2 windows-update windows-update-status

Created on Jul 25, 2016 2:13:52 PM by Erhard Mikulik [Paessler Support]

Last change on Jul 25, 2016 4:52:40 PM by Gerald Schoch [Paessler Support]



3 Replies

Accepted Answer

Votes:

0

Important Information: This article is deprecated and is no longer updated. As of October 2023, PRTG no longer supports Windows Server 2012 R2. We recommend you use the most recent version of Windows Server.

This article applies to PRTG Network Monitor 16 or later

Fixing the Windows Updates Status (Powershell) Sensor after Windows 2012 R2 Update

If the Windows Updates Status (Powershell) sensor suddenly stops working and shows the error message Exception calling "Search" with "1" argument(s): "Exception from HRESULT: 0x80244007", the reason may be an update for Windows Server 2012 R2 (KB3159706).

This update enables ESD decryption provision in WSUS and has a number of manual post installation requirements. Once you have done these post install requirements, the WSUS service and so the sensor will work again.

Please follow the steps below to fulfill the post install requirements.

  1. Open an elevated Command Prompt window, and then run the following command (case sensitive, assume "C" as the system volume): "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing
  2. Select HTTP Activation under .NET Framework 4.5 Features in the Server Manager Add Roles and Features wizard.
  3. Restart the WSUS service.

(Thank you, Peter King!)

Created on Jul 25, 2016 2:24:44 PM by Erhard Mikulik [Paessler Support]

Last change on Nov 24, 2023 10:45:47 AM by Jacqueline Conforti [Paessler Support]



Votes:

0

I'm getting the above error on a group of non-wsus servers. These are newly installed sensors. I checked on one in particular and it is Server 2012 R2 that is used for security cams. There is no KB3159706 installed. Is there a fix/work around for this?

Created on Feb 24, 2017 5:19:42 PM



Votes:

0

Hi bendu,

What happens when you run an updatecheck manually on the affected hosts? What you get in the sensor is basically the same you would get when checking updates manually, which is in the end an issue on the operating system in this case. Are you sure there's no WSUS involved? I'm just asking, because the error is usually only thrown with WSUS involved. If you can't get around it, your best option would be to contact Microsoft about it I'm afraid.

Kind regards,

Erhard

Created on Feb 27, 2017 8:16:34 AM by Erhard Mikulik [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.