SQL Server 2K configuration failed - setup failed

SQL Server 2K configuration failed - setup failed

Post by Michael Farbe » Tue, 19 Nov 2002 06:37:48



Greetings!

I have been having this nagging problem with SQL Server
2000 Enterprise Evaluation Edition setup procedure.
While finishing setup at the end, the setup Wizard is
trying to connect to SQL Server to configure it. After
some waiting period (about 30 seconds), the error message
pops up saying:
"Setup failed to configure the server. Refer to the server
error logs at D:\WINNT\sqlstp.log for more information."
And here is the extract from this sqlstp.log file where
this problem has been described.

###########################################################

Starting Service ...

SQL_Latin1_General_CP1_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql
server};server=MICHAEL;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection
broken.

[Microsoft][ODBC SQL Server Driver][Named Pipes]
ConnectionRead (GetOverLappedResult()).

driver={sql
server};server=MICHAEL;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection
broken.

[Microsoft][ODBC SQL Server Driver][Named Pipes]
ConnectionRead (GetOverLappedResult()).

driver={sql
server};server=MICHAEL;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection
broken.

[Microsoft][ODBC SQL Server Driver][Named Pipes]
ConnectionRead (ReadFile()).

SQL Server configuration failed.

21:33:22 Process Exit Code: (-1)
21:35:16 Setup failed to configure the server.   Refer to
the server error logs and D:\WINNT\sqlstp.log for more

information.
21:35:16 Action CleanUpInstall:
21:35:16 D:\WINNT\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -
Action 4 -Service SQLSERVERAGENT
21:35:16 Process Exit Code: (1060) The specified service
does not exist as an installed service.

21:35:16 D:\WINNT\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -
Action 4 -Service MSSQLSERVER
21:35:16 Process Exit Code: (0)
21:35:16 StatsGenerate returned: 2
21:35:16 StatsGenerate
(0x0,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
21:35:16 StatsGenerate -1,Michael Farber)
21:35:16 Installation Failed.

###########################################################

As you can see my computer name is "Michael". I selected
Windows Domain account that was "Michael Farber"
Why was the connection kept broken in several attempts
using [Microsoft][ODBC SQL Server Driver][Named
Pipes]? By the way I installed the latest version of MDAC
2.7. My O/S is Windows 2000 Professional, which is
compatible with this version of SQL Server 2K. I am trying
to install this version of SQL Server 2K on a
stand-alone computer that is not connected to any LAN
except to Internet through satellite modem setup.
I did stop IIS 5 Server before installation. I disabled my
antivirus protection and the screen saver as it was said
in preinstallation steps on MS site.
Besides the above sqlstp.log file, I found another
ERRORLOG file located in D:\Program Files\Microsoft SQL
Server\MSSQL\log\ERRORLOG'.
Here is the most important extract of that file where the
configuration has failed:

###########################################################
############

2002-11-13 21:32:51.98 server    Microsoft SQL Server  
2000 - 8.00.194 (Intel X86)
        Aug  6 2000 00:57:48
        Copyright (c) 1988-2000 Microsoft Corporation
        Enterprise Evaluation Edition on Windows NT 5.0
(Build 2195: Service Pack 2)

2002-11-13 21:32:52.02 server    Copyright (C) 1988-2000
Microsoft Corporation.
2002-11-13 21:32:52.02 server    All rights reserved.
2002-11-13 21:32:52.02 server    Server Process ID is 1544.
2002-11-13 21:32:52.02 server    Logging SQL Server
messages in file 'D:\Program Files\Microsoft SQL

