SQL Server Performance

failover node not working

Discussion in 'SQL Server Clustering' started by mrdavevoge, Apr 21, 2006.

  1. mrdavevoge New Member

    We installed some windows updates. Tried to move the node to update the other server then we get a failure. What i am assuming that is happenning here is that xpsqlbot.dll is looking for a file that doesn't exist or is corrupted. Please look at the sql log and event viewer for the error messages. Thanks in advance.

    Last 2 entries from the sql error log

    Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.
    SQL Server is terminating due to 'stop' request from Service Control Manager.


    system log on failure

    Event Type:Error
    Event Source:Service Control Manager
    Event Category:None
    Event ID:7000
    Date:4/21/2006
    Time:9:59:34 PM
    User:N/A
    Computer:SW73DPTAPP02
    Description:
    The MSSQLSERVER service failed to start due to the following error:
    The system cannot find the file specified.

    For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
  2. satya Moderator

    Have you referred that hotifx about any specific instructions on clustered environment.
    In my experience the most common cause of this issue is when one of the files needed by sql server was not on a shared resource, and Sql Server, once failed to the other node, couldn't access it.

    I would like to know whether this failing process is same when failing-over to other node too?
    If not, verify that the files being accessed can be seen by both nodes.

    KBAhttp://support.microsoft.com/default.aspx?scid=kb;en-us;322140 for reference, test and fix (may) it.

    Satya SKJ
    Microsoft SQL Server MVP
    Contributing Editor & Forums Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  3. Argyle New Member

    The xp_qv is a standard thing that is run. The interesting part is the line after which is: "SQL Server is terminating due to 'stop' request from Service Control Manager."

    So the question is why does it stop? The reason can be found in the description field in the event log: "The MSSQLSERVER service failed to start due to the following error: The system cannot find the file specified."

    As satya mentions, the SQL Server service can not find its startup files on the second node. Most likely unrelated to the windows updates. Have you ever failed over successfully before?

    On the problem node go to the Administrative Tools -> Services and check the properties on the MSSQLSERVER service. There you can see the path to the files for the service. Verify that it is on a shared drive (that was sucessfully failed over as well) and that the correct rights exist for the SQL Service account to execute these files.
  4. mrdavevoge New Member

    Thank for your help guys. It turns out that our antivirus software somehow quarentined some of our sql server files including sqlserver.exe. We use MacFee, not sure why it would do that.
  5. satya Moderator

    ... then best bit is to exclude SQL server realted files from the AV checkup. This is one of the reasons why AV must be refrained from SQL Servers, if not atleast exclude the SQL path.

    Satya SKJ
    Microsoft SQL Server MVP
    Contributing Editor & Forums Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page