Online data retrieval failures occurred windows 2019 - Доктор Windows

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>

Источник

Обновлено 03.06.2020

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

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

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

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

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

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

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

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

Попытавшись открыть настройки 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

Видя все это безобразие, я полез на свои брокеры подключений, напоминаю для этого нужно использовать ключ «/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

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

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

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

Из самых распространенных проблем, это наличие на вашем сервере, куда вы подключаетесь наличие программного продукта КриптоПРО версии 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 использовал протокол UDP.

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

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

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

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

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

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

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

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

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

Источник

3 Replies

mace

Windows Server Expert
- check
  120
  Best Answers
- thumb_up
  969
  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

Источник

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

Источник

Categories
Discussions
Cireson Uploads
Feature Request

Home› General Discussion

Online — Data Retrieval Failures Occurred

Curious if anyone has ever seen this error before. Started a couple weeks ago and since then our workflows have been stopping mid day. We restart the Cache Builder service and that seems to get things going again.

CIRESON COMMUNITY WEB SITE

TERMS OF USE

AGREEMENT BETWEEN USER AND CIRESON

The Cireson Community Web Site is comprised of various web pages operated by Cireson, LLC (collectively, the web pages are referred to herein as the “Cireson Community Web Site”).

The Cireson Community Web Site is offered to you conditioned on your acceptance of the terms, conditions, and notices contained herein without modification or exception. Your use of the Cireson Community Web Site constitutes your agreement to all such terms, conditions, and notices contained in these Terms of Use.

MODIFICATION OF THESE TERMS OF USE

Cireson reserves the right to change the terms, conditions, and notices under which the Cireson Community Web Site is offered, including but not limited to the charges associated with the use of the Cireson Community Web Site upon written notice.

LINKS TO THIRD PARTY SITES

The Cireson Community Web Site may contain links to other Web Sites (“Linked Sites”). The Linked Sites are not under the control of Cireson and therefore Cireson is not responsible for the contents of any Linked Site, including, without limitation, any link contained in a Linked Site, or any changes or updates to a Linked Site. Cireson is not responsible for webcasting or any other form of transmission received from any Linked Site. Cireson is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Cireson of the site or any association with its operators.

NO UNLAWFUL OR PROHIBITED USE

As a condition of your use of the Cireson Community Web Site, you warrant to Cireson that you will not use the Cireson Community Web Site for any purpose that is prohibited by law, rule regulation or by any of these terms, conditions, and notices, including, without limitation the export of any Software or technical data to any country prohibited by law. You may not use the Cireson Community Web Site in any manner which could damage, disable, overburden, or impair the Cireson Community Web Site or interfere with any other party’s use and enjoyment of the Cireson Community Web Site. You may not obtain or attempt to obtain any materials or information through any means not intentionally made available or provided for through the Cireson Community Web Site.

USE OF COMMUNICATION SERVICES

The Cireson Community Web Site may contain bulletin board services, chat areas, news groups, forums, communities, personal web pages, calendars, and/or other message or communication facilities designed to enable you to communicate with the public at large or with a group (each a “Communication Service,” and collectively, “Communication Services”). You agree to use the Communication Services only to post, send and receive messages and material that are appropriate, proper and related to the particular Communication Service. By way of example, and not as a limitation, you agree that when using a Communication Service, you will not:

Defame, abuse, harass, stalk, threaten or otherwise violate the legal rights (such as rights of privacy and publicity) of others.
Publish, post, upload, distribute or disseminate any inappropriate, profane, defamatory, infringing, obscene, indecent or unlawful topic, name, material or information.
Upload files that contain software or other material protected by intellectual property laws (or by rights of privacy of publicity) unless you own or control the rights thereto or have received all necessary consents.
Upload files that contain viruses, corrupted files, or any other similar software or programs that may damage the operation of another’s computer.
Advertise or offer to sell or buy any goods or services for any business purpose, unless such Communication Service specifically allows such messages.
Conduct or forward surveys, contests, pyramid schemes or chain letters.
Download any file posted by another user of a Communication Service that you know, or reasonably should know, cannot be legally distributed in such manner.
Falsify or delete any author attributions, legal or other proper notices or proprietary designations or labels of the origin or source of software or other material contained in a file that is uploaded.
Restrict or inhibit any other user from using and enjoying the Communication Services.
Violate any code of conduct or other guidelines which may be applicable for any particular Communication Service.
Harvest or otherwise collect information about others, including e-mail addresses, without their consent.
Violate any applicable laws, rules or regulations.

Cireson has no obligation to monitor the Communication Services. However, Cireson reserves the right to review materials posted to a Communication Service and to remove any materials in its sole discretion. Cireson reserves the right to suspend or terminate your access to any or all of the Communication Services at any time without notice for any reason whatsoever.

Cireson reserves the right at all times to disclose any information as necessary to satisfy any applicable law, rule, regulation, legal process or governmental request, or to edit, refuse to post or to remove any information or materials, in whole or in part, in Cireson’s sole discretion.