Server\MSSQL\log\ERRORLOG'.
2002-11-13 21:32:52.04 server    SQL Server is starting at
priority class 'normal'(1 CPU detected).
2002-11-13 21:32:52.16 server    SQL Server configured for
thread mode processing.
2002-11-13 21:32:52.19 server    Using dynamic lock
allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2002-11-13 21:32:52.30 server    Attempting to initialize
Distributed Transaction Coordinator.
2002-11-13 21:32:52.68 server    Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2002-11-13 21:32:52.70 spid3     Warning ******************
2002-11-13 21:32:52.71 spid3     SQL Server started in
single user mode. Updates allowed to system catalogs.
2002-11-13 21:32:52.72 spid3     Starting up
database 'master'.
2002-11-13 21:32:53.15 spid3     Server name is 'MICHAEL'.
2002-11-13 21:32:53.15 server    Using 'SSNETLIB.DLL'
version '8.0.194'.
2002-11-13 21:32:53.15 spid5     Starting up
database 'model'.
2002-11-13 21:32:53.15 spid7     Starting up
database 'msdb'.
2002-11-13 21:32:53.16 spid8     Starting up
database 'pubs'.
2002-11-13 21:32:53.16 spid9     Starting up
database 'Northwind'.
2002-11-13 21:32:53.81 spid5     Clearing tempdb database.
2002-11-13 21:32:56.40 spid5     Starting up
database 'tempdb'.
2002-11-13 21:32:56.52 spid3     Recovery complete.
2002-11-13 21:32:56.54 spid3     Warning: override,
autoexec procedures skipped.
2002-11-13 21:32:58.24 server    SQL server listening on
TCP, Shared Memory, Named Pipes.
2002-11-13 21:32:58.24 server    SQL server listening on
10.111.49.130:1433, 127.0.0.1:1433.
2002-11-13 21:32:58.24 server    SQL Server is ready for
client connections
2002-11-13 21:33:07.43 spid3     SQL Server is terminating
due to 'stop' request from Service Control Manager.

###########################################################

I tried to use the PING command with 10.111.49.130 and
127.0.0.1 IP's and had a successful connection.
However, when I added ":1433" port to the IP address,
there was the error message saying "Unknown host
127.0.0.1:1433" Why is the server trying to find this
port :1433 that I don't have or hasn't been setup?
Do I need a NIC card? It should work on a stand-alone
machine also.
I am not a system administrator. I guess this problem
could be easily solved by Windows 2K system
administrator knowledgeable how to configure the
environment for this type of installation.
I did use system administration account with all rights.
Please any system administrator, help me. I will be very
grateful for any thoughts and advises.
I badly need SQL Server 2K running at home when I work
from home developing some applications based on SQL
Server 2K stored procedures and ASP pages.
Thank you very much in advance!

Michael.  

 
 
 

SQL Server 2K configuration failed - setup failed

Post by Steve Park » Wed, 20 Nov 2002 13:26:39


You might want to try installing MDAC separately, then go
back and install SQL.  For SQL Server 2000 use MDAC 2.5 or
2.6 I think.  For SQL 7 use MDAC 2.1.  

Also try MS KB Article 305680 for more hints on cnfgsvr.exe

Also, make sure both the C and D drive allow FULL CONTROL
permissions for the SYSTEM account.  

Quote:>-----Original Message-----
>Greetings!

>I have been having this nagging problem with SQL Server
>2000 Enterprise Evaluation Edition setup procedure.
>While finishing setup at the end, the setup Wizard is
>trying to connect to SQL Server to configure it. After
>some waiting period (about 30 seconds), the error message
>pops up saying:
>"Setup failed to configure the server. Refer to the
server
>error logs at D:\WINNT\sqlstp.log for more information."
>And here is the extract from this sqlstp.log file where
>this problem has been described.

>##########################################################
#

>Starting Service ...

>SQL_Latin1_General_CP1_CI_AS

>-m -Q -T4022 -T3659

>Connecting to Server ...

>driver={sql
>server};server=MICHAEL;UID=sa;PWD=;database=master

>[Microsoft][ODBC SQL Server Driver][Named Pipes]
Connection
>broken.

>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>ConnectionRead (GetOverLappedResult()).

>driver={sql
>server};server=MICHAEL;UID=sa;PWD=;database=master

>[Microsoft][ODBC SQL Server Driver][Named Pipes]
Connection
>broken.

>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>ConnectionRead (GetOverLappedResult()).

>driver={sql
>server};server=MICHAEL;UID=sa;PWD=;database=master

>[Microsoft][ODBC SQL Server Driver][Named Pipes]
Connection
>broken.

>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>ConnectionRead (ReadFile()).

>SQL Server configuration failed.

>21:33:22 Process Exit Code: (-1)
>21:35:16 Setup failed to configure the server.   Refer to
>the server error logs and D:\WINNT\sqlstp.log for more

>information.
>21:35:16 Action CleanUpInstall:
>21:35:16 D:\WINNT\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -
>Action 4 -Service SQLSERVERAGENT
>21:35:16 Process Exit Code: (1060) The specified service
>does not exist as an installed service.

>21:35:16 D:\WINNT\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -
>Action 4 -Service MSSQLSERVER
>21:35:16 Process Exit Code: (0)
>21:35:16 StatsGenerate returned: 2
>21:35:16 StatsGenerate
>(0x0,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
>21:35:16 StatsGenerate -1,Michael Farber)
>21:35:16 Installation Failed.

>##########################################################
#

>As you can see my computer name is "Michael". I selected
>Windows Domain account that was "Michael Farber"
>Why was the connection kept broken in several attempts
>using [Microsoft][ODBC SQL Server Driver][Named
>Pipes]? By the way I installed the latest version of MDAC
>2.7. My O/S is Windows 2000 Professional, which is
>compatible with this version of SQL Server 2K. I am
trying
>to install this version of SQL Server 2K on a
>stand-alone computer that is not connected to any LAN
>except to Internet through satellite modem setup.
>I did stop IIS 5 Server before installation. I disabled
my
>antivirus protection and the screen saver as it was said
>in preinstallation steps on MS site.
>Besides the above sqlstp.log file, I found another
>ERRORLOG file located in D:\Program Files\Microsoft SQL
>Server\MSSQL\log\ERRORLOG'.
>Here is the most important extract of that file where the
>configuration has failed:

>##########################################################
#
>############

>2002-11-13 21:32:51.98 server    Microsoft SQL Server  
>2000 - 8.00.194 (Intel X86)
>    Aug  6 2000 00:57:48
>    Copyright (c) 1988-2000 Microsoft Corporation
>    Enterprise Evaluation Edition on Windows NT 5.0
>(Build 2195: Service Pack 2)

>2002-11-13 21:32:52.02 server    Copyright (C) 1988-2000
>Microsoft Corporation.
>2002-11-13 21:32:52.02 server    All rights reserved.
>2002-11-13 21:32:52.02 server    Server Process ID is
1544.
>2002-11-13 21:32:52.02 server    Logging SQL Server
>messages in file 'D:\Program Files\Microsoft SQL

>Server\MSSQL\log\ERRORLOG'.
>2002-11-13 21:32:52.04 server    SQL Server is starting
at
>priority class 'normal'(1 CPU detected).
>2002-11-13 21:32:52.16 server    SQL Server configured
for
>thread mode processing.
>2002-11-13 21:32:52.19 server    Using dynamic lock
>allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
>2002-11-13 21:32:52.30 server    Attempting to initialize
>Distributed Transaction Coordinator.
>2002-11-13 21:32:52.68 server    Failed to obtain
>TransactionDispenserInterface: Result Code = 0x8004d01b
>2002-11-13 21:32:52.70 spid3     Warning
******************
>2002-11-13 21:32:52.71 spid3     SQL Server started in
>single user mode. Updates allowed to system catalogs.
>2002-11-13 21:32:52.72 spid3     Starting up
>database 'master'.
>2002-11-13 21:32:53.15 spid3     Server name is 'MICHAEL'.
>2002-11-13 21:32:53.15 server    Using 'SSNETLIB.DLL'
>version '8.0.194'.
>2002-11-13 21:32:53.15 spid5     Starting up
>database 'model'.
>2002-11-13 21:32:53.15 spid7     Starting up
>database 'msdb'.
>2002-11-13 21:32:53.16 spid8     Starting up
>database 'pubs'.
>2002-11-13 21:32:53.16 spid9     Starting up
>database 'Northwind'.
>2002-11-13 21:32:53.81 spid5     Clearing tempdb database.
>2002-11-13 21:32:56.40 spid5     Starting up
>database 'tempdb'.
>2002-11-13 21:32:56.52 spid3     Recovery complete.
>2002-11-13 21:32:56.54 spid3     Warning: override,
>autoexec procedures skipped.
>2002-11-13 21:32:58.24 server    SQL server listening on
>TCP, Shared Memory, Named Pipes.
>2002-11-13 21:32:58.24 server    SQL server listening on
>10.111.49.130:1433, 127.0.0.1:1433.
>2002-11-13 21:32:58.24 server    SQL Server is ready for
>client connections
>2002-11-13 21:33:07.43 spid3     SQL Server is
terminating
>due to 'stop' request from Service Control Manager.

