Data retrieval failures occurred ошибка - Ремонт и установка крупной бытовой техники

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:

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,

A strange thing appears in the log:

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

Here is the log:

C:Windowssystem32>cd wbem

C:WindowsSystem32wbem>cd AutoRecover

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

C:WindowsSystem32wbemAutoRecover>

Обновлено 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.

Источник

You may find that when you add an Exchange server to a DAG that Server Manager shows multiple errors.

The Notification flag at the top indicates «Refresh failed» and Manageability for All Servers shows an error for the remote DAG member saying, «Online — Data retrieval failures occurred«.

You may also see errors that say, «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).«

These errors occur when the Failover Clustering feature is installed on the DAG member. I’ve usually only seen this for Exchange 2019 installed in Windows Server 2019 or Windows Server 2022. This is a Windows Server issue, not an Exchange issue, so this fix should also apply to any Windows cluster experiencing this problem.

The fix is to increase the WSMAN maxEnvelopeSize in the registry on all DAG members.

On the DAG member, launch regedit.exe and navigate to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANClient.
Create a new DWORD (32-bit) value named maxEnvelopeSize, or modify it if it already exists.
Set the value data to 2000 hexadecimal (8192 decimal).

Finally, restart the Windows Remote Management (WS-Management), aka WinRM, service on the server.

When you refresh Server Manager, the error should go away.

Источник

Please see the detailed info below:

Since the upgrade Windows Server 2012 to Windows Server 2012 R2 a couple of days ago, I started receiving the following:

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

I was able to drill down a bit more by clicking notifications at the top right of server manager and under task details this is the detailed message received:

(Computer Name): Configuration refresh message: The system cannot access one or more event logs because of insufficient rights, file corruption, or other reasons. For more information, see the Operation channel in the ServerManager-ManagementProvider
error log on the target server.

When I go to the Applications and Services Logs, Microsoft, Windows, ServerManager-ManagementProvider, Operational in the Event Log, These are some of the alerts I am receiving:

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

Failed to query the results of bpa xpath: Microsoft/Windows/CertificateServices:$reports$*Result.xml:/ResultDatabase/Result. error: A device attached to the system is not functioning., last error: The system cannot find the path specified..

Failed to query the results of bpa xpath: Microsoft/Windows/MSMQ:$reports$*Result.xml:/ResultDatabase/Result. error: A device attached to the system is not functioning., last error: The system cannot find the path specified..

Failed to query the results of bpa xpath: Microsoft/Windows/WebServer:$reports$*Result.xml:/ResultDatabase/Result. error: A device attached to the system is not functioning., last error: The system cannot find the path specified..

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

I am signed on as the administrator of the domain. This only happened after the upgrade to 2012 RTM R2. This message is in regards to the local server, not remote servers in the domain as I have read in other posts.

The only other issue I had during the upgrade was with Exchange 2013 database not mounting (The server with the issue is an Exchange VM). When upgrading, the system did not perform a clean shutdown. Maybe the install should gracefully shut down
Exchange Services prior to any upgrades on Server OS’s? There was a chance that my database was corrupted, but after hours of troubleshooting, I was able to repair database any move the logs to another directory and finally the database mounted and all
is good now. I know the Exchange info is probably for another forum, but incase any of this is related to the current problem, I felt I should state it up front.

I appreciate any assistance from Microsoft or from anyone who has any ideas as to what I should be looking for to resolve.

Thanks,

Ray

Источник

3 Replies

Brand Representative for Object First
mace

Windows Server Expert

check
123
Best Answers

thumb_up
1000
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

Источник