none
Create cluster for 2 node by scvmm 2012

    Question

  • I create cluster ( 2 node ) by scvmm 2012 rtm version, but i got the error code 25310 (Unable to connect to the user host process),

    I already create domain admins on local host of administrator group

    How can i solved it ?

    Monday, January 09, 2012 1:10 AM

All replies

  • As per MS you can retry the operation.

    http://social.technet.microsoft.com/wiki/contents/articles/4930.aspx


    Mohamed Fawzi | http://fawzi.wordpress.com
    Sunday, January 15, 2012 10:07 PM
  • Any update on this one?

     


    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )
    Thursday, February 02, 2012 5:00 PM
  • As per MS you can retry the operation.

    http://social.technet.microsoft.com/wiki/contents/articles/4930.aspx


    Mohamed Fawzi | http://fawzi.wordpress.com

    I get this error at the moment as well. The two hosts selected for the cluster both pass 100% of all Failover Cluster Manager Cluster Validation tests. VMM 2012 RC cluster wizard and FCM validation tests both run from the same user session on the same box.

    Retried this about half a dozen times. No go... Looking like a bug in the RC.

    Anyone got a work around? Should I just be attempting to create the cluster without running the validation tests?

    Cheers,
    Nick

    Thursday, February 09, 2012 6:08 AM
  • Could you please check your event logs once on the HOST. Specially anything around DCOM.


    Jeevan Bisht


    Sunday, February 19, 2012 2:23 PM
  • This worked for me: http://hypervzen.wordpress.com/2012/03/09/scvmm-2012-cluster-creation-and-error-25310/

    Add HKLM\Software\Microsoft\ Microsoft System Center Virtual Machine Manager Server\Settings\HelperHostConnectRetryCount DWORD = 0x0a

    on the VMM server

    and retry - no host or service restarts needed.

    Took a long time, but the cluster was created.

    The wiki link above that has the error codes is pretty much useless, as it simply has a table of the error codes and the same information that the VMM console provides, and no remediation actions are suggested.

    Friday, July 06, 2012 10:47 PM