Post reply

Using same service account for cluster and SQL

  • December 29, 2009 at 9:54 pm

    #137785

    Hi friends,

    I have a production server on SQL 2005 active /active cluster.

    Recently I am getting some logon error like

    SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed. [CLIENT: <IP>]

    and also

    logon errors for a second instance

    Error: 18456, Severity: 14, State: 10.

    The first error ,I learned ,denotes that the AD couldnot authenticate the user and

    the second error seems to occur when SQL service account is locked.

    A restart solved the problem for the time being.

    We are using same account to run the cluster service and for SQL server. Is there any problem with this?

    Please someone shed some light regarding this.

    ----------------------------------------------------------------------------------------------------------------------------------------------------
    Roshan Joe

    Jeff Moden -Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • December 30, 2009 at 8:06 am

    #1097457

    Hi,

    I'm not sure is related to the issue you are seeing, but I think you should run cluster and SQL services with different accounts, this way you can change their passwords only to the account you need it.

    To see if you are getting some login failed issues with your account you may use the toool lockoutstatus from microsoft.

    Regards.

    Jose Santiago Oyervides.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply