none
dcom error 10010 + server manager cannot refresh roles and features error.

    Question

  • I am running a fresh installation of Windows server 2012 R2 (fully updated) acting as primary domain controller with DNS, DHCP, DFS, VSS, Hyper-V and about 1 TB of files being shared. On a fresh boot, everything is fine and working good. 

    Every 3-4 days however, I log into to the server and see a DCOM Error Event ID 10010 and the Server Manager cannot refresh roles and features. The shadow copies stop working automatically and previous versions disappear. I can however force a manual shadow copy successfully. If I leave the server in this state for more than a day or 2, the remote desktop screen becomes black when i try and login, and so i have to reboot the server while being physically in front of it. (I'm not 100% sure both problems are related). After I reboot, everything is back to normal. 

    I have seen and read several articles on technet but nothing for Server 2012. Please can anyone help me! I cannot continue to lose all previous versions of our companys files. 

    Thanks

    J



    Saturday, March 08, 2014 6:54 PM

All replies

  • Hi Babajeeb69,

    Based on my research, please try to find the relevant Application according to the AppGUID(listed in Event ID 10010), and find which application it is and try Re-registering exe's (DCOM), then try to stop and restart the service.

    In addition, please also refer to these to troubleshoot:

    DistributedCOM Error ID 10010

    Event ID: 10010 Source: DCOMI hope this helps.

    Monday, March 10, 2014 4:12 PM
  • DistributedCOM 10010 Error : The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. In the registry:i have 2 entries. I do not know which application this is ?!  I only got it once after my reboot so i'm not sure this is the cause of all my issues. 

    HKCR\wow6432Node\CLSID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}

    -ShellWindows

    -Interactive User

    HKCR\CLSID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}\LocalServer32\

    -%sysroot%\system32\rundll32.exe shell32.dll, ShCreateLocalServerRunDll {9bA..}

    Before rebooting i had this DCOM every 10mins. The server was not really responsive as described above.

    the server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout.

    %systemroot%\system32\wbem\wmiprvse.exe

    I already did a sfc /scannow with no errors, and a "WMIPRVSE.exe /regserver" .

    Which service do i restart?

    I can't really tell if it works right away because the server is fine for a few days after reboot. All i can say is i had a few thousand dcom erros for wmiprv when the server was unresponsive.

    Any help is extremely appreciated.



    Tuesday, March 11, 2014 2:15 PM
  • These guys have the same problem:

     http://social.technet.microsoft.com/Forums/windowsserver/en-US/523d180c-a213-416c-ae8f-bdb430e8e373/dcom-errors-event-id-10010-printing-and-remote-desktop-issue?forum=winserver8gen

    Tuesday, March 11, 2014 2:20 PM
  • If you look in Event Viewer, expand Applications and Services Logs, Microsoft, Windows, WMI-Activity, operational 

    we get errors like these before it happens :

    Id = {B2464CD7-6E73-4AB1-984A-D62A829DA902}; ClientMachine = PCNAME; User = DOMAIN\USER; ClientProcessId = 7152; Component = Provider; Operation = Start IWbemServices::ExecMethod - root\microsoft\windows\servermanager : MSFT_ServerManagerTasks::GetServerFeature; ResultCode = 0x80041001; PossibleCause = Unknown

    Id = {9830001E-0F31-4D04-8F36-D8D18D89444A}; ClientMachine = PCNAME; User = DOMAIN\USER; ClientProcessId = 8252; Component = Unknown; Operation = Start IWbemServices::ExecMethod - root\Microsoft\Windows\ServerManager : MSFT_ServerManagerDeploymentTasks::GetServerComponentsAsync; ResultCode = 0x80080005; PossibleCause = Unknown

    CIMWin32 provider started with result code 0x0. HostProcess = wmiprvse.exe; ProcessID = 8252; ProviderPath = %systemroot%\system32\wbem\cimwin32.dll

    mgmtprovider provider started with result code 0x0. HostProcess = wmiprvse.exe; ProcessID = 8252; ProviderPath = %systemroot%\system32\wbem\mgmtprovider.dll

    Thursday, March 13, 2014 5:16 PM
  • hello babajeeb69,

    could you to solve this error? I'm with the same error.

    Thanks.


    • Edited by Eduardo Dm Friday, August 29, 2014 6:52 PM
    Friday, August 29, 2014 6:49 PM