Installation.... Help!!!greenspun.com : LUSENET : SQL Server Database Administration : One Thread
Well I have tried several times, with no success, to install SQLServer 6.5..It gets all the way through and then says that "setup couldnot connect withsql server".....Any ideas......
Thanx for any help Mike
-- Anonymous, December 06, 1998
You can find more information about what went wrong during setup in the *.OUT files located in the \MSSQL\INSTALL directory.
The following advice comes from Neil Pike of Protech Computing Ltd.
Try the following check-list of things that could go wrong during install.
1. Make sure you have administrator level permissions on the machine in question, as SQL needs to create registry entries, services etc.
2. If you have tried to install SQL before then manually clean-up all the files/registry entries as follows :-
directory and everything under it Remove the dir from the path (use control panel/system for this) Remove the SQL registry entries using regedt32/regedit. These are :- (all versions) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer (6.x only) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SQLExecutive (7.x only) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SQLServerAgent (all versions) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
3. SQL Server is dependent on network functionality - even for the set-up routines. Specifically it needs to use named-pipe/mailslot functionality. These usually require a network card to be present. If you don't have a network card then go to control panel/networks, choose add adapter and then add the Microsoft loopback adapter - which is just a dummy driver, no hardware involved. This needs to have working network protocol(s) bound to it. Let whichever protocols you have use default parameters, EXCEPT for tcp-ip. If you are using this then do NOT specify dhcp assigned address, use 192.168.1.1 as the IP address and 255.255.255.0 as the subnet mask. This is a standard RFC1918 non-routed IP address so shouldn't clash with any dial-up address you may be given by an ISP.
4. Because a named-pipe, used by the set-up routine, is effectively a file as far as the operating system is concerned, real-time Virus scanners can cause problems. Most of these have been fixed, so make sure you're running the latest version. But if in doubt, then disable the virus software for the duration of the install.
5. Other software packages can also interfere with SQL's install - typically they interfere with named-pipes/mailslot connectivity and setup will terminate with an error like 'unable to write to mailslot.....'. Shut-down any of these for the duration of the install. Packages that are known to interfere with SQL's setup routines include :-
IIS - Internet Information Server - the web parts, not FTP PWS - Personal Web Server Exchange Server
6. If the dial-up networking icon/window appears and tries to make a network connection, then stop and disable the "Remote Access Autodial Manager" service via control panel/services. This is an NT issue rather than a SQL one, but disabling auto-dial is the easiest way around it.
-- Anonymous, December 07, 1998