Меню

Data retrieval failures occurred ошибка

3 Replies

  • Author Supaplex

    mace

    Windows Server Expert

    • check
      120
      Best Answers
    • thumb_up
      966
      Helpful Votes

    Unfortunately, the Windows Server Manager has always been buggy, even more than other traditional RSAT tools. Currently, it gets slowly discontinued in favor of the new web-based Windows Admin Center https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/overview Opens a new window. Installing it doesn’t take a lot of time. Since it is pretty fresh, it also has some issues present but at least managing roles and features works like a charm. An excellent guide about how to install, configure, and use it can be found here https://www.starwindsoftware.com/blog/windows-admin-center-for-windows-server-2019-getting-started Opens a new window. I hope it helps you a bit.

    Personally, I always prefer Powershell to install new roles and features. The ability to install everything you need, including all the dependencies, within a single command, is just magnificent. And takes less time compared to ticking those damn checkboxes in the list.


    0 of 1 found this helpful
    thumb_up
    thumb_down

  • Thanks, Supaplex​. I would happily use any tool, but this issue seems to be breaking the entire Add/Remove Role or Features of the Server. 

    How can I test just listing out Role/Features in PowerShell? I google’d it but found a ton of info and nothing simple. 


    Was this post helpful?
    thumb_up
    thumb_down

  • FIXED — Solution found in this SE post: https://stackoverflow.com/questions/36293055/windows-server-2012-r2-error-server-manager-is-collecti… Opens a new window

    Open CMD prompt (not PS!) with Admin rights and execute this:

    Batchfile

    cd C:WindowsSystem32wbemAutoRecover

for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

    Anyone know what the second command does? Just curious. 


    Was this post helpful?
    thumb_up
    thumb_down

Источник

Hi,

Unfortunately, performing WMI repository autorecover did not help me and the error still appears in the server manager and in the event viewer when opening Administrative Events. I returned the reg key with the enabled option and reset the server. I did the procedure according to the instructions, but unfortunately the error still occurs. I also tried to reset the server after the procedure, but it didn’t help.

A strange thing appears in the log:

WARNING: File 01C0F3A81F9A4314BBA9813A02D602AA.mof does not contain #PRAGMA AUTORECOVER.

Here is the log:

Microsoft Windows [Version 10.0.20348.1129]
(c) Microsoft Corporation. All rights reserved.

C:Windowssystem32>cd wbem

C:WindowsSystem32wbem>cd AutoRecover

C:WindowsSystem32wbemAutoRecover>for /f %s in (‘dir /b *.mof *.mfl’) do mofcomp %s