>##########################################################
#

>I tried to use the PING command with 10.111.49.130 and
>127.0.0.1 IP's and had a successful connection.
>However, when I added ":1433" port to the IP address,
>there was the error message saying "Unknown host
>127.0.0.1:1433" Why is the server trying to find this
>port :1433 that I don't have or hasn't been setup?
>Do I need a NIC card? It should work on a stand-alone
>machine also.
>I am not a system administrator. I guess this problem
>could be easily solved by Windows 2K system
>administrator knowledgeable how to configure the
>environment for this type of installation.
>I did use system administration account with all rights.
>Please any system administrator, help me. I will be very
>grateful for any thoughts and advises.
>I badly need SQL Server 2K running at home when I work
>from home developing some applications based on SQL
>Server 2K stored procedures and ASP pages.
>Thank you very much in advance!

>Michael.  

>.


 
 
 

SQL Server 2K configuration failed - setup failed

Post by Michae » Mon, 25 Nov 2002 07:03:23


Thanks for reply. However, I've tried everything,
installing MDAC separately, using local computer account
and Widows Domain account, nothing worked. I use
Administrator account (not the account having
administration rights) when installing SQL Server 2000,
didn't help. I found article 302409 in MS KB concerning
Certificate Authority (CA) with their key and the host
name being the same could prevent installing SQL Server
2K. I removed CA from the system and tried to install SQL
Server, still the same problem. So, that also didn't help.
I really ran out of options. I still think it must have
something to do with ports and with special network setup
for stand along computer because SQL server is trying to
connect through 10.111.49.130:1433, 127.0.0.1:1433 using
Named Pipes. If it can't find this port, the connection is
broken.
Thank you!
Michael

>-----Original Message-----
>You might want to try installing MDAC separately, then go
>back and install SQL.  For SQL Server 2000 use MDAC 2.5
or
>2.6 I think.  For SQL 7 use MDAC 2.1.  

>Also try MS KB Article 305680 for more hints on
cnfgsvr.exe

>Also, make sure both the C and D drive allow FULL CONTROL
>permissions for the SYSTEM account.  

>>-----Original Message-----
>>Greetings!

>>I have been having this nagging problem with SQL Server
>>2000 Enterprise Evaluation Edition setup procedure.
>>While finishing setup at the end, the setup Wizard is
>>trying to connect to SQL Server to configure it. After
>>some waiting period (about 30 seconds), the error
message
>>pops up saying:
>>"Setup failed to configure the server. Refer to the
>server
>>error logs at D:\WINNT\sqlstp.log for more information."
>>And here is the extract from this sqlstp.log file where
>>this problem has been described.

>>#########################################################
#
>#

>>Starting Service ...

>>SQL_Latin1_General_CP1_CI_AS

>>-m -Q -T4022 -T3659

>>Connecting to Server ...

>>driver={sql
>>server};server=MICHAEL;UID=sa;PWD=;database=master

>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>Connection
>>broken.

>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>>ConnectionRead (GetOverLappedResult()).

>>driver={sql
>>server};server=MICHAEL;UID=sa;PWD=;database=master

