Upgrade SQL 2000 Enterprise SP3 to SP4

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

New to SQL Server Programming

Upgrade SQL 2000 Enterprise SP3 to SP4

Author

Topic

suijan
Starting Member

1 Post

Posted - 2010-04-14 : 06:40:16

Hi All,

I am installing SQL 2000 Enterprise Editon on Windows 2003 Enterprise Edition ( 32 bit ) with HP Server using 8 Proc AMD 6 Core - total 48 Core with 96 GB Memory.

I have a problem when upgrading the SQL 2000 SP3 to SP4 with error message below :

A service control operation failed for the MSSQLSERVER service : 1460
The operation returned because the timeout period expired.

An error occured starting the service to build system catalogs

and there are services error

Could not start thr MSSQLSERVER service on local computer
Error 1067 : the process terminated unexpectedly..

Could not start SQLSERVERAGENT service on local computer
Error 1068 : the dependency service or group failed to start

Any advise ?

Thank you for your kind attention.

Regards,

Sui Jan

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-04-14 : 12:06:27

Check the Application Log for the reason why the services are having issues.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

kronik
Starting Member

1 Post

Posted - 2010-04-15 : 23:15:45

We have the same issue - trying to upgrade from SQL 2000 RTM to SP4. I've posted on a number of sites, no one has been much help as of yet.

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$SERV1DEVlog\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$SERV1DEVlog\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?

pbcconsulting
Starting Member

1 Post

Posted - 2010-09-18 : 15:24:22

I had 3 bizarre problems on this OLD SQL 2000 server:

- I couldn’t install SQL2000 SP4, nor any hotfixes (cumulative 2187 & 2249) completely – Kept on getting timeout error 1460 during those installs, and/or only the “tools” would update but not the DBs themselves (Master, etc…).

- I also couldn’t create maintenance plans (backups) for the SQL server – kept on getting SQL ServerAgent error 14258.

- Finally, my Online Backup software would always fail to backup the SQL server using its default SQL settings.

Then I discovered that the server was in “fiber / lightweight pooling mode” rather than in the default “thread mode”:

http://support.microsoft.com/kb/319942
http://www.sql-server-performance.com/faq/fiber_lightweight_pooling_p1.aspx
http://msdn.microsoft.com/en-us/library/aa175385(SQL.80).aspx

After I placed the server back into its default “thread mode”:

sp_configure 'allow updates', 1
go
reconfigure with override
go
sp_configure 'lightweight pooling', 0
go
reconfigure with override
go

…all my problems went away. I know it’s a very old issue, but perhaps there are still people out there that could benefit from this tidbit of experience.

Regards,

Philippe Blanchard, MCSE
President - PBC Consulting
philippe@pbcconsulting.com

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2010-09-18 : 22:58:57

I am always suspicious when someone bumps a 5 month old post, has the word "consulting" in their name, and provides contact information.