What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Sensor Windows updates error PE205

Votes:

0

Your Vote:

Up

Down

I have configured the windows update sensor for our probe server. It is returning the error "Could not retrieve update data. Please make sure your WSUS is configured correctly. (code: PE205)". I have rebooted the server. .NET is installed.

Server is Windows Server 2012R2. Other servers have the same sensor and are running without errors.

I have recreated the sensor, but still get this error.

How do i troubleshoot this?

pe205 updates windows windows-update-status windowsupdate wsus

Created on Aug 29, 2017 9:35:29 AM by  rajeevthakoerdajal (0) 1



13 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

Do you have another probe which is in the same network as the probe where the error is displayed? If so, try to create a new device with the IP address of the other remote probe and add the Windows Update Status to this device. Does the sensor work?

Best regards, Felix

Created on Aug 30, 2017 12:04:56 PM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Felix,

No, there is only 1 probe in this network.

Regards, Rajeev

Created on Aug 31, 2017 7:26:25 AM by  rajeevthakoerdajal (0) 1



Votes:

0

Your Vote:

Up

Down

Hello Rajeev,

We are currently investigating the issue to provide a fix. PRTG administrators will automatically be informed as soon as a new version is available. Please bear with us.

Best regards, Felix

Created on Aug 31, 2017 8:27:42 AM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Same error in our probe.

Problem on 3 Servers.

Windows 2008 Server 2 * Windows 2012 Server

Problems came up after switching to a new wsus. 20 others windows 2008/2012/2016 servers are working fine.

Created on Oct 8, 2017 12:36:23 PM by  Andre238 (0)



Votes:

0

Your Vote:

Up

Down

Andre,

This issue should be resolved within the latest version of PRTG. Please update and see if the problems are resolved.

Best, Felix

Created on Oct 8, 2017 2:23:17 PM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I get the same error after upgrading/changing our wsus server.

" Could not retrieve update data. Please make sure your WSUS is configured correctly. (code: PE205) "

I just upgraded our PRTG to the latest version Currently Installed Version 17.4.35.3326+ Tried to add the sensor again, but still get the same error.

This is the error log from the sensor.

2017-11-20T09:47:32.0957324+01:00 _-^-_ ### Entering Remote Connection to PS
2017-11-20T09:47:32.1167333+01:00 _-^-_ ### Remote Connection to PS succeeded
2017-11-20T09:47:32.5357431+01:00 _-^-_ ### Runspace Open
2017-11-20T09:47:32.8227552+01:00 _-^-_ ### Starting Check for Winupdate Numbers
2017-11-20T09:47:32.8237650+01:00 _-^-_ ### Before Running Script
2017-11-20T09:47:32.8237650+01:00 _-^-_ ### Script: $searcher = (New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher();$searcher.Search("Type='Software'").Updates | Sort-Object -Property Dates -Descending | ft -autosize IsInstalled, MsrcSeverity, IsHidden
2017-11-20T09:47:35.5640720+01:00 _-^-_ ### Script was executed, showing results: 
2017-11-20T09:47:35.5640720+01:00 _-^-_ ### Result Nr: 0:
2017-11-20T09:47:35.5640720+01:00 _-^-_ 
2017-11-20T09:47:35.5640720+01:00 _-^-_ ### Finished writing results
2017-11-20T09:47:35.5640720+01:00 _-^-_ ### Script Result lower than 3 elements, aborting

Any update on the problem.

Best Regards Stefan

Created on Nov 20, 2017 9:05:31 AM by  StefanK (0)

Last change on Nov 20, 2017 9:43:31 AM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Stefan,

Please log onto the host where the probe is installed from which PRTG sends the requests. Copy and paste this command into a PowerShell console (replace the host name in the first line by the address of the host where the sensor does not work):

Enter-PSSession -ComputerName NameOfTheTargetHost

$exectime = [System.Diagnostics.Stopwatch]::StartNew()

