I have one 2016 server that is running the 2.42 version of the powershell client and it's intermittently returning nothing for the svcs check, so I get a blank section like below, which causes the service check to fail with no matching services.
[svcs] Name StartupType Status DisplayName
If I run it manually it works fine each time. It's happening intermittently - anyone had this before and know what to check? I have tried the 2.27 and 2.42 version of the client and it's happening on both. It's likely related to this specific server but I can't see anything wrong and it has been working for a long time and reporting the services ok.
Regards,
Brandon
Hi
The svcs check is based on this Powershell command:
Get-WmiObject -Class Win32_Service | Sort-Object -Property Name
Occasionally I have seen issues when the WMI repository on the host becomes corrupt and this causes empty results. There used to be a decent Microsoft article on this but they've reorganised everything... I found this:
https://techcommunity.microsoft.com/t5/Ask-The-Performance-Team/WMI-Rebuildi... https://community.spiceworks.com/how_to/21413-rebuilding-the-wmi-repository
I have had some success in the past with the following commands:
winmgmt /verifyrepository
winmgmt /salvagerepository
There's also:
winmgmt /resetrepository
The articles linked above has more info and explanation, obviously, use at your own risk, make sure you have a backup / snapshot etc.
Zak
From: Xymon <xymon-bounces at xymon.com> On Behalf Of Brandon Dale Sent: Wednesday, 21 August 2019 03:04 To: xymon at xymon.com Subject: [External] [Xymon] powershell client blank service list
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.
I have one 2016 server that is running the 2.42 version of the powershell client and it's intermittently returning nothing for the svcs check, so I get a blank section like below, which causes the service check to fail with no matching services.
[svcs] Name StartupType Status DisplayName
If I run it manually it works fine each time. It's happening intermittently - anyone had this before and know what to check? I have tried the 2.27 and 2.42 version of the client and it's happening on both. It's likely related to this specific server but I can't see anything wrong and it has been working for a long time and reporting the services ok.
Regards,
Brandon
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
www.accenture.com
participants (2)
-
BDale@kitchengroup.com.au
-
zak.beck@accenture.com