none
Provisioning of compute node fail due to user adding to Administrators group fail RRS feed

  • Question

  • Dear All,

    Please give a hand with this error, thank you so much in advance.

    1) Head Node:  Topology 5.  Win Server 2008 R2 Standard

    2) Compute Node: Win Server 2008 Standard

    Error Message: Relatively long, thank you for your patience first;)

    Time Message
    5/19/2011 10:32:32 AM The operation failed due to errors during execution.
    5/19/2011 10:32:32 AM Failed to add user S-1-5-21-2788599657-4248964495-2287889006-1217 () to group Administrators. Exception has been thrown by the target of an invocation.
    5/19/2011 10:32:32 AM Adding user S-1-5-21-2788599657-4248964495-2287889006-1217 to group Administrators
    5/19/2011 10:32:22 AM Retrying operation Update, retry count 1
    5/19/2011 10:32:22 AM Failed to add user S-1-5-21-2788599657-4248964495-2287889006-1217 () to group Administrators. Exception has been thrown by the target of an invocation.
    5/19/2011 10:32:22 AM Adding user S-1-5-21-2788599657-4248964495-2287889006-1217 to group Administrators
    5/19/2011 10:32:21 AM Updating Windows Firewall
    5/19/2011 10:32:17 AM Adding IP address 192.168.75.8:255.255.255.0 to network adapter 'Broadcom NetXtreme Gigabit Ethernet'
    5/19/2011 10:32:17 AM Adding member  to the security group Administrators
    5/19/2011 10:32:17 AM Updating the name of the network adapter Local Area Connection to Enterprise
    5/19/2011 10:32:17 AM Enabling the firewall on node R2-FINANCIAL\MATRIX
    5/19/2011 10:32:17 AM Updating the local host file based on changes to nodes in the cluster
    5/19/2011 10:32:17 AM Updating the configuration of R2-FINANCIAL\MATRIX
    5/19/2011 10:32:16 AM Updating Windows Firewall
    5/19/2011 10:32:13 AM Adding IP address 192.168.75.8:255.255.255.0 to network adapter 'Broadcom NetXtreme Gigabit Ethernet'
    5/19/2011 10:32:12 AM The operation failed due to errors during execution.
    5/19/2011 10:32:12 AM Failed to add user S-1-5-21-2788599657-4248964495-2287889006-1217 () to group Administrators. Exception has been thrown by the target of an invocation.
    5/19/2011 10:32:12 AM Adding user S-1-5-21-2788599657-4248964495-2287889006-1217 to group Administrators
    5/19/2011 10:32:02 AM Retrying operation Update, retry count 1
    5/19/2011 10:32:02 AM Failed to add user S-1-5-21-2788599657-4248964495-2287889006-1217 () to group Administrators. Exception has been thrown by the target of an invocation.
    5/19/2011 10:32:02 AM Adding user S-1-5-21-2788599657-4248964495-2287889006-1217 to group Administrators
    5/19/2011 10:32:01 AM Updating Windows Firewall
    5/19/2011 10:31:57 AM Adding IP address 192.168.75.8:255.255.255.0 to network adapter 'Broadcom NetXtreme Gigabit Ethernet'
    5/19/2011 10:31:57 AM Adding member  to the security group Administrators
    5/19/2011 10:31:57 AM Updating the name of the network adapter Local Area Connection to Enterprise
    5/19/2011 10:31:57 AM Enabling the firewall on node R2-FINANCIAL\MATRIX
    5/19/2011 10:31:57 AM Updating the local host file based on changes to nodes in the cluster
    5/19/2011 10:31:57 AM Updating the configuration of R2-FINANCIAL\MATRIX
    5/19/2011 10:31:56 AM Updating Windows Firewall
    5/19/2011 10:31:52 AM Adding IP address 192.168.75.8:255.255.255.0 to network adapter 'Broadcom NetXtreme Gigabit Ethernet'

    P.S . What is weird to me is that when it is adding the user, it should add the "Domain\UserName" instead of the ugly {SID} of the user,  is this a bug?

     Update : The same compute node can be successfully added to another head node, after an re-installation. So the problem is not in the compute node, it is in the server head node.  The difference between the two head nodes are the versions of HPC Pack. one is express, one is enterprise.  The one that fail is Express.  Re-installed the Express on the failing head node, error reproducible. Please advise. 

     




    Thursday, May 19, 2011 7:16 PM

