Results 1 to 10 of 10
  1. #1
    Join Date
    Mar 2010
    Posts
    5

    Unanswered: SQL 2000 RTM -> SP4 Failure

    So, I have 4 SQL instances, 3 clustered and 1 standalone. I can't seem to get SP4 to install to any of them.

    When I run it on the clustered named instances, it fails, one of the nodes (whichever I installed on) can never start the instance back up. The other works. On top of that, the Full-Text remains in Failure mode. I get a fairly generic error from the Event Viewer.

    On the standalone, default (or named) instance, it fails with the message of "A server control operation failed for the MSSQLSERVER service: 1460
    This operation returned because the timeout period expired." Subsequently, "an error occurred starting the service to build system catalogs".

    Last few lines of the log:

    01:42:58 Upgrading databases
    01:42:58 Upgrading databases on instance 'MSSQLSERVER'
    01:42:58 C:\DOCUME~1\TBA~1.ITS\LOCALS~1\Temp\3\SqlSetup\Bin \scm.exe -Silent 1 -Action 6 -Service MSSQLSERVER
    01:42:58 Process Exit Code: (0)
    01:42:58 C:\DOCUME~1\TBA~1.ITS\LOCALS~1\Temp\3\SqlSetup\Bin \scm.exe -Silent 1 -Action 6 -Service MSSQLSERVER
    01:42:58 Process Exit Code: (0)
    01:42:58 C:\DOCUME~1\TBA~1.ITS\LOCALS~1\Temp\3\SqlSetup\Bin \scm.exe -Silent 1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
    01:58:04 Process Exit Code: (1460) This operation returned because the timeout period expired.

    02:00:56 A service control operation failed for the MSSQLSERVER service: 1460
    This operation returned because the timeout period expired.

    02:01:24 An error occurred starting the service to build system catalogs.
    02:01:24 Action CleanUpInstall:
    02:01:24 Installation Failed.

    I suspect? if I can remedy this issue on the standalone, I may be able to do the same for the clustered?

    Any ideas?

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Is the timeout the SCM waiting for SQL Server to start up, or is it the service pack attempting to log in to the started instance, and timing out then? What is in the SQL Server errorlog? You should see one of them say something along the lines of "started in single user mode". What can happen at this point, is that if some process logs in as an administrator, they can take up that one connection, and lock out the service pack install. Likely causes can be monitoring packages (like BMC Patrol), Replication, any application that runs as an administrator.

  3. #3
    Join Date
    Mar 2010
    Posts
    5
    ERRORLOG

    2010-04-09 11:10:38.22 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
    Aug 6 2000 00:57:48
    Copyright (c) 1988-2000 Microsoft Corporation
    Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

    2010-04-09 11:10:38.22 server Copyright (C) 1988-2000 Microsoft Corporation.
    2010-04-09 11:10:38.22 server All rights reserved.
    2010-04-09 11:10:38.22 server Server Process ID is 2416.
    2010-04-09 11:10:38.22 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL

    Server\MSSQL$SERV1DEV\log\ERRORLOG'.
    2010-04-09 11:10:38.22 server SQL Server is starting at priority class 'normal'(12 CPUs detected).
    2010-04-09 11:10:38.36 server SQL Server configured for thread mode processing.
    2010-04-09 11:10:38.36 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
    2010-04-09 11:10:38.55 server Attempting to initialize Distributed Transaction Coordinator.
    2010-04-09 11:10:40.60 spid2 Starting up database 'master'.
    2010-04-09 11:10:40.79 server Using 'SSNETLIB.DLL' version '8.0.311'.
    2010-04-09 11:10:40.79 spid5 Starting up database 'model'.
    2010-04-09 11:10:40.79 server SQL server listening on 158.74.48.162: 1254.
    2010-04-09 11:10:40.80 server SQL server listening on 169.254.218.224: 1254.
    2010-04-09 11:10:40.80 server SQL server listening on 127.0.0.1: 1254.
    2010-04-09 11:10:40.82 spid2 Server name is 'SERVER203\SERV1DEV'.
    2010-04-09 11:10:40.82 spid8 Starting up database 'msdb'.
    2010-04-09 11:10:40.82 spid9 Starting up database 'pubs'.
    2010-04-09 11:10:40.82 spid10 Starting up database 'Northwind'.
    2010-04-09 11:10:40.96 spid5 Clearing tempdb database.
    2010-04-09 11:10:40.98 server SQL server listening on TCP, Shared Memory, Named Pipes.
    2010-04-09 11:10:40.98 server SQL Server is ready for client connections
    2010-04-09 11:10:41.13 spid5 Starting up database 'tempdb'.
    2010-04-09 11:10:41.21 spid2 Recovery complete.
    2010-04-09 11:10:41.27 spid2 Warning: override, autoexec procedures skipped.
    2010-04-09 11:10:59.10 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.

    exception.log

    04/09/10 11:11:40 spid 0 Exception 0x400042ac PRINTSTACK at 0x77E4BEF7
    04/09/10 11:11:42 spid 0 Exception

    0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x77E4BEF7


    SQLDUMP01

    ================================================== ===================
    BugCheck Dump
    ================================================== ===================

    This file is generated by Microsoft SQL Server 8.00.2039
    upon detection of fatal unexpected error. Please return this file,
    the query or program that produced the bugcheck, the database and
    the error log, and any other pertinent information with a Service Request.

    Computer type is AT/AT COMPATIBLE.
    Bios Version is S M C - 10000917
    Supermicro H8DMT/-F/-IBX/-IBXF BIOS Date: 10/17/09 06:24:54 Ver 3.5b
    Current time is 11:11:40 04/09/10.
    12 Intel x86 level 16, 2613 Mhz processor(s).
    Windows NT 5.2 Build 3790 CSD Service Pack 2.


    Memory
    MemoryLoad = 2%
    Total Physical = 4095 MB
    Available Physical = 4095 MB
    Total Page File = 4095 MB
    Available Page File = 4095 MB
    Total Virtual = 2047 MB
    Available Virtual = 2015 MB

    *Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL$SERV1DEV\
    log\SQLDump0001.txt
    * ************************************************** ***************************
    **
    *
    * BEGIN STACK DUMP:
    * 04/09/10 11:11:40 spid 0
    *
    * Exception Address = 77E4BEF7 (RaiseException + 0000003C Line 0+00000000)
    * Exception Code = 400042ac PRINTSTACK
    *
    * MODULE BASE END SIZE

    ------------------

    SQLDump002

    ================================================== ===================
    BugCheck Dump
    ================================================== ===================

    This file is generated by Microsoft SQL Server 8.00.2039
    upon detection of fatal unexpected error. Please return this file,
    the query or program that produced the bugcheck, the database and
    the error log, and any other pertinent information with a Service Request.

    Computer type is AT/AT COMPATIBLE.
    Bios Version is S M C - 10000917
    Supermicro H8DMT/-F/-IBX/-IBXF BIOS Date: 10/17/09 06:24:54 Ver 3.5b
    Current time is 11:11:42 04/09/10.
    12 Intel x86 level 16, 2613 Mhz processor(s).
    Windows NT 5.2 Build 3790 CSD Service Pack 2.


    Memory
    MemoryLoad = 2%
    Total Physical = 4095 MB
    Available Physical = 4095 MB
    Total Page File = 4095 MB
    Available Page File = 4095 MB
    Total Virtual = 2047 MB
    Available Virtual = 2014 MB

    *Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL$SERV1DEV\
    log\SQLDump0002.txt
    * ************************************************** ***************************
    **
    *
    * BEGIN STACK DUMP:
    * 04/09/10 11:11:42 spid 0
    *
    * Exception Address = 77E4BEF7 (RaiseException + 0000003C Line 0+00000000)
    * Exception Code = c000001d EXCEPTION_ILLEGAL_INSTRUCTION
    *
    * MODULE BASE END SIZE

    ------------------

    Event log:


    Event Type: Information
    Event Source: MSSQL$SERV1DEV
    Event Category: (2)
    Event ID: 17052
    Date: 4/9/2010
    Time: 11:11:16 AM
    User: N/A
    Computer: SERVER203
    Description:
    18801:
    SQLSETUP: The service pack installation for SERV1DEV has started.

    For more information, see Help and Support

    Center at Events and Errors Message Center: Basic Search.


    Event Type: Error
    Event Source: MSSQL$SERV1DEV
    Event Category: (2)
    Event ID: 17055
    Date: 4/9/2010
    Time: 11:11:42 AM
    User: N/A
    Computer: SERVER203
    Description:
    17066 :
    SQL Server Assertion: File: <serverma.c>, line=2833
    Failed Assertion = '(numSMT & (numSMT - 1)) == 0'.


    For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.


    Event Type: Error
    Event Source: MSSQL$SERV1DEV
    Event Category: (2)
    Event ID: 17055
    Date: 4/9/2010
    Time: 11:11:42 AM
    User: N/A
    Computer: SERVER203
    Description:
    17310 :
    SqlDumpExceptionHandler: Process 3612 generated fatal exception c000001d EXCEPTION_ILLEGAL_INSTRUCTION. SQL Server

    is terminating this process.


    For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.



    Event Type: Error
    Event Source: MSSQL$SERV1DEV
    Event Category: (2)
    Event ID: 17055
    Date: 4/9/2010
    Time: 11:11:42 AM
    User: N/A
    Computer: SERVER203
    Description:
    17311 :
    SQL Server is aborting. Fatal exception c000001d caught.


    For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

  4. #4
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    I am beginning to suspect that the binaries on one of the cluster nodes have been updated, but the binaries on the other node(s) have not. Can you go to sqlservr.exe in the BINN directory for this instance, on each node. Right click, and look for properties, then version. If they are different on one or more nodes, then you may be looking at a remove and replace of SQL Server to fix this.

    This line indicates RTM version:
    2010-04-09 11:10:38.22 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
    This line indicates not:
    This file is generated by Microsoft SQL Server 8.00.2039

  5. #5
    Join Date
    Mar 2010
    Posts
    5
    In this case, this is the standalone dev box - I'm trying to resolve it here first as I think if I can get it fixed here, I can fix it in the cluster.

  6. #6
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Try the following from a command prompt on the standalone box:
    Code:
    sqlservr.exe -c -s instancename -m
    You will want to run that from the BINN directory for the instance you are troubleshooting. See if there are any interesting messages in the std output. Oh, and make sure all the services related to the standalone instance are shut down beforehand. Contention for the master database is an ugly thing.

  7. #7
    Join Date
    Mar 2010
    Posts
    5
    I tried that earlier and it pumped out the same results, both dumps starting with "8.00.2039".

  8. #8
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    How long does the instance stay up?

  9. #9
    Join Date
    Mar 2010
    Posts
    5
    It never gets up - the SQL Server service never actually starts, it terminates unexpectedly with the aforementioned errors.

  10. #10
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Out of curiosity, how long does it stay up if you feed it the trace flags?

    Code:
    sqlservr.exe -c -s instancename -m -T4022 -T4010
    Some of my googling has pointed me toward a mismatch of the schema in the master database, and the executable version. You >might< (bit of a long shot, what with all the unknowns) be able to manually run the sql upgrade scripts, but I do not know what order they need to be run in. This is something I would only try on a completely throwaway instance.

    You may also try this, but his installation is failing at a different point than yours:

    sqlserver server Installing service pack fails (solution)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •