SQL 2000 RTM -> SP4 Upgrade Failing

  • 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? I found with some Googling trying to reinstall the MDAC and changing the unsigned secpol to Silently Succeed. I am trying that currently but wanted to know if there were any other ideas if it doesn't work.

    Additional info:

    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.

    Any ideas?

  • i've got some servers that are currently on SQL 2000 RTM and was wondering how to proceed with updating their patches to the latest versions even though its 2012 the customer is licenced to SQL 2000 so unless they pay for licence upgrades not much else I can do but upgrade patches.

    My question is should I proceed on a cumulative basis Ie upgrade to SP1, then SP2 then Sp3 before updating to SP4 and the latest cumulative update. Or would I be able to go straight from RTM -> SP4 with latest CU.

    In the past i've kept updates upto date so would appreciate some advise.

  • Service packs are cumulative. You can upgrade straight to SP4.

    That being said, even though they have a license for SQL 2000 they will not get support. Mainstream support ended in 2008 and extended support ends next summer. They would have had to bought into extended support to get it (before that cycle started) and there is still no guarantee that a patch for an issue can be provided for a particular issue.

    I would highly recommend breaching the topic of upgrades to a supported version.

    Joie Andrew
    "Since 1982"

  • Thanks joie, I agree about updating SQL versions to 2005. Believe it or not I have customers whos databases are still on version 6.5 and I have a proposal to upgrade their servers. my previous roles encompassed managing my own companies databases but currently started working for a company as a SQL consultant so role encompasses managing databases for around 12 customers whos databases are a mess. 😀

  • I would not go with SQL 2005 either. SQL Server 2008 R2 is the latest version that supports direct upgrades from SQL Server 2000.

    Products Released: SQL Server 2005 Enterprise Edition

    Lifecycle Start Date: 1/14/2006

    Mainstream Support End Date: 4/12/2011

    Extended Support End Date: 4/12/2016

    Service Pack Support End Date: 7/10/2007

    Microsoft Support Lifecycle

    Joie Andrew
    "Since 1982"

  • Fair points, Thanks for the responses.

    I'll have to rework the proposals and see whether the customers are happy to stump up extra cash, the money parts usually the stumbler for most work :hehe:

Viewing 6 posts - 1 through 5 (of 5 total)

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