C:WindowsSystem32wbemAutoRecover>mofcomp 00744A75F86D5BA0D35F673723E49EBE.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 00744A75F86D5BA0D35F673723E49EBE.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 01C0F3A81F9A4314BBA9813A02D602AA.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 01C0F3A81F9A4314BBA9813A02D602AA.mof
MOF file has been successfully parsed
Storing data in the repository…
WARNING: File 01C0F3A81F9A4314BBA9813A02D602AA.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 079AAE2A462B9E15D843B46ABA01B257.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 079AAE2A462B9E15D843B46ABA01B257.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 08C18351E9E713EB47A11790CA0CE94A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 08C18351E9E713EB47A11790CA0CE94A.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 0CF494C661F4CE4927C40F5293B1309C.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 0CF494C661F4CE4927C40F5293B1309C.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 0F9498A8C3A78092022C9CC49955C6EC.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 0F9498A8C3A78092022C9CC49955C6EC.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 135B74A698486C6F06BDC384690867B6.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 135B74A698486C6F06BDC384690867B6.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 15046DBDCBEEF92CCD2BEFEF67A544E2.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 15046DBDCBEEF92CCD2BEFEF67A544E2.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 1B054D14ED32B6C986A4B80A1971B507.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 1B054D14ED32B6C986A4B80A1971B507.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 1D554E50A17FD1E08ECF90A5936D29E4.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 1D554E50A17FD1E08ECF90A5936D29E4.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 1DE7BE7BA35D977F49656C02C66058FC.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 1DE7BE7BA35D977F49656C02C66058FC.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 21BD8E9B6A3575C7E6CFD05471F4DE86.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 21BD8E9B6A3575C7E6CFD05471F4DE86.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 26514409CC4910118B040726189DED3D.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 26514409CC4910118B040726189DED3D.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 270E6F495B767FBDF4DB07F5DE16055F.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 270E6F495B767FBDF4DB07F5DE16055F.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 2D291BC2C93E41CE963CDDECD5CEEDC9.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 2D291BC2C93E41CE963CDDECD5CEEDC9.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 2E6E576003AC48B631A669B2932BB1C2.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 2E6E576003AC48B631A669B2932BB1C2.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 343E2AF1057A8BA8148BB735067E817A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 343E2AF1057A8BA8148BB735067E817A.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 3A01647A9113490045B9D4AE10390941.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 3A01647A9113490045B9D4AE10390941.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 4232C9D6829B409B5D825D0F97ACEC63.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 4232C9D6829B409B5D825D0F97ACEC63.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 44BD58CF87D84E4D08B2223F1EDD24E4.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 44BD58CF87D84E4D08B2223F1EDD24E4.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 4D06958C26E8EE4ED93ADDC0E43A3DFB.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 4D06958C26E8EE4ED93ADDC0E43A3DFB.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 54BDD8DB6504771BB43BAAA596324930.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 54BDD8DB6504771BB43BAAA596324930.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 5B56FCB55A56653EDA41E8A7D5D36A32.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 5B56FCB55A56653EDA41E8A7D5D36A32.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 61D69B6E1564ACF7B6E32F6D0B951CF5.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 61D69B6E1564ACF7B6E32F6D0B951CF5.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 669532D3E0C12013ED00C40C8307310F.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 669532D3E0C12013ED00C40C8307310F.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 69D23F5E6BF4F0DA0498649351B6046D.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 69D23F5E6BF4F0DA0498649351B6046D.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 6EF6778A71129DDBCE093A02799E28DD.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 6EF6778A71129DDBCE093A02799E28DD.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 6FC2693FFECCC30FD2B0C42B0443B9C9.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 6FC2693FFECCC30FD2B0C42B0443B9C9.mof
MOF file has been successfully parsed
Storing data in the repository…
WARNING: File 6FC2693FFECCC30FD2B0C42B0443B9C9.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 7073EBB8E2F3C70E0FA1F650B7DEA970.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 7073EBB8E2F3C70E0FA1F650B7DEA970.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 7989C664815B7AF909AB221E34890DEA.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 7989C664815B7AF909AB221E34890DEA.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 7DFE8C6791931712E5E8C76E2B3612A6.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 7DFE8C6791931712E5E8C76E2B3612A6.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 7E9A06269FE9F368EE7F5DF6350AA315.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 7E9A06269FE9F368EE7F5DF6350AA315.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 85CE57E0C8E10DD2E6175DA8B8C40F48.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 85CE57E0C8E10DD2E6175DA8B8C40F48.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 8742AF6B78D6A2FC4AB9AC090C6E391E.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 8742AF6B78D6A2FC4AB9AC090C6E391E.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 88744D2A29102FC88ECF505DD2E984FC.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 88744D2A29102FC88ECF505DD2E984FC.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 88F6A2F38C8C6430B59F31477479C304.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 88F6A2F38C8C6430B59F31477479C304.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 8BA70471D298E2919940ACECA2CC9754.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 8BA70471D298E2919940ACECA2CC9754.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp 8E599464072F15C56474A50D8756349A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 8E599464072F15C56474A50D8756349A.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp A359F193EB73A77290BA1CA931BC06CB.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: A359F193EB73A77290BA1CA931BC06CB.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp A5E01B1838C9AEEA0C0CC412768C8A01.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: A5E01B1838C9AEEA0C0CC412768C8A01.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp AC220A8791FC6D7B8E8F2B26C21FE74A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: AC220A8791FC6D7B8E8F2B26C21FE74A.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp ADC76C6473F1C3722A0A86C2A9AED340.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: ADC76C6473F1C3722A0A86C2A9AED340.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp AE3832D9BEFB84DEB5BB187912DF2345.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: AE3832D9BEFB84DEB5BB187912DF2345.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp B355992E8BD649C24023BB7FD49A4C6F.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: B355992E8BD649C24023BB7FD49A4C6F.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp B8B54A0F9FF06190F8DF8AFE871AD0BA.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: B8B54A0F9FF06190F8DF8AFE871AD0BA.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp C178855BCF87ACB74F467532808B7EA6.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: C178855BCF87ACB74F467532808B7EA6.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp C599AFA5A6F053BAD70179501868318E.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: C599AFA5A6F053BAD70179501868318E.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp C59FAE5604BA27360FE3C8145302C43C.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: C59FAE5604BA27360FE3C8145302C43C.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp C8463ECBE33BC240263A0B094E46D510.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: C8463ECBE33BC240263A0B094E46D510.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp D0A59D2AF9A904A77DC6E7C92B8A3E0C.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: D0A59D2AF9A904A77DC6E7C92B8A3E0C.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp D5D286F205A8518EDCCF33465D7869CD.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: D5D286F205A8518EDCCF33465D7869CD.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp D5D6BB480217F9DCEC357F57222DEE59.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: D5D6BB480217F9DCEC357F57222DEE59.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp D9B050B7A24E09624652E41AC4639DDE.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: D9B050B7A24E09624652E41AC4639DDE.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp DF66BF7FE8B151CD01B5A759CD88E60A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: DF66BF7FE8B151CD01B5A759CD88E60A.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp E449DF8E37B700427A984BAC1AD11EF0.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: E449DF8E37B700427A984BAC1AD11EF0.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp E64DEFC698F67BCC2EBDE5C8BB24CA93.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: E64DEFC698F67BCC2EBDE5C8BB24CA93.mof
MOF file has been successfully parsed
Storing data in the repository…
WARNING: File E64DEFC698F67BCC2EBDE5C8BB24CA93.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp E75B84BF30D37D54881678B1E35246BC.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: E75B84BF30D37D54881678B1E35246BC.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp ED57484AAC7475D8631352D817AB6A43.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: ED57484AAC7475D8631352D817AB6A43.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp F4F9B78B4B4537617EAF17FFC1BB4624.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: F4F9B78B4B4537617EAF17FFC1BB4624.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp F7D2F5DD6AD538F08A78FE75923B0C37.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: F7D2F5DD6AD538F08A78FE75923B0C37.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp F868406B4813AB4041346B98EFFA5DA7.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: F868406B4813AB4041346B98EFFA5DA7.mof
MOF file has been successfully parsed
Storing data in the repository…
WARNING: File F868406B4813AB4041346B98EFFA5DA7.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp FAB4FD1F41BAD00B53FE8A2B9DD19520.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: FAB4FD1F41BAD00B53FE8A2B9DD19520.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>mofcomp FBC22038FB1BD86499891CF935882F20.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: FBC22038FB1BD86499891CF935882F20.mof
MOF file has been successfully parsed
Storing data in the repository…
Done!