$searcher = (New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher();$searcher.Search("Type='Software'").Updates | Sort-Object -Property Dates -Descending | ft -autosize IsInstalled, MsrcSeverity, Title

((New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher()).Search("Type='Software'")

((New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher()).Search("Type='Software'").Updates

$exectime.Stop()

Please forward a screenshot of the results you receive. Please note that it might take some time until the result is displayed.

Best regards, Felix

Created on Nov 20, 2017 9:49:19 AM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Here is the Output from Powershell

PS C:\Windows\system32> Enter-PSSession -ComputerName Server01.domain.local

[Server01.domain.local]: PS C:\Users\adminuser\Documents>

[Server01.domain.local]: PS C:\Users\adminuser\Documents> $exectime = [System.Diagnostics.Stopwatch]::StartNew()

[Server01.domain.local]: PS C:\Users\adminuser\Documents>

[Server01.domain.local]: PS C:\Users\adminuser\Documents> $searcher = (New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher();$searcher.Search("Type='Software'").Updates | Sort-Object -Propert
y Dates -Descending | ft -autosize IsInstalled, MsrcSeverity, Title

[Server01.domain.local]: PS C:\Users\adminuser\Documents>

[Server01.domain.local]: PS C:\Users\adminuser\Documents> ((New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher()).Search("Type='Software'")

                                       ResultCode RootCategories                                    Updates                                           Warnings
                                       ---------- --------------                                    -------                                           --------
                                                2 System.__ComObject                                System.__ComObject                                System.__ComObject


[Server01.domain.local]: PS C:\Users\adminuser\Documents>

[Server01.domain.local]: PS C:\Users\adminuser\Documents> ((New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher()).Search("Type='Software'").Updates
[Server01.domain.local]: PS C:\Users\adminuser\Documents>

[Server01.domain.local]: PS C:\Users\adminuser\Documents> $exectime.Stop()

[Server01.domain.local]: PS C:\Users\adminuser\Documents>

Best Regards Stefan

Created on Nov 20, 2017 11:12:33 AM by  StefanK (0)

Last change on Nov 21, 2017 8:50:49 AM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Stefan,

According to the results, the PowerShell command misses some results, did you copy the code into the console at once, or line by line? If it was passed line by line, try to paste it completely at once.

We also encountered one very similar case where the automatic update of Windows did not work at all on the target host. Does the Windows feature display the open update if you open it via Windows?

Best regards, Felix

Created on Nov 21, 2017 8:58:06 AM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I did some testing, and almost all my servers, didn't give any output of the powershell script.

They I found 2 that it worked on, the ones it stopped working on had just got an agent for SCCM installed, instead of our old WSUS server. and the 2 that the script worked on, had not.

Windows update works fine on the servers, but the update history is empty, I tried to install and update, and it got in the history fine, but still no output from the powershell script.

Do you know of any issues with SCCM and the windows update sensor.

Created on Nov 22, 2017 8:06:28 AM by  StefanK (0)



Votes:

0

Your Vote:

Up

Down

Yep, SCCM based update distribution is not supported by the sensor I'm afraid :(


Kind regards,
Tech Support Team

Created on Nov 23, 2017 3:16:35 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello, i have same issue.

did all things but no sucess.

There is result powershell scritpt.

i'm not upgrade to v18 yet.

"Exception calling "Search" with "1" argument(s): "Exception from HRESULT: 0x8024401F"
At line:7 char:1
+ $searcher.Search("Type='Software'").Updates | Sort-Object -Property Dates -Desce ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ComMethodTargetInvocation
 
Exception calling "Search" with "1" argument(s): "Exception from HRESULT: 0x8024401F"
At line:9 char:1
+ ((New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher()).Search ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ComMethodTargetInvocation
 
Exception calling "Search" with "1" argument(s): "Exception from HRESULT: 0x8024401F"
At line:11 char:1
+ ((New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher()).Search ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ComMethodTargetInvocation"

What else can I do?

Created on May 18, 2018 4:49:01 PM by  francisgoliveira (0) 1

Last change on May 21, 2018 7:38:32 AM by  Luciano Lingnau [Paessler]



Votes:

0

Your Vote:

Up

Down

Version 18 will probably error out as well. Are you able to install any updates on the host or are there non available?


Kind regards,
Stephan Linke, Tech Support Team

Created on May 21, 2018 7:49:38 AM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


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.