Forum Discussion

Karl-WE's avatar
Karl-WE
MVP
Nov 06, 2023

ISSUE: Server Manager remote management error for clustered servers

Dear Windows Server Insider Team,    After long puzzles someone finally found a solution that Windows Server 2022 and vNext will appear "online" with no errors in Server Manager.   Warning: do no...
clustering
general
Hyper-V
management
DB2024's avatar
DB2024
Copper Contributor
Jan 04, 2024

Christian_Feuerstein  Here is the warning from Microsoft-Windows-ServerManager-DeploymentProvider/Operational:

Generic failure querying the localized name for channel: Microsoft-Windows-Kernel-IoTrace/Diagnostic [hResult = Function failed during execution., hLastResult = The instance name passed was not recognized as valid by a WMI data provider.].

 

I get a similar error when I go to the Microsoft/Windows/Kernel-IoTrace/Diagnostic log in Event Viewer:

Event Viewer cannot open the event log or custom view. Verify that Event Log service is running or query is too long. The instance name passed was not recognized as valid by a WMI data provider. (4201)

I also get the same WMI error referring to the Kernel-IoTrace/Diagnostic log when I go to the Administrative Events Custom View in Event Viewer.

Thanks.

Christian_Feuerstein's avatar
Christian_Feuerstein
Copper Contributor
Jan 08, 2024
That looks like the same error and I suspect that it is still the permissions that are causing the problem. Since I myself do not work with HCI but only with a HyperV Cluster 2022, it could theoretically be that the nodes are actually making requests here and therefore need to be added to the permission group in addition to the cluster object. Could you try that?
  • DB2024's avatar
    DB2024
    Copper Contributor
    Jan 08, 2024

    Christian_FeuersteinThanks for the reply. I have already added each host to its Event Log Viewer group and it didn't help. Did you mean add each host to all hosts' Event Log Viewer groups? I'm not working with HCI either, just Hyper-V on Server 2022.

    • Voon_Kim_Heng's avatar
      Voon_Kim_Heng
      Copper Contributor
      Jan 12, 2024
      Hi all. had tried above references, then saw this post then I follow the solution.
      https://www.checkyourlogs.net/fixed-s2d-cluster-data-retrieval-failures-occurred-error/
      5. According to this, the WS-Management Service has a packet limit by default. Run the following cmdlets to fix this error.
      Get-WSManInstance -ResourceURI winrm/config
      Set-WSManInstance -ResourceURI winrm/config -ValueSet @{MaxEnvelopeSizekb = “700”}
      6.Restarted the Service.
      This solve the "DATA RETRIEVAL FAILURES OCCURRED ERROR"
      • DB2024's avatar
        DB2024
        Copper Contributor
        Jan 15, 2024
        Hello. Thanks for the reply, but that fix is for a different issue than the one we're seeing.

        The error that is fixed by changing the WMI packet size is something like "Configuration refresh failed with the following error: The WS-Management service cannot process the request. The computed response packet size (517916) exceeds the maximum envelope size that is allowed (512000)." See https://blog.expta.com/2022/11/fix-for-online-data-retrieval-failures.html as an example.

Resources