by Thank you, Stefano.
I had the same symptoms as described by KKinsey. I checked with
cliconfg.exe and found out that there were still old aliases set (from
a prior install of SQL Server 2000). After removing the alias, it
installed flawless.
It's awesome. KKinsey wrote his question more then one year ago. I
wonder if he ever solved *his* problem. Anyway, your reply helpe *me*
now - some time later.
Google Group Rocks !!!
Thanks,
Godwin.
> %windir%\system32\cliconfg.exe
> Check if Shared Memory check and TCP protocol are enabled. Check also if you
> have aliases to the local server. If you do, delete them and try again.
>> I am running Windows 2000 SP 1. At the end of the installation
when it
>> tries to start and configure the server, I get the following
message, "Setup
>> failed to configure the server. Refer to the server error logs and
>> c:\winnt\sqlstp.log for more info."
>> Below is what I see at the end of the sqlstp.log file. Apparently
it
>> partially installed, but not the server portion, because I have a
Microsoft
>> SQL Server Program Group with about seven things listed. I can
start the
>> Enterprise Manager, drill down and see my server name, but I cannot
connect
>> to it. I tried to uninstall and remove all footsteps from the
registry
>> (suggested in some other posts I found), but this did not help.
Any other
>> suggestions??
>> *******************
>> Starting Service ...
>> SQL_Latin1_General_CP1_CI_AS
>> -m -Q -T4022 -T3659
>> Connecting to Server ...
>> driver={sql server};server=MyTestSvrName;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=MyTestSvrName;UID=sa;PWD=;database=master
>> [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.
>> [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead
(ReadFile()).
>> driver={sql server};server=MyTestSvrName;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.