moonshadow
Programmer
We're trying to install SQL 2000 (no SP) and then SP4 on Windows 2003 SP1. This is being installed automatically. However, the initial SQL 2K install is failing. The sqlstp.log has the following error message:
14:18:35 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 196814 -U sa -P
###############################################################################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occurred while attempting to start the service (1053)
SQL Server configuration failed.
###############################################################################
14:23:31 Process Exit Code: (-1)
14:23:31 Setup failed to configure the server. Refer to the server error logs and C:\WINDOWS\sqlstp.log for more information.
The error log for SQL is thus:
2005-09-05 14:18:35.67 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2005-09-05 14:18:35.68 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-09-05 14:18:35.68 server All rights reserved.
2005-09-05 14:18:35.68 server Server Process ID is 3412.
2005-09-05 14:18:35.68 server Logging SQL Server messages in file 'E:\MSSQL\log\ERRORLOG'.
2005-09-05 14:18:35.69 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2005-09-05 14:18:35.75 server SQL Server configured for thread mode processing.
2005-09-05 14:18:35.76 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2005-09-05 14:18:35.78 server Attempting to initialize Distributed Transaction Coordinator.
2005-09-05 14:18:37.23 spid3 Warning ******************
2005-09-05 14:18:37.23 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2005-09-05 14:18:37.25 spid3 Starting up database 'master'.
2005-09-05 14:18:37.73 spid3 Server name is 'SBN023770'.
2005-09-05 14:18:37.74 server Using 'SSNETLIB.DLL' version '8.0.311'.
2005-09-05 14:18:37.74 spid5 Starting up database 'model'.
2005-09-05 14:18:37.74 spid7 Starting up database 'msdb'.
2005-09-05 14:18:37.74 spid8 Starting up database 'pubs'.
2005-09-05 14:18:37.74 spid9 Starting up database 'Northwind'.
2005-09-05 14:18:38.07 spid5 Clearing tempdb database.
2005-09-05 14:18:38.15 server SQL server listening on 10.30.237.70: 1433.
2005-09-05 14:18:38.15 server SQL server listening on 127.0.0.1: 1433.
2005-09-05 14:18:38.61 spid5 Starting up database 'tempdb'.
2005-09-05 14:18:38.71 spid3 Recovery complete.
2005-09-05 14:18:38.72 spid3 Warning: override, autoexec procedures skipped.
2005-09-05 14:23:32.16 server SQL server listening on TCP, Shared Memory, Named Pipes.
2005-09-05 14:23:32.16 server SQL Server is ready for client connections
2005-09-05 14:23:37.04 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
As you see, there's a 5 minute delay from 14:18:38.72 to 14:23:32.16 before SQL Server is eventually listening. I believe the SQL configuration utility is meanwhile trying to start the SQL Agent service, and this is failing with a time out (1053).
We have a 120 of these remote servers to build, and quite a few are failing.
Anyone any ideas?
14:18:35 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 196814 -U sa -P
###############################################################################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occurred while attempting to start the service (1053)
SQL Server configuration failed.
###############################################################################
14:23:31 Process Exit Code: (-1)
14:23:31 Setup failed to configure the server. Refer to the server error logs and C:\WINDOWS\sqlstp.log for more information.
The error log for SQL is thus:
2005-09-05 14:18:35.67 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2005-09-05 14:18:35.68 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-09-05 14:18:35.68 server All rights reserved.
2005-09-05 14:18:35.68 server Server Process ID is 3412.
2005-09-05 14:18:35.68 server Logging SQL Server messages in file 'E:\MSSQL\log\ERRORLOG'.
2005-09-05 14:18:35.69 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2005-09-05 14:18:35.75 server SQL Server configured for thread mode processing.
2005-09-05 14:18:35.76 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2005-09-05 14:18:35.78 server Attempting to initialize Distributed Transaction Coordinator.
2005-09-05 14:18:37.23 spid3 Warning ******************
2005-09-05 14:18:37.23 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2005-09-05 14:18:37.25 spid3 Starting up database 'master'.
2005-09-05 14:18:37.73 spid3 Server name is 'SBN023770'.
2005-09-05 14:18:37.74 server Using 'SSNETLIB.DLL' version '8.0.311'.
2005-09-05 14:18:37.74 spid5 Starting up database 'model'.
2005-09-05 14:18:37.74 spid7 Starting up database 'msdb'.
2005-09-05 14:18:37.74 spid8 Starting up database 'pubs'.
2005-09-05 14:18:37.74 spid9 Starting up database 'Northwind'.
2005-09-05 14:18:38.07 spid5 Clearing tempdb database.
2005-09-05 14:18:38.15 server SQL server listening on 10.30.237.70: 1433.
2005-09-05 14:18:38.15 server SQL server listening on 127.0.0.1: 1433.
2005-09-05 14:18:38.61 spid5 Starting up database 'tempdb'.
2005-09-05 14:18:38.71 spid3 Recovery complete.
2005-09-05 14:18:38.72 spid3 Warning: override, autoexec procedures skipped.
2005-09-05 14:23:32.16 server SQL server listening on TCP, Shared Memory, Named Pipes.
2005-09-05 14:23:32.16 server SQL Server is ready for client connections
2005-09-05 14:23:37.04 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
As you see, there's a 5 minute delay from 14:18:38.72 to 14:23:32.16 before SQL Server is eventually listening. I believe the SQL configuration utility is meanwhile trying to start the SQL Agent service, and this is failing with a time out (1053).
We have a 120 of these remote servers to build, and quite a few are failing.
Anyone any ideas?