>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>Connection
>>broken.

>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>>ConnectionRead (GetOverLappedResult()).

>>driver={sql
>>server};server=MICHAEL;UID=sa;PWD=;database=master

>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>Connection
>>broken.

>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>>ConnectionRead (ReadFile()).

>>SQL Server configuration failed.

>>21:33:22 Process Exit Code: (-1)
>>21:35:16 Setup failed to configure the server.   Refer
to
>>the server error logs and D:\WINNT\sqlstp.log for more

>>information.
>>21:35:16 Action CleanUpInstall:
>>21:35:16 D:\WINNT\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -
>>Action 4 -Service SQLSERVERAGENT
>>21:35:16 Process Exit Code: (1060) The specified service
>>does not exist as an installed service.

>>21:35:16 D:\WINNT\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -
>>Action 4 -Service MSSQLSERVER
>>21:35:16 Process Exit Code: (0)
>>21:35:16 StatsGenerate returned: 2
>>21:35:16 StatsGenerate
>>(0x0,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
>>21:35:16 StatsGenerate -1,Michael Farber)
>>21:35:16 Installation Failed.

>>#########################################################
#
>#

>>As you can see my computer name is "Michael". I selected
>>Windows Domain account that was "Michael Farber"
>>Why was the connection kept broken in several attempts
>>using [Microsoft][ODBC SQL Server Driver][Named
>>Pipes]? By the way I installed the latest version of
MDAC
>>2.7. My O/S is Windows 2000 Professional, which is
>>compatible with this version of SQL Server 2K. I am
>trying
>>to install this version of SQL Server 2K on a
>>stand-alone computer that is not connected to any LAN
>>except to Internet through satellite modem setup.
>>I did stop IIS 5 Server before installation. I disabled
>my
>>antivirus protection and the screen saver as it was said
>>in preinstallation steps on MS site.
>>Besides the above sqlstp.log file, I found another
>>ERRORLOG file located in D:\Program Files\Microsoft SQL
>>Server\MSSQL\log\ERRORLOG'.
>>Here is the most important extract of that file where
the
>>configuration has failed:

>>#########################################################
#
>#
>>############

>>2002-11-13 21:32:51.98 server    Microsoft SQL Server  
>>2000 - 8.00.194 (Intel X86)
>>        Aug  6 2000 00:57:48
>>        Copyright (c) 1988-2000 Microsoft Corporation
>>        Enterprise Evaluation Edition on Windows NT 5.0
>>(Build 2195: Service Pack 2)

>>2002-11-13 21:32:52.02 server    Copyright (C) 1988-2000
>>Microsoft Corporation.
>>2002-11-13 21:32:52.02 server    All rights reserved.
>>2002-11-13 21:32:52.02 server    Server Process ID is
>1544.
>>2002-11-13 21:32:52.02 server    Logging SQL Server
>>messages in file 'D:\Program Files\Microsoft SQL

