SQL Server Performance

SQL Server Agent login failure

Discussion in 'SQL Server Clustering' started by look, Apr 15, 2004.

  1. look New Member


    I use SQL Serv 2000 running two noded cluster on W2K SP3.
    When i move group from Node2 to Node1 i get these in System log:

    "Logon attempt with current password failed with the following error:
    Logon failure: unknown user name or bad password"

    "The SQLSERVERAGENT" service failed to start due to the following error:
    The service did not start due to a logon failure."

    and the following in Security Log:

    "The logon to account: sqladmin
    by MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
    from workstation Node1
    failed: The error code was: 3221225578"

    "Logon failure:
    Reason: Unknown user name or bad password
    User Name: sqladmin
    Domain: MYDOMAIN
    Logon Type: 5
    Logon Process: SCMgr
    Authentication Package:
    MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
    Workstation Name: Node1"

    Moving group fails, gets back to Node2 and works fine on it.

    Server Agent runs from account MYDOMAINsqladmin and the password set there (via Enterprise Manager) is the same as for the domain user sqladmin.
    As you can see the problem occurs only with Node1, on Node2 everything works fine.

    Are the passwords cached locally on nodes or what ? Any ideas ?
  2. bradmcgehee New Member

    Be sure that the sqladmin user account is made a member of the local admin group of both nodes in the cluster.

    Also be sure the cluster service account is a domain account, is a member of the local admin group of both nodes, and is also a member of the admin group in SQL Server.

    Has this every worked, or has it always failed?

    -----------------------------
    Brad M. McGehee, MVP
    Webmaster
    SQL-Server-Performance.Com
  3. look New Member

    <br />&gt; Be sure that the sqladmin user account is made a member of the local admin group of both nodes in the cluster.<br /><br />It is not possible since there are no local accounts on nodes - they are primary and secondary DCs.<br /><br />&gt; Also be sure the cluster service account is a domain account<br /><br />It is.<br /><br />&gt; is a member of the local admin group of both nodes<br /><br />Not possible because of the top above.<br /><br />&gt; and is also a member of the admin group in SQL Server.<br /><br />It is.<br /><br />&gt; Has this every worked, or has it always failed?<br /><br />It worked, but now it does not. Unfortunately i dont know what operations could damage it <img src='/community/emoticons/emotion-6.gif' alt=':(' /><br /><br />
  4. barozai New Member

    I also go that problem acouple of months before. I did whatever I can do but the ultimate solution is reinstalling the SQL clustering.

    Aman
    DBA
    Chenab Ltd
  5. look New Member


    I found kind of workaround.
    Under "Cluster Administrator" choose Properties of "SQL Server Agent", then click Advanced tab.
    Then clear the checkbox "Affect the group".
    Now, even if the SQL Agent fails to run on NodeA, it does not make the group switch back to NodeB. But in such circumstances SQL backups will not work since they are driven by the Agent.
  6. bradmcgehee New Member

    I want to point out that is not a best practice to install a cluster on domain controllers, although it is possible. DC should be on dedicated boxes, just as SQL Server should be running on dedicated boxes, especially in a cluster environment.

    On another topic, on DC, there is a group called the Administrator Built-In group. You can use this group in instead of the Local Admin group to add your service accounts. If you haven't done this, I recommend you do.

    -----------------------------
    Brad M. McGehee, MVP
    Webmaster
    SQL-Server-Performance.Com

Share This Page