locked
server execution error server 2012 r2 RRS feed

  • Question

  • when i go to the server manager to add roles and features i get a server execution failed at the server selection screen after i hit next, even though the correct server is selected the event log says The server {$%%#^##%#$^$%} did not register with DCOM within the required timeout.  10010 error source being distributedCOM  i have researched and tried a great deal, any ideas
    Friday, October 16, 2015 1:06 PM

Answers

  • Hi johnwagr,

    Thanks for your post.

    The Component Object Model (COM) infrastructure tried to start the named server; however, the server did not reply within the required timeout period. There might be a deadlock, or the program might not have responded to the server initialization code within the timeout period of two minutes.

    You could follow Milos Puchta's suggestion in the similar thread discussed before to do the troubleshooting.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/77b1db1d-f186-4515-8f7d-2241942eb9b7/distributedcom-error-id-10010?forum=winservergen

    Best Regards,

    Mary Dong


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

    • Proposed as answer by Mary Dong Tuesday, October 27, 2015 1:06 AM
    • Marked as answer by Mary Dong Thursday, October 29, 2015 1:37 AM
    Monday, October 19, 2015 8:59 AM

All replies

  • There's some info here on exceptions for DCOM.

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

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Friday, October 16, 2015 1:17 PM
  • Hi johnwagr,

    Thanks for your post.

    The Component Object Model (COM) infrastructure tried to start the named server; however, the server did not reply within the required timeout period. There might be a deadlock, or the program might not have responded to the server initialization code within the timeout period of two minutes.

    You could follow Milos Puchta's suggestion in the similar thread discussed before to do the troubleshooting.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/77b1db1d-f186-4515-8f7d-2241942eb9b7/distributedcom-error-id-10010?forum=winservergen

    Best Regards,

    Mary Dong


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

    • Proposed as answer by Mary Dong Tuesday, October 27, 2015 1:06 AM
    • Marked as answer by Mary Dong Thursday, October 29, 2015 1:37 AM
    Monday, October 19, 2015 8:59 AM