C:WindowsSystem32wbemAutoRecover>

Источник

  • Hi TParky,

    This error most time occur when the firewall configure incorrect, please try to disabled firewall on all this servers, then try again. This indicated the Server Manager cannot
    get event data from the target server. The user might not have access rights to the target server event log, or event log files might not contain valid data.

    For some roles and features (Hyper-V, Print and Document Services, AD LDS), this error can occur after installation, but before required post-installation configuration has
    been completed. The error is resolved after post-installation configuration is complete.

    This error can also occur if specific roles and features have been installed, but not yet configured. The following underlying error messages are examples of known cases where
    a role, role service, or feature requires post-installation configuration to clear the error.

    •Events from ‘Virtualization.Events.xml’ could not be enumerated. (This error is cleared after required post-installation configuration for Hyper-V is completed.)

     •Events from ‘PrintServices.Events.xml’ could not be enumerated. (This error is cleared after required post-installation configuration for Print and Document
    Services is completed.)

     •Events from ‘ADAM.Events.xml’ could not be enumerated. (This error might be cleared after required post-installation configuration for Active Directory Lightweight
    Directory Services is completed.)

    More information:

    Configure Remote Management in Server Manager

     http://technet.microsoft.com/en-us/library/hh921475.aspx

    Windows Server 2012 — Server Manager Troubleshooting Guide, Part II: Troubleshoot Manageability Status Errors in Server Manager

    http://social.technet.microsoft.com/wiki/contents/articles/13444.windows-server-2012-server-manager-troubleshooting-guide-part-ii-troubleshoot-manageability-status-errors-in-server-manager.aspx

    I’m glad to be of help to you!

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    • Предложено в качестве ответа

      6 мая 2015 г. 2:24

    • Помечено в качестве ответа
      Alex Lv
      11 мая 2015 г. 1:32

    • Источник

    I have a Windows Server 2012 Standard machine that serves as a DC, file server, and Hyper-V host. It has been in place for a handful of years and is running fine to my knowledge.

    The issue is, on the Server Manager dashboard, everything is red, erroring for ‘manageability’ with error «Online — Data retrieval failures occurred.» Task details for the server manage refresh states «The system cannot access one or more event logs because of insufficient access rights, file corruption, or other reasons.» Event log shows the following, varying for each role that throws the error:

    «Failed to query the results of bpa xpath: Microsoft/Windows/DHCPServer:$reports$$latestreport$Discovery.xml:$creationtime$. error: The system cannot find the file specified., last error: The system cannot find the path specified..»

    The client this server belongs to has a login to it, has seen the red, and wants it fixed.

    I’ve dug and dug, over 7 hours logged on my ticket for this, without a resolution. Most of what I find says to image the machine, or to delete a registry key regarding a ringtone which doesn’t exist on this server as is. I found a couple archived posts in this reddit with the same error, but no fix was posted.

    Any assistance is much appreciated. I’m not sure where else to turn at this point. Thanks!

    Источник

    Обновлено 03.06.2020

    rdpДобрый день! Уважаемые читатели и гости одного из крупнейших IT блогов России Pyatilistnik.org. В прошлый раз мы с вами рассмотрели удобного RDP клиента Remote Desktop Connection Manager, посмотрели его достоинства и недостатки. Сегодня я хочу опять вернуться к терминальным фермам и рассмотреть вот такую ошибку, которую вы можете увидеть при попытке зайти на RDS ферму, звучит она так «Выполняется оценка качества подключения«, после чего подключение отваливается. Давайте смотреть в чем дело и как это можно исправить.

    Ошибка «Выполняется оценка качества подключения» при попытке зайти на терминальную ферму

    И так, в одно прекрасное утро, начали поступать массовые жалобы от технической поддержки, что пользователи не могут подключиться к RDS ферме. Я сразу полез проверять наши терминалы. При попытке подключиться, люди видели вот такую картину. Долго висело подключение со статусом «Выполняется оценка качества подключения»

    Выполняется оценка качества подключения

    После чего попытка подключения прерывается и появляется ошибка из ряда:

    Компьютер не может подключиться к удаленному компьютеру, так как посреднику подключений не удалось проверить параметры файла RDP. Обратитесь за помощью к администратору сети

    Ошибка подключения RDP

    Алгоритм диагностики и устранения ошибки

    Первым делом я через команду ping проверил сетевую доступность своих серверов, с ними было все в порядке. Далее я открыл оснастку управления RDS фермой и посмотрел статусы всех серверов участвующих в ней. Я увидел много ошибок:

    Я увидел у одних статус «data retrieval failures occurred», у других статус «Target computer not accessible, где-то был статус «Cannot get role and feature data»

    data retrieval failures occurred

    Попытавшись открыть настройки RDS фермы, я получил вот такую ошибку:

    The server pool does not match the RD Connection Brokers that are in it. Errors: Cannot connect to any of the specified RD Connection Brokers servers. Ensure that at least one server is avaliable and that the Remote Desctop Management (rdms), RD Connection Broker (tssdis), or RemoteApp and Desctop Connection (tscpubrpc) service running

    Ошибка подключения к RDS брокерам

    Видя все это безобразие, я полез на свои брокеры подключений, напоминаю для этого нужно использовать ключ «/admin». Начав изучать логи Windows я обнаружил событие ID 2048.

    ID 2048: The Remote Desktop Connection Broker server detected that the database is not available and will notify all Remote Desktop Connection Broker plug-ins

    The Remote Desktop Connection Broker server detected that the database is not available and will notify all Remote Desktop Connection Broker plug-ins

    Тут все встало на свои места, пользователи видели ошибку «Выполняется оценка качества подключения» из-за того, что брокеры потеряли связь со своей базой данных. Напоминаю, что посмотреть настройки базы данных для отказоустойчивой RDS фермы, вам необходимо открыть окно «Выполнить» и ввести в нем:

    Открытие cliconfg.exe

    На вкладке «Alias» вы найдете имя сервера и параметры подключения к базе данных. Далее остается их только восстановить и вернуть работу вашей RDS ферме.

    Просмотр настроек базы данных Connection Brokers

    Дополнительные причины ошибки «Выполняется оценка качества подключения»

    • Из самых распространенных проблем, это наличие на вашем сервере, куда вы подключаетесь наличие программного продукта КриптоПРО версии 3.9, проблема там была в неком ГОСТ SSL, который предлагалось отключить или же полностью удалить КриптоПРО, с переходом на более свежую версию. Если нужно отключить ГОСТ SSL, то в реестре Windows нужно привести ключ cpksp вот к такому виду:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerCProPatchesSCHANNEL]
    «Image Dll»=»_schannel.dll»
    [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicescpksp]
    «Start»=dword:00000003

    Далее перезагрузить сервер, это обязательно.

    • Вторая проблема, это не работает или не отвечает ваш сервер лицензирования удаленных рабочих столов. В диспетчере сервера — ошибки службы лицензирования рабочих столов. Отсутствует сервер лицензирования. Устраняем проблему с лицензиями и радуемся
    • Еще бывает, что помогает выбор транспортных протоколов, давайте подробнее.  При подключении по RDP используются два транспортных протокола TCP/UDP. Фишка в том, чтобы оставить только TCP. Для этого создайте групповую политику или отредактируйте локальную на серверах подключений, вот по такому пути:

    Конфигурация компьютера — Административные шаблоны — Компоненты Windows — Службы удаленных рабочих столов — Узел сеансов удаленных рабочих столов — Подключения — Выбор транспортных протоколов — выбрать только TCP

    Потребуется перезагрузка или перезапуск служб RDP.

    Выбор транспортных протоколов RDP

    Этот параметр политики позволяет указать, какие протоколы можно использовать для доступа к данному серверу по протоколу RDP. Если вы включаете этот параметр политики, необходимо указать, хотите ли вы, чтобы протокол RDP использовал протокол UDP.

    Вы можете выбрать один из следующих вариантов: «Использовать UDP и TCP (по умолчанию)», «Использовать только TCP» или «Использовать либо UDP, либо TCP». Если вы выбираете вариант «Использовать либо UDP, либо TCP» и подключение UDP выполнено успешно, то большая часть трафика по протоколу RDP использует протокол UDP.

    Если подключение UDP не выполнено успешно или если вы выбираете вариант «Использовать только TCP», весь трафик по протоколу RDP использует протокол TCP.Если вы отключаете или не настраиваете этот параметр политики, RDP выбирает оптимальные протоколы для обеспечения наилучшего взаимодействия с пользователем.

    Я часто встречал ситуацию, что человек работает удаленно с дачи или еще более удаленного места, со своим мобильным интернетом, в следствии проблем со скоростью получал ошибку «Выполняется оценка качества подключения», где сразу начинал говорить, что ваша RDS ферма плохая. Пока ты ему докажешь, что дело в его мобильном интернете, пройдет не один десяток минут. Хорошо, что после RDP клиента восьмой версии, диагностировать стало проще, там появился индикатор, о подключении к клиенту удаленного рабочего стола (RDC).

    Вы найдете индикатор RDC вверху панели подключения, в верхней части любого полноэкранного подключения к удаленному рабочему столу. Индикатор отобразит от одной до четырех полос, которые суммируют задержку двустороннего соединения (RTT) и текущую полосу пропускания в простой для чтения иконке. Выглядит, это вот так.

    Качество подключения к удаленному компьютеру хорошее

    RDC индикатор

    Например, полный набор из четырех полос указывает, что задержка составляет менее 50 мс, а полоса пропускания превышает 10 Мбит/с. Когда полосок меньше, пользователь подключается с более высокой задержкой или с меньшей пропускной способностью.

    Пользователь также может щелкнуть значок индикатора, чтобы увидеть письменное описание качества своего соединения и узнать, пользуется ли он дополнительными преимуществами соединения на основе UDP.

    Качество подключения к удаленному компьютеру хорошее, протокол UDP включен

    RDC индикатор

    На этом у меня все, надеюсь, что мне удалось помочь вам решить проблему с подключением к вашей RDS ферме. С вами был Иван Семин, автор и создатель IT портала Pyatilistnik.org.

    Источник

    by
    ·

    Published December 19, 2013
    · Updated February 20, 2015

    windows-8

    Server Manager console is a great tool that I have tried to use on Windows 8 and now Windows 8.1 but I had connection issues.

    Once I have added couple of servers to manage via Server Manager console, during discovery I ran into the following errors:

    Online – Data retrieval failures occurred

    Once I have checked the details of this error message here’s what I got:

    %servername%: Configuration refresh failed with the following error: The metadata failded to be tetrieved from the server, due to the following error: The WinRM client received an HTTP status code of 502 from the remote WS-Management service.

    I should mention that I was using Server Manager console under domain admin rights. Although I was admin I have added my account to the WinRMRemoteWMIUsers_ group on the server, but without luck.

    After than I have tried with netsh command as this helped me once I got Store connection problems with Windows 8 and 8.1.

    I have run the following command:

    netsh winHTTP set proxy proxy-server=”http://%proxyname:port%” bypass-list=”%*.domainname%”

    After you run this command try to refresh Server Manager console on your machine and you should be able to connect and manage servers normally.

    If you still have issues, please post below and I’ll try to help.

    Источник

    RRS feed

    • Remove From My Forums

    locked

    Server Manager: Under Manageability — Online- Data retrieval failures occurred

    RRS feed

    • Question

    Answers

      • Marked as answer by
        Andy Qi
        Wednesday, February 12, 2014 1:47 AM

    All replies

    • Hello,<o:p></o:p>

      <o:p> </o:p>

      Thank you
      for posting your issue in the forum.<o:p></o:p>

      <o:p> </o:p>

      It seems
      like the issue is caused due to incorrectly setting GPP to collect Event Logs
      backup. <o:p></o:p>

      <o:p> </o:p>

      Important:
      The action plan below will modify the registry. However, serious
      problems might occur if you modify the registry incorrectly.       So please back up the registry before you modify it.
      Then, you can restore the registry if a problem occurs.<o:p></o:p>

           <o:p></o:p>

      After
      backing up the following registry key, please delete this AutoBakupLogFiles
      registry and refresh/close and open Server Manager.<o:p></o:p>

       <o:p></o:p>

      Name:
      AutoBackupLogFiles       <o:p></o:p>

      Location:

      HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesEventLogSecurity<o:p></o:p>

      <o:p> </o:p>

      Here is
      the article that gives more details on how to configure backing up event logs:<o:p></o:p>

       <o:p></o:p>

      msdn.microsoft.com/en-us/library/cc231247.aspx

      <o:p> </o:p>

      Best regards,<o:p></o:p>

      Sophia Sun<o:p></o:p>

    • Hi,

      How is everything going?

      Do you have any updates about the status of the issue? When you have time, please feel free to post this information here. Thanks for your cooperation.

      Regards,

    • please delete this AutoBakupLogFiles

      registry and refresh/close and open Server Manager


      HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesEventLogSecurity<o:p>

      There is no entry AutoBackupLogFiles on any machine, client or server using the Server Manager.

    • Hi,

      How is everything going?

      Do you have any updates about the status of the issue? When you have time, please feel free to post this information here. Thanks for your cooperation.

      Regards,

      Yes the issue still exists. I just did another upgrade from 2012 vl to 2012r2 vl and the problem is still happening.

      I did find out something interesting. Removing the GUI from the server and then re-installing it fixes the problem.

      Dism /online /disable-feature /featurename:ServerCore-FullServer

      Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer

      • Marked as answer by
        Andy Qi
        Tuesday, November 26, 2013 3:18 AM
      • Unmarked as answer by
        JC_3
        Tuesday, December 3, 2013 9:36 PM

    • Hi,

      How is everything going?

      Do you have any updates about the status of the issue? When you have time, please feel free to post this information here. Thanks for your cooperation.

      Regards,

      Yes the issue still exists. I just did another upgrade from 2012 vl to 2012r2 vl and the problem is still happening.

      I did find out something interesting. Removing the GUI from the server and then re-installing it fixes the problem.

      Dism /online /disable-feature /featurename:ServerCore-FullServer

      Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer

      As an update this worked 80% of the time. I still have several servers that are still reporting: Server Manager, All servers, Manageability column, «Online — Data retrieval failures occurred».

      • Marked as answer by
        Andy Qi
        Wednesday, February 12, 2014 1:47 AM

    • Hello,

      Just want to confirm the current situations.

      Please feel free to let us know if you need further assistance.

      Regards,

      Sophia Sun

      Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Hi,

      i had the exact same problem and the channel registry keys wasn’t the same as its mentioned on many forums . It varies on all machines so the general fix is below:

      Check in channel events in event viewer:

      Event viewer > Microsoft > Windows > servermanager-Managementprovider > Operational and check the warning messages it generates at the time of server manager refresh.

      eg:    Generic failure querying the localized name for channel: Microsoft-Windows-AppModel-Runtime/Diagnostics [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].

      as you see Microsoft-Windows-AppModel-Runtime/Diagnostics is the channel that is throwing the warning and now go to registry and delete the channel

      on registry:

      go to HKLMSOFTWAREMicrosoftWindowsCurrentVersionWINEVTChannels

      and find the appropriate channel as per the event log and delete them.

      make sure to delete all of them that is throwing the warning and reopen server manager and the events will be cleared.

      PS: please export and save registry before changes (just in case )

      SCCM Query on Technet

      • Proposed as answer by
        P_zachsys
        Wednesday, March 22, 2017 3:09 PM

    Источник

    RRS feed

    • Remove From My Forums

    locked

    Server Manager: Under Manageability — Online- Data retrieval failures occurred

    RRS feed

    • Question

    Answers

      • Marked as answer by
        Andy Qi
        Wednesday, February 12, 2014 1:47 AM

    All replies

    • Hello,<o:p></o:p>

      <o:p> </o:p>

      Thank you
      for posting your issue in the forum.<o:p></o:p>

      <o:p> </o:p>

      It seems
      like the issue is caused due to incorrectly setting GPP to collect Event Logs
      backup. <o:p></o:p>

      <o:p> </o:p>

      Important:
      The action plan below will modify the registry. However, serious
      problems might occur if you modify the registry incorrectly.       So please back up the registry before you modify it.
      Then, you can restore the registry if a problem occurs.<o:p></o:p>

           <o:p></o:p>

      After
      backing up the following registry key, please delete this AutoBakupLogFiles
      registry and refresh/close and open Server Manager.<o:p></o:p>

       <o:p></o:p>

      Name:
      AutoBackupLogFiles       <o:p></o:p>

      Location:

      HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesEventLogSecurity<o:p></o:p>

      <o:p> </o:p>

      Here is
      the article that gives more details on how to configure backing up event logs:<o:p></o:p>

       <o:p></o:p>

      msdn.microsoft.com/en-us/library/cc231247.aspx

      <o:p> </o:p>

      Best regards,<o:p></o:p>

      Sophia Sun<o:p></o:p>

    • Hi,

      How is everything going?

      Do you have any updates about the status of the issue? When you have time, please feel free to post this information here. Thanks for your cooperation.

      Regards,

    • please delete this AutoBakupLogFiles

      registry and refresh/close and open Server Manager


      HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesEventLogSecurity<o:p>

      There is no entry AutoBackupLogFiles on any machine, client or server using the Server Manager.

    • Hi,

      How is everything going?

      Do you have any updates about the status of the issue? When you have time, please feel free to post this information here. Thanks for your cooperation.

      Regards,

      Yes the issue still exists. I just did another upgrade from 2012 vl to 2012r2 vl and the problem is still happening.

      I did find out something interesting. Removing the GUI from the server and then re-installing it fixes the problem.

      Dism /online /disable-feature /featurename:ServerCore-FullServer

      Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer

      • Marked as answer by
        Andy Qi
        Tuesday, November 26, 2013 3:18 AM
      • Unmarked as answer by
        JC_3
        Tuesday, December 3, 2013 9:36 PM

    • Hi,

      How is everything going?

      Do you have any updates about the status of the issue? When you have time, please feel free to post this information here. Thanks for your cooperation.

      Regards,

      Yes the issue still exists. I just did another upgrade from 2012 vl to 2012r2 vl and the problem is still happening.

      I did find out something interesting. Removing the GUI from the server and then re-installing it fixes the problem.

      Dism /online /disable-feature /featurename:ServerCore-FullServer

      Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer

      As an update this worked 80% of the time. I still have several servers that are still reporting: Server Manager, All servers, Manageability column, «Online — Data retrieval failures occurred».

      • Marked as answer by
        Andy Qi
        Wednesday, February 12, 2014 1:47 AM

    • Hello,

      Just want to confirm the current situations.

      Please feel free to let us know if you need further assistance.

      Regards,

      Sophia Sun

      Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Hi,

      i had the exact same problem and the channel registry keys wasn’t the same as its mentioned on many forums . It varies on all machines so the general fix is below:

      Check in channel events in event viewer:

      Event viewer > Microsoft > Windows > servermanager-Managementprovider > Operational and check the warning messages it generates at the time of server manager refresh.

      eg:    Generic failure querying the localized name for channel: Microsoft-Windows-AppModel-Runtime/Diagnostics [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].

      as you see Microsoft-Windows-AppModel-Runtime/Diagnostics is the channel that is throwing the warning and now go to registry and delete the channel

      on registry:

      go to HKLMSOFTWAREMicrosoftWindowsCurrentVersionWINEVTChannels

      and find the appropriate channel as per the event log and delete them.

      make sure to delete all of them that is throwing the warning and reopen server manager and the events will be cleared.

      PS: please export and save registry before changes (just in case )

      SCCM Query on Technet

      • Proposed as answer by
        P_zachsys
        Wednesday, March 22, 2017 3:09 PM

    Источник

    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии

    А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Data folder not found как исправить ошибку
  • Dashchan ошибка при загрузке данных

    • ➤