>>Server\MSSQL\log\ERRORLOG'.
>>2002-11-13 21:32:52.04 server    SQL Server is starting
>at
>>priority class 'normal'(1 CPU detected).
>>2002-11-13 21:32:52.16 server    SQL Server configured
>for
>>thread mode processing.
>>2002-11-13 21:32:52.19 server    Using dynamic lock
>>allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
>>2002-11-13 21:32:52.30 server    Attempting to
initialize
>>Distributed Transaction Coordinator.
>>2002-11-13 21:32:52.68 server    Failed to obtain
>>TransactionDispenserInterface: Result Code = 0x8004d01b
>>2002-11-13 21:32:52.70 spid3     Warning
>******************
>>2002-11-13 21:32:52.71 spid3     SQL Server started in
>>single user mode. Updates allowed to system catalogs.
>>2002-11-13 21:32:52.72 spid3     Starting up
>>database 'master'.
>>2002-11-13 21:32:53.15 spid3     Server name
is 'MICHAEL'.
>>2002-11-13 21:32:53.15 server    Using 'SSNETLIB.DLL'
>>version '8.0.194'.
>>2002-11-13 21:32:53.15 spid5     Starting up
>>database 'model'.
>>2002-11-13 21:32:53.15 spid7     Starting up
>>database 'msdb'.
>>2002-11-13 21:32:53.16 spid8     Starting up
>>database 'pubs'.
>>2002-11-13 21:32:53.16 spid9     Starting up
>>database 'Northwind'.
>>2002-11-13 21:32:53.81 spid5     Clearing tempdb
database.
>>2002-11-13 21:32:56.40 spid5     Starting up
>>database 'tempdb'.
>>2002-11-13 21:32:56.52 spid3     Recovery complete.
>>2002-11-13 21:32:56.54 spid3     Warning: override,
>>autoexec procedures skipped.
>>2002-11-13 21:32:58.24 server    SQL server listening on
>>TCP, Shared Memory, Named Pipes.
>>2002-11-13 21:32:58.24 server    SQL server listening on
>>10.111.49.130:1433, 127.0.0.1:1433.
>>2002-11-13 21:32:58.24 server    SQL Server is ready for
>>client connections
>>2002-11-13 21:33:07.43 spid3     SQL Server is
>terminating
>>due to 'stop' request from Service Control Manager.

>>#########################################################
#
>#

>>I tried to use the PING command with 10.111.49.130 and
>>127.0.0.1 IP's and had a successful connection.
>>However, when I added ":1433" port to the IP address,
>>there was the error message saying "Unknown host
>>127.0.0.1:1433" Why is the server trying to find this
>>port :1433 that I don't have or hasn't been setup?
>>Do I need a NIC card? It should work on a stand-alone
>>machine also.
>>I am not a system administrator. I guess this problem
>>could be easily solved by Windows 2K system
>>administrator knowledgeable how to configure the
>>environment for this type of installation.
>>I did use system administration account with all rights.
>>Please any system administrator, help me. I will be very
>>grateful for any thoughts and advises.
>>I badly need SQL Server 2K running at home when I work
>>from home developing some applications based on SQL
>>Server 2K stored procedures and ASP pages.
>>Thank you very much in advance!

>>Michael.  

>>.

>.

 
 
 

SQL Server 2K configuration failed - setup failed

Post by Ursul » Tue, 21 Jan 2003 10:17:08


Michael,

I seem to be having the same problem you described. Did
you ever find a resolution?

It's definitely a machine-specific problem. I've been able
to install SQL2K on two different machines (one with
Win2K, the other with WinXP) with no problem whatsoever.
But when I try to install it on this third machine (also
Win2K), I get the same error message you did:

"Setup failed to configure the server. Refer to the server
error logs at D:\WINNT\sqlstp.log for more information."

Everything seems to install just fine, right up to the
very end -- then nothin'!

Has anyone else experienced this? Or discovered a
workaround/fix for it?

Desperate-to-finish-app-in-2-days,

Ursula

>-----Original Message-----
>Thanks for reply. However, I've tried everything,
>installing MDAC separately, using local computer account
>and Widows Domain account, nothing worked. I use
>Administrator account (not the account having
>administration rights) when installing SQL Server 2000,
>didn't help. I found article 302409 in MS KB concerning
>Certificate Authority (CA) with their key and the host
>name being the same could prevent installing SQL Server
>2K. I removed CA from the system and tried to install SQL
>Server, still the same problem. So, that also didn't help.
>I really ran out of options. I still think it must have
>something to do with ports and with special network setup
>for stand along computer because SQL server is trying to
>connect through 10.111.49.130:1433, 127.0.0.1:1433 using
>Named Pipes. If it can't find this port, the connection
is
>broken.
>Thank you!
>Michael

>>-----Original Message-----
>>You might want to try installing MDAC separately, then
go
>>back and install SQL.  For SQL Server 2000 use MDAC 2.5
>or
>>2.6 I think.  For SQL 7 use MDAC 2.1.  

>>Also try MS KB Article 305680 for more hints on
>cnfgsvr.exe

