Probs on installing SQLSERVER2000 on Win 2003

[appi]

Hi all,

I just try to install an SQL-Server on a Win2003 Box.
The Installation went fine if I only install the default Instance.
If I try to install with a named Instance (Called sms) the installation process failed with the following error stack:

Starting Service ...

SQL_Latin1_General_CP1_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=AGNW2K40\SMS;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).

driver={sql server};server=AGNW2K40\SMS;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).

driver={sql server};server=AGNW2K40\SMS;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).

SQL Server configuration failed.

Why does it will not be possible top install this instance ?
This Instance was created before on a Win2000 Box.
kind regards
Uwe

 

[yelworcm]

Is there a local firewall, or some port blocking software involved? Also, is port 1434 blocked at teh switch this sever is hooked up to?

 

[appi]

Nop, there's no active local Firewall. If I try to get the default Instance it works fine. Only If I try to take an Instance called SMS or sms.
But we have tis Instance running inside a Win 2000 Box.

rgds
Uwe

 

[mrdenny]

Windows is killing your access to the SQL Server. Known issue with SQL 2000 on Windows 2003.

Before installing the named instance do the following.

Open the client network utility (Start > Programs > Microsoft SQL Server).
Alias tab.
Add
Server Alias = ServerName\SMS
Select Named Piped
Server Name = ServerName\SMS
Don't change the Pape Name

Install SQL
Patch to SP3a or higher
Remove the Server Alias from the Client Network Utility

The problem is that Windows 2003 doesn't allow access to the SQL Server over TCP/IP until it's patched to SP3 or higher. Because it's a named instance you have to connect over TCP/IP while installing. By adding the alian to the CNU you are forcing the connection to go over Net Bios which stays open.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[appi]

Thanks Danny,
I thought to have upgraded to SP3a, but it was still RTM. So I try ones again to install the named instance (if neccesary). By now we're working with the default instance. Seems like the Software which work on that DB could handle it.

regards
Uwe