All replies

  • Could you please include more information about the network configuration on your head node.  I see 192.168 addresses - are you running your own local domain controller and do you have a private domain? 

     

    Also could you please check to ensure the contents of your administrators group on your head node are in fact valide - are the SIDs there too or just when the compute node is added.

     

    Thanks,

    Mark

     

    Friday, May 20, 2011 11:37 PM
  • Hi Mike,

    Thank you so much for taking the time to reply to my question.  As for your first question, I am pretty sure that we are running a local domain controller within the cooperation which is not public. But I really don't know the difference between a local domain controller and private domain, appreciated if you could further clarify this point with me.

    As for the second question, since I am in no way a system admin, I am not sure how to check the admin group and how to verify its validity. Can you show me some links regarding how to do? I saw the SID was tried to add as user name which was very weird to me.

    Thanks,

    Feng Wang

     

     

     


    Feng Wang
    Friday, May 27, 2011 1:41 PM
  • Hi Mark,

    Do appologize for my too bad typing. But anyway, would you please lend a hand? Thx.

    Feng Wang

     


    Feng Wang
    Thursday, June 2, 2011 2:57 PM
  • On your headnode, open Administrative Tools -> Computer Management and then drill down to Local Users and Groups -> Groups -> Administrators

    What accounts are listed?

    Friday, June 3, 2011 8:23 AM
  • Dear LR90,

    Thank you so much for your reply with my question. The following is what I can saw on the machine head node after your advice,

    Administrator
    LovelyBird
    UglyBear
    XR-DOM\Administrator
    XR-DOM\Domain Admins
    XR-DOM\swang
    XR-DOM\ZEUS

    Among which Administrator, LovelyBird, UglyBear, XR-DOM\ZEUS are computers on the domain, XR-DOM\swang is a user name in the domain.

    Please advise.

     

     

     


    Feng Wang
    Friday, June 3, 2011 1:39 PM
  • Dear LR90,

    Thank you so much for your reply with my question. The following is what I can saw on the machine head node after your advice,

    Administrator
    LovelyBird
    UglyBear
    XR-DOM\Administrator
    XR-DOM\Domain Admins
    XR-DOM\swang
    XR-DOM\ZEUS

    Among which Administrator, LovelyBird, UglyBear, XR-DOM\ZEUS are computers on the domain, XR-DOM\swang is a user name in the domain.

    Please advise.


    Feng Wang
    Thursday, June 9, 2011 6:56 PM
  • Hi Feng Wang, Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
    The fact that your head node was showing SIDs in provisioning log indicates that it might have lost connectivity or trust with it's domain controller.  You might try re-joining the faulty head node to your domain as a possible resolution.  It is also possible that the network configuration for your head-node is not quite right.  If you can rejoin your head node to it's domain but continue to have problems, then it might help to provide the ouput from "ipconfig /all" on that head node.
    Thanks,
    --Brian
    Monday, June 20, 2011 8:16 AM
  • Dear Feng Wang,

     

     Are you still dealing with this issue or has the information that Brian has provided helped?

     

    Mark

     

    Thursday, October 20, 2011 6:46 PM
  • Hi Mark,

    Thank you for your care. Information from Brian although new, but did not help. The final workaround I adopt is that choose a different Computer as the Head node, and don't use that one any more due to the fact that the troublesome computer is mainly used as a development unit all the time anyhow.  

    Feng Wang


    Feng Wang
    • Proposed as answer by Mark Staveley Thursday, October 20, 2011 8:31 PM
    Thursday, October 20, 2011 7:10 PM