It gets an error that the connection was refused. It works fine for a named instance.
Since all of the MSSQLServer registry entries are new, I don't think it is there. And all are done with the service Local Account. So I think the problem must be in the TCP/IP configuration referring to an old installation.
What is the problem? Is there a reference to all of these registry entries.
Thanks,
DavidIt's very difficult to provide you an answer given the information you provided. Are you trying to access the instance remotely or locally? By default, TCP is off. To turn on remote connectivity you can use either SQL Configuration Manager or SQL Server Surface Area Configuration Manager.
Dan
"This posting is provided "AS IS" with no warranties, and confers no rights"|||This occurs during the installation, so it is before the utilities are available. What communications method does the setup program use that can be refused. It is only refused for the default instance.|||Are you saying this works if you install a named instance? That's strange. Can you grab the log files from: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*.log. You can zip the files before attaching them.
Thanks,
Dan|||Hi David
Probably setup is finding an default instance in the machine. I suggest that you uninstall previous build using the command line:
Start /wait D:\SQLDEV_CTP4\setup.exe /qb REMOVE=ALL
Start /wait msiexec /qb /X D:\SQLDEV_CTP4\Setup\sqlncli.msi
Start /wait D:\SQLDEV_CTP4\redist\2.0\dotnetfx.exe /q:a /c:"install /qu"
where D:\SQLDEV_CTP4 is the way for which you it extracted the of setup files.
Another option is to use Build Uninstall Wizard (\Setup Tools\Build Uninstall Wizard),but still I think that command line is more efficient to remove one previous build.
regards
Nilton Pinheiro
|||Sorry to say, I've got this exact same situation, and the above doesn't fix the problem.
