windows server is failing with this error

ServiceNow_111 · yesterday

During discovery, the following error was observed:

Error during execution of Windows command:
executeQuery -Namespace Root\MSCluster -Query "SELECT GroupComponent, PartComponent FROM MSCluster_ClusterToResource"

The command timed out after 300 seconds while executing:

$tmpDir = getTempDirectory -subdirectory 'OnpremDiscoPROD' -serviceName 'snc_mid_OnpremDiscoPROD' -useSecureTemp $true

The Windows timeout/connection failure count reached 3, while the allowable failure threshold is 2. As a result, the pattern execution was terminated.

We performed the requested validations on the affected Windows servers using the following query:

Get-CimInstance -Namespace root\MSCluster -ClassName MSCluster_ClusterToResource

During validation, we found that the ClusSvc (Cluster Service) is not present, and the root\MSCluster namespace is unavailable, returning an "Invalid namespace" error. However, normal WMI functionality was verified successfully using the root\CIMV2 namespace and the Win32_OperatingSystem class.

Since these target servers are not configured as Windows Failover Cluster nodes, the MSCluster namespace does not exist on them.

Additionally, the remaining servers are being discovered successfully even when the Invalid Namespace error is encountered and ignored. However, only four servers are consistently failing discovery with this error.

Could you please advise what might be causing the issue on these