This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Windows Update Monitoring - Days passed from last Windows Update randomly going up and down

mikedaves over 8 years ago

Hi,

I have a problem with the "Days passed from last Windows Update" monitor in the Windows Update Monitoring template. It randomly goes down, one server at a time, effecting between 2 and 25 servers. I have several hundred other monitors, that all work fine, only this one monitor is showing this behavior.

When I go to component status, I get the following error:

PowerShell script error. Scripting Error: Script does not contain the expected parameters or is improperly formatted. 'Statistic' missing.

Can you tell me how to troubleshoot and resolve the issue?

Thanks,

Mike

Top Replies

0 jeiband over 7 years ago

Did you ever get it fixed? I have the same problem!
Cancel
Vote Up 0 Vote Down

Cancel
0 nick.myers over 7 years ago

I also have the same issue. Can you let me know if this was ever fixed?
Thanks
Cancel
Vote Up 0 Vote Down

Cancel
0 osborne_graham over 7 years ago

Same... Anyone have any updates?
Cancel
Vote Up 0 Vote Down

Cancel
0 osborne_graham over 7 years ago

I've found the cause of the error - For some reason around 30 servers are returning null for $objSearcher.QueryHistory(0, 1) so $objEntry is then null causing "$d = $objEntry.Date" to also return null so when it tries to split what should be a date/time (for what appears to be an inelegant way of trimming whitespace) it causes the line to error out with "You cannot call a method on a null-valued expression". I'll look into this some more when I get time but this info might be enough for someone else to jump in with a resolution.
Cancel
Vote Up 0 Vote Down

Cancel
0 fewillia over 6 years ago in reply to osborne_graham

Having same issue? Any suggestions?
Cancel
Vote Up 0 Vote Down

Cancel
0 akash1309 over 5 years ago

Hi,
I have not yet found the fix, but for the windows days up time, you can use the Universal device poller to get the accurate data.
Let me know, if you need help, can share info.
Cancel
Vote Up 0 Vote Down

Cancel
0 jozsef.budahaz over 5 years ago

Hi,
I came across the very same issue in my lab,
I believe I found the root cause and may have a workaround for this issue.
It would be great to get some other feedback in case this helps..
1. Please edit the template
2. Edit the component monitor (Days passed from last Windows Update)
3. Find this line of code (Expand the template, click on Edit Script):
if ($res -eq "00.00.00")
4. Now replace it with this:
if ($res -eq "00:00:00")
5. Test the component again.
Please let me know how you get on and if all good, we shall request development to update this.
Thanks All!
Joe.
Cancel
Vote Up +1 Vote Down

Cancel
0 jimwatgt over 5 years ago in reply to jozsef.budahaz

That change cleared the error in my test case. I'm not sure if the data is correct, but at least it's not giving the missing statistic error.
Cancel
Vote Up 0 Vote Down

Cancel
0 jozsef.budahaz over 5 years ago in reply to jimwatgt

Hi, to explain the issue:
Updates installed today (Statistic output is NaN):
Run the script on the node itself and added extra line to display the returned value (returned value on 0 day is 00:00:00):
Modified the script to match the returned value (Statistic output is 0):
I hope it's explain.
Thanks
Joe
Cancel
Vote Up 0 Vote Down

Cancel
0 mhavens over 4 years ago

I just ran into this issue with Server 2019 OS.
if ($res[0] -eq "00.00.00" -Or $res[0] -eq "00:00:00" )
Change the 0 day check to the above, and it works for everything.
Cancel
Vote Up +1 Vote Down

Cancel