| Squak Mountain Consulting, Inc. |
Fixing SQL Server 2000 Install Error:
|
|
Inside Microsoft SQL Server 2000 (With CD-ROM) |
SQL Server 2000 Fast Answers for DBAs and Developers |
Microsoft SQL Server 2000 Unleashed (2nd Edition) |
Microsoft SQL Server 2000 Resource Kit (With CD-ROM) |
Microsoft SQL Server 2000 Developer Edition |
Microsoft Visual Studio .NET Professional Upgrade |
Overview of the problem:
You're trying to install or
re-install SQL Server 2000.
The
install fails, and you find the below error in your C:\WINNT\sqlstp.log :
| Sample Error Log |
| 23:53:00 C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -I
MSSQLSERVER -V 1 -M 1 -Q "SQL_Latin1_General_CP1_CI_AS" -H 3605458 -U sa -P
############################################################################### Starting Service ... SQL_Latin1_General_CP1_CI_AS -m -Q -T4022-T3659 ConnectingtoServer... driver={sqlserver};server=TK;UID=sa;PWD=;database=master [Microsoft][ODBCSQLServerDriver][NamedPipes]Connectionbroken. [Microsoft][ODBCSQLServerDriver][NamedPipes]ConnectionRead(GetOverLappedResult()) .driver={sqlserver};server=TK;UID=sa;PWD=;database=master [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken. [Microsoft][ODBCSQLServerDriver][NamedPipes]ConnectionRead(GetOverLappedResult()) .driver={sqlserver};server=TK;UID=sa;PWD=;database=master [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken. [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead(GetOverLappedResult()). SQL Server configuration failed. ############################################################################### 23:53:47 Process Exit Code: (-1) 23:53:51 Setup failed to configure the server. Refer to the server error logs and C:\WINNT\sqlstp.log for more information. |
Explanation:
During install SQL Server 2000 is supposed to connect using in-memory
communications. If it uses anything else, like Named Pipes or TCP/IP, the
install fails.
The first line that contains "[NamedPipes]Connectionbroken" is our clue that
the install didn't use in-memory communication and that's why the install
failed.
The Fix:
The fix for this
problem is the following procedure:
1. Open a command
prompt and navigate to the directory where SQL Server setup.exe resides
2. Run setup
manually with the following command:
setup /qf /L*v setup.log REINSTALL=ALL
The really important part of
this command is the "REINSTALL=ALL" statement.
This tells setup to copy all the
files that are part of SQL Server 2000, even if they are already on the machine.
Setup's default behavior is to not copy any files that are already on the
machine.
Presumably, this fixes the problem because
some file that's already on the machine has been corrupted.
The "/qf"
parameter forces all the dialogs and prompts to be shown to you.
The "/L*v
setup.log" parameter creates a verbose log that might be helpful if
something goes wrong.
NOTE: If you're running this from CD, you'll have to point
your setup.log to a writable disk.
That's it. I hope it works for you as smoothly as it did for me.