>>Also, make sure both the C and D drive allow FULL
CONTROL
>>permissions for the SYSTEM account.  

>>>-----Original Message-----
>>>Greetings!

>>>I have been having this nagging problem with SQL Server
>>>2000 Enterprise Evaluation Edition setup procedure.
>>>While finishing setup at the end, the setup Wizard is
>>>trying to connect to SQL Server to configure it. After
>>>some waiting period (about 30 seconds), the error
>message
>>>pops up saying:
>>>"Setup failed to configure the server. Refer to the
>>server
>>>error logs at D:\WINNT\sqlstp.log for more information."
>>>And here is the extract from this sqlstp.log file where
>>>this problem has been described.

>>>########################################################
#
>#
>>#

>>>Starting Service ...

>>>SQL_Latin1_General_CP1_CI_AS

>>>-m -Q -T4022 -T3659

>>>Connecting to Server ...

>>>driver={sql
>>>server};server=MICHAEL;UID=sa;PWD=;database=master

>>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>>Connection
>>>broken.

>>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>>>ConnectionRead (GetOverLappedResult()).

>>>driver={sql
>>>server};server=MICHAEL;UID=sa;PWD=;database=master

>>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>>Connection
>>>broken.

>>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>>>ConnectionRead (GetOverLappedResult()).

>>>driver={sql
>>>server};server=MICHAEL;UID=sa;PWD=;database=master

>>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>>Connection
>>>broken.

>>>[Microsoft][ODBC SQL Server Driver][Named Pipes]
>>>ConnectionRead (ReadFile()).

>>>SQL Server configuration failed.

>>>21:33:22 Process Exit Code: (-1)
>>>21:35:16 Setup failed to configure the server.   Refer
>to
>>>the server error logs and D:\WINNT\sqlstp.log for more

>>>information.
>>>21:35:16 Action CleanUpInstall:
>>>21:35:16 D:\WINNT\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -
>>>Action 4 -Service SQLSERVERAGENT
>>>21:35:16 Process Exit Code: (1060) The specified
service
>>>does not exist as an installed service.

>>>21:35:16 D:\WINNT\TEMP\SqlSetup\Bin\scm.exe  -Silent 1 -
>>>Action 4 -Service MSSQLSERVER
>>>21:35:16 Process Exit Code: (0)
>>>21:35:16 StatsGenerate returned: 2
>>>21:35:16 StatsGenerate
>>>(0x0,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
>>>21:35:16 StatsGenerate -1,Michael Farber)
>>>21:35:16 Installation Failed.

>>>########################################################
#
>#
>>#

>>>As you can see my computer name is "Michael". I
selected
>>>Windows Domain account that was "Michael Farber"
>>>Why was the connection kept broken in several attempts
>>>using [Microsoft][ODBC SQL Server Driver][Named
>>>Pipes]? By the way I installed the latest version of
>MDAC
>>>2.7. My O/S is Windows 2000 Professional, which is
>>>compatible with this version of SQL Server 2K. I am
>>trying
>>>to install this version of SQL Server 2K on a
>>>stand-alone computer that is not connected to any LAN
>>>except to Internet through satellite modem setup.
>>>I did stop IIS 5 Server before installation. I disabled
>>my
>>>antivirus protection and the screen saver as it was
said
>>>in preinstallation steps on MS site.
>>>Besides the above sqlstp.log file, I found another
>>>ERRORLOG file located in D:\Program Files\Microsoft SQL
>>>Server\MSSQL\log\ERRORLOG'.
>>>Here is the most important extract of that file where
>the
>>>configuration has failed:

>>>########################################################
#
>#
>>#
>>>############

>>>2002-11-13 21:32:51.98 server    Microsoft SQL Server  
>>>2000 - 8.00.194 (Intel X86)
>>>    Aug  6 2000 00:57:48
>>>    Copyright (c) 1988-2000 Microsoft Corporation
>>>    Enterprise Evaluation Edition on Windows NT 5.0
>>>(Build 2195: Service Pack 2)

