Answered Failed to start a SQL cluster

  • Saturday, April 28, 2012 3:45 AM
     
     

    Hi,

    My SQL cluster is failed to start, and it constantly shows "Unable to obtain the Primary Cluster Name Identity token" and "Please ensure that the witness resource is online and available", I checked security permissions of computer object in ADUC the cluster$ and SQL installing account were granted as "full control", further more I find out a error as below picture, hope buddies in this forum can help me out,thanks.


    Best regards,

All Replies

  • Saturday, April 28, 2012 6:38 AM
     
     

    Can you check the cluster logs in the OS-what other error has logged in it

    c:\windows\cluster\cluster.log


    Rama Udaya.K ramaudaya.blogspot.com ---------------------------------------- Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Monday, April 30, 2012 7:46 AM
    Moderator
     
     

    Hi Blue Coast,

    Please post the detailed error log as Udaya suggested.


    Best Regards,
    Peja

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Monday, April 30, 2012 7:57 AM
     
     Proposed

    See if the below helps  you

    /*

    A 2005 failover cluster is suddenly unable to start its network name resource, what do you do? Panic?! The logs show that the cluster name object (CNO) is “unable to obtain the primary cluster name identity token” along with a few other account related errors. After verifying the CNO is still in AD and the permissions are correct, it ultimately turns out to be an account password synchronization issue. If this ever happens to you, open the Failover Cluster Manager, right click on the CNO that is failing and select “More Actions” then select “Repair Active Directory Object”. Luckily it’s a nice quick fix.

    */


    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/

  • Tuesday, May 15, 2012 8:57 AM
     
     
    Hi Udaya,

    I get logs "adc:e70.05/16[03:06:40.727](000000) WARN  [RES] Network Name <SQL Network Name (SQL)>: Password for computer account SQLCLUS$ is incorrect (status 0x00000569).  LOGONUSER Failed for CNO Incorrect CNO password .", how can I fix it?

    Dimant,

    I'd tried “Repair Active Directory Object” but it doesn't work for me, any other ideas? 

    and I see errors "The cluster identity 'Sqlcluster$' may lack permissions required to update the object"


    Best regards,
    • Edited by Blue Coast Thursday, May 17, 2012 5:03 AM
    •  
  • Thursday, May 17, 2012 5:38 AM
    Moderator
     
     Answered

    Hi Blue Coast,

    Cause
    Local Group policy "Access this computer from the Network" is missing
    "Every one"
    Resolution

    Executed GPEDIT.MSC on Cluster Node Under Local Computer Policy
    ->Computer Configuration -> Windows Settings-> Security Settings ->
    Local Polices -> User Rights Assignment, Added Everyone and Authenticated
    Users for "Access this computer from the Network " Policy

    Make sure the policy is configured on all cluster
    nodes.

    And the default local policy on a cluster node includes the following
    groups:

    Administrators
    Backup
    Operators
    Everyone
    Users

    Once add 'Authenticated Users' to the
    policy and ran a gpupdate /force on the
    cluster nodes, the Cluster Network
    Name came Online.

    Note: if the resources fails to come Online, you can
    alternatively try a 'Repair
    Active Directory Object' operation


    Best Regards,
    Peja

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.