Always use caution when giving out any personally identifying information about yourself or your children in any Communication Service. Always use caution when giving out any information concerning your employer or customers, if any. Cireson does not control or endorse the content, messages or information found in any Communication Service and, therefore, Cireson specifically disclaims any liability with regard to the Communication Services and any actions resulting from your participation in any Communication Service. Managers and hosts are not authorized Cireson spokespersons, and their views do not necessarily reflect those of Cireson.

Materials uploaded to a Communication Service may be subject to posted limitations on usage, reproduction and/or dissemination. You are responsible for adhering to such limitations if you download the materials.

MATERIALS PROVIDED TO CIRESON OR POSTED ON THE CIRESON COMMUNITY WEB SITE

Cireson does not claim ownership of the materials you provide to Cireson via the Cireson Community Web Site (including feedback and suggestions) or post, upload, input or submit to the Cireson Community Web Site or its associated services (collectively “Submissions”). However, by posting, uploading, inputting, providing or submitting your Submission you are granting Cireson, its affiliated companies and sublicensees permission to use your Submission in connection with the operation of their Internet businesses including, without limitation, the rights to: copy, distribute, transmit, publicly display, publicly perform, reproduce, edit, translate and reformat your Submission; and to publish your name in connection with your Submission.

No compensation will be paid with respect to the use of your Submission, as provided herein. Cireson is under no obligation to post or use any Submission you may provide and may remove any Submission at any time in Cireson’s sole discretion.

By posting, uploading, inputting, providing or submitting your Submission you warrant and represent that you own or otherwise control all of the rights to your Submission as described in this section including, without limitation, all the rights necessary for you to provide, post, upload, input or submit the Submissions.

LIABILITY DISCLAIMER

THE INFORMATION, SOFTWARE, PRODUCTS, AND SERVICES INCLUDED IN OR AVAILABLE THROUGH THE CIRESON COMMUNITY WEB SITE MAY INCLUDE INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN. CIRESON (OR ITS SUPPLIERS) MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE CIRESON COMMUNITY WEB SITE AT ANY TIME. ADVICE RECEIVED VIA THE CIRESON COMMUNITY WEB SITE SHOULD NOT BE RELIED UPON FOR PERSONAL, MEDICAL, LEGAL OR FINANCIAL DECISIONS AND YOU SHOULD CONSULT AN APPROPRIATE PROFESSIONAL FOR SPECIFIC ADVICE TAILORED TO YOUR SITUATION.

NEITHER CIRESON NOR ANY OF ITS SUPPLIERS MAKE ANY REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, AVAILABILITY, TIMELINESS, AND ACCURACY OF THE INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS CONTAINED ON THE CIRESON COMMUNITY WEB SITE FOR ANY PURPOSE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, ALL SUCH INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS ARE PROVIDED “AS IS” WITHOUT WARRANTY OR CONDITION OF ANY KIND. CIRESON AND/OR ITS SUPPLIERS HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL CIRESON AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OR PERFORMANCE OF THE CIRESON COMMUNITY WEB SITE, WITH THE DELAY OR INABILITY TO USE THE CIRESON COMMUNITY WEB SITE OR RELATED SERVICES, THE PROVISION OF OR FAILURE TO PROVIDE SERVICES, OR FOR ANY INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS OBTAINED THROUGH THE CIRESON COMMUNITY WEB SITE, OR OTHERWISE ARISING OUT OF THE USE OF THE CIRESON COMMUNITY WEB SITE, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF CIRESON OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES. BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IF YOU ARE DISSATISFIED WITH ANY PORTION OF CIRESON COMMUNITY WEB SITE, OR WITH ANY OF THESE TERMS OF USE, YOUR SOLE AND EXCLUSIVE REMEDY IS TO DISCONTINUE USING THE CIRESON COMMUNITY WEB SITE.

SERVICE CONTACT: [email protected]

TERMINATION/ACCESS RESTRICTION

Cireson reserves the right, in its sole discretion, to terminate your access to the Cireson Community Web Site and the related services or any portion thereof at any time, without notice.

GENERAL