>>>2002-11-13 21:32:52.02 server    Copyright (C) 1988-
2000
>>>Microsoft Corporation.
>>>2002-11-13 21:32:52.02 server    All rights reserved.
>>>2002-11-13 21:32:52.02 server    Server Process ID is
>>1544.
>>>2002-11-13 21:32:52.02 server    Logging SQL Server
>>>messages in file 'D:\Program Files\Microsoft SQL

>>>Server\MSSQL\log\ERRORLOG'.
>>>2002-11-13 21:32:52.04 server    SQL Server is starting
>>at
>>>priority class 'normal'(1 CPU detected).
>>>2002-11-13 21:32:52.16 server    SQL Server configured
>>for
>>>thread mode processing.
>>>2002-11-13 21:32:52.19 server    Using dynamic lock
>>>allocation. [2500] Lock Blocks, [5000] Lock Owner
Blocks.
>>>2002-11-13 21:32:52.30 server    Attempting to
>initialize
>>>Distributed Transaction Coordinator.
>>>2002-11-13 21:32:52.68 server    Failed to obtain
>>>TransactionDispenserInterface: Result Code = 0x8004d01b
>>>2002-11-13 21:32:52.70 spid3     Warning
>>******************
>>>2002-11-13 21:32:52.71 spid3     SQL Server started in
>>>single user mode. Updates allowed to system catalogs.
>>>2002-11-13 21:32:52.72 spid3     Starting up
>>>database 'master'.
>>>2002-11-13 21:32:53.15 spid3     Server name
>is 'MICHAEL'.
>>>2002-11-13 21:32:53.15 server    Using 'SSNETLIB.DLL'
>>>version '8.0.194'.
>>>2002-11-13 21:32:53.15 spid5     Starting up
>>>database 'model'.
>>>2002-11-13 21:32:53.15 spid7     Starting up
>>>database 'msdb'.
>>>2002-11-13 21:32:53.16 spid8     Starting up
>>>database 'pubs'.
>>>2002-11-13 21:32:53.16 spid9     Starting up
>>>database 'Northwind'.
>>>2002-11-13 21:32:53.81 spid5     Clearing tempdb
>database.
>>>2002-11-13 21:32:56.40 spid5     Starting up
>>>database 'tempdb'.
>>>2002-11-13 21:32:56.52 spid3     Recovery complete.
>>>2002-11-13 21:32:56.54 spid3     Warning: override,
>>>autoexec procedures skipped.
>>>2002-11-13 21:32:58.24 server    SQL server listening
on
>>>TCP, Shared Memory, Named Pipes.
>>>2002-11-13 21:32:58.24 server    SQL server listening
on
>>>10.111.49.130:1433, 127.0.0.1:1433.
>>>2002-11-13 21:32:58.24 server    SQL Server is ready
for
>>>client connections
>>>2002-11-13 21:33:07.43 spid3     SQL Server is
>>terminating
>>>due to 'stop' request from Service Control Manager.

>>>########################################################
#
>#
>>#

>>>I tried to use the PING command with 10.111.49.130 and
>>>127.0.0.1 IP's and had a successful connection.
>>>However, when I added ":1433" port to the IP address,
>>>there was the error message saying "Unknown host
>>>127.0.0.1:1433" Why is the server trying to find this
>>>port :1433 that I don't have or hasn't been setup?
>>>Do I need a NIC card? It should work on a stand-alone
>>>machine also.
>>>I am not a system administrator. I guess this problem
>>>could be easily solved by Windows 2K system
>>>administrator knowledgeable how to configure the
>>>environment for this type of installation.
>>>I did use system administration account with all rights.
>>>Please any system administrator, help me. I will be
very
>>>grateful for any thoughts and advises.
>>>I badly need SQL Server 2K running at home when I work
>>>from home developing some applications based on SQL
>>>Server 2K stored procedures and ASP pages.
>>>Thank you very much in advance!

>>>Michael.  

>>>.

>>.

>.