To the maximum extent permitted by law, this agreement is governed by the laws of the State of California, U.S.A. and you hereby consent to the exclusive jurisdiction and venue of courts in San Diego County, California, U.S.A. in all disputes arising out of or relating to the use of the Cireson Community Web Site. Use of the Cireson Community Web Site is unauthorized in any jurisdiction that does not give effect to all provisions of these terms and conditions, including without limitation this paragraph. You agree that no joint venture, partnership, employment, or agency relationship exists between you and Cireson as a result of this agreement or use of the Cireson Community Web Site. Cireson’s performance of this agreement is subject to existing laws and legal process, and nothing contained in this agreement is in derogation of Cireson’s right to comply with governmental, court and law enforcement requests or requirements relating to your use of the Cireson Community Web Site or information provided to or gathered by Cireson with respect to such use. If any part of this agreement is determined to be invalid or unenforceable pursuant to applicable law including, but not limited to, the warranty disclaimers and liability limitations set forth above, then the invalid or unenforceable provision will be deemed superseded by a valid, enforceable provision that most closely matches the intent of the original provision and the remainder of the agreement shall continue in effect. Unless otherwise specified herein, this agreement constitutes the entire agreement between the user and Cireson with respect to the Cireson Community Web Site and it supersedes all prior or contemporaneous communications and proposals, whether electronic, oral or written, between the user and Cireson with respect to the Cireson Community Web Site. A printed version of this agreement and of any notice given in electronic form shall be admissible in judicial or administrative proceedings based upon or relating to this agreement to the same extent and subject to the same conditions as other business documents and records originally generated and maintained in printed form. It is the express wish to the parties that this agreement and all related documents be drawn up in English.

COPYRIGHT AND TRADEMARK NOTICES:

TRADEMARKS

The names of actual companies and products mentioned herein and on the Cireson Community Web Site may be the trademarks of their respective owners.

The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person, or event is intended or should be inferred.

Any rights not expressly granted herein are reserved.

NOTICES AND PROCEDURE FOR MAKING CLAIMS OF COPYRIGHT INFRINGEMENT

Cireson respects the intellectual property of others and asks that users of the Cireson Community Web Site do the same. In connection with the Cireson Community Web Site, we have adopted and implemented a policy respecting copyright law that provides for the removal of any infringing materials and for the termination, in appropriate circumstances, of users of the Cireson Community Web Site who are repeat infringers of intellectual property rights, including copyrights. If you believe that one of the Cireson Community Web Site users is, through the use of the Cireson Community Web Site, unlawfully infringing the copyright(s) in a work, and wish to have the allegedly infringing material removed, the following information in the form of a written notification (pursuant to 17 U.S.C. § 512(c)) must be provided to our designated Copyright Agent:

your physical or electronic signature;
identification of the copyrighted work(s) that you claim to have been infringed;
identification of the material on our services that you claim is infringing and that you request us to remove;
sufficient information to permit us to locate such material;
your address, telephone number, and e-mail address;
a statement that you have a good faith belief that use of the objectionable material is not authorized by the copyright owner, its agent, or under the law; and
a statement that the information in the notification is accurate, and under penalty of perjury, that you are either the owner of the copyright that has allegedly been infringed or that you are authorized to act on behalf of the copyright owner.

Please note that, pursuant to 17 U.S.C. § 512(f), any misrepresentation of material fact (falsities) in a written notification automatically subjects the complaining party to liability for any damages, costs and attorney’s fees incurred by us in connection with the written notification and allegation of copyright infringement.

Designated Agent: Matthew W. Deen, Esq.

Address of Agent: 1620 Fifth Avenue, Suite 875, San Diego, CA 92101

Telephone: 619-993-8873

Fax: 888-244-8458

Email: [email protected]

Источник

by
·

Published December 19, 2013
· Updated February 20, 2015

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.

Источник

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

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

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

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

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

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

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

Из самых распространенных проблем, это наличие на вашем сервере, куда вы подключаетесь наличие программного продукта КриптоПРО версии 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. Для этого создайте групповую политику или отредактируйте локальную на серверах подключений, вот по такому пути:

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

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

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

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

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

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

Источник

Online — Data Retrieval Failures Occred

Hi,

Thanks for posting in the forum.

Regarding the current issue, since you have received the error Online — Data Retrieval Failures Occurred in Server Manager after upgrading to Windows Server 2012 R2, I suggest you could refer
to the following article to see if it could work. As it mentioned, the issue may be related to a bad upgrade Routine.

Tip: Fixing Windows Server 2012 upgrade to Server 2012 R2 Data retrieval issue in Server Manager

http://blog.cloud-client.info/2013/09/27/tip-fixing-windows-server-2012-upgrade-to-server-2012-r2-data-retrieval-issue-in-server-manager/

In addition, regarding the error message in DC1, please try to refer to the following article for troubleshooting.

Windows Server 2012 — Server Manager Troubleshooting Guide, Part III: Common Events and Errors in Server Manager

http://social.technet.microsoft.com/wiki/contents/articles/13445.windows-server-2012-server-manager-troubleshooting-guide-part-iii-common-events-and-errors-in-server-manager.aspx

Hope this helps.

Best Regards,

Andy Qi

TechNet Subscriber Support

If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.

November 18th, 2013 8:39am

What I ended up doing is another upgrade. This time an in-place upgrade Server 2012 R2 to Server 2012 R2.

It resolved the issue. Thanks.

Marked as answer by

Monday, November 18, 2013 2:33 PM

November 18th, 2013 2:32pm

Hello,

the URL to the cloud-client.info article has been changed, it’s now http://blog.cloud-client.info/?p=632

Cheers

Michael

Proposed as answer by
TomazicM
12 hours 40 minutes ago

June 12th, 2014 4:52pm

Источник