PHWinfo - Afficher un message - Do SqlServer 2000 & SqlServer 2005 co-exist

31/10/2006, 04h40

Hello Cubicle,

I understand that you can connect to SQL 2000 named instance on the local
console of server. However, you cannot cannot it from client machines.

Since you installed SQL 2000 after 2005 instance, you may encounter the
known issue documented in the following article

905618 You may receive a connection error message when you try to connect
to an instance of SQL Server 2000 or of SQL Server 7.0 that was installed
after you installed SQL Server 2005
http://support.microsoft.com/default...b;EN-US;905618

You may want to test if above article fix the problem. When you have a
named instance of SQL Server 2000 that is running side-by-side with an
instance of SQL Server 2005 on the same computer, the SQL Server 2005
Browser service listens on UDP port 1434 for incoming requests for the
named instance of SQL Server 2000.

If the issue still occurs, it seems the instance was blocked by the
firewall. Going forward, I suggest that you try the following steps to
isolate the issue:

1. Click Start->ALL Programs->Microsoft SQL Server, run SQL 2000 Sever
network utility, select SQL 2000 server name (servername\instancename).

2. Make sure TCPIP and Named Pipes protocol are enabled

3. Select TCPIP, and click Properties, and set the port of the instance to
a fixed port such as 1500.

4. Restart SQL 2000 named instance.

5. Run "Client Network utility" on the server, on Alias type, add a alias
such as test, select TCPIP, type the server computer name in Server name.

6. Check if you could connect to Alias on the local server.

7. If you have firewall enabled on your computer, please open the port.
Please note, in Win2003 sp1, you could configure Windows firewall in the
Control Panel. Please refer to the following article as I mentioned for
details.

INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/kb/287932

8. Run "Client Network utility" on the client machine, and create Alias as
described in setp 5. If you encounter any problem from this step, you may
want to use "telnet <servername> 1500 to see if you could connect to the
port you configure from client machine.

If you encounter any error message, please let's know exact message.

More related information

922131 You cannot remotely connect to a named instance of SQL Server 2000
by using the TCP/IP protocol
http://support.microsoft.com/default...b;EN-US;922131

I look forward to your reply. Thanks.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

31/10/2006, 04h40	#5
Peter Yang [MSFT] Messages: n/a Hébergeur:	Re: Do SqlServer 2000 & SqlServer 2005 co-exist Hello Cubicle, I understand that you can connect to SQL 2000 named instance on the local console of server. However, you cannot cannot it from client machines. Since you installed SQL 2000 after 2005 instance, you may encounter the known issue documented in the following article 905618 You may receive a connection error message when you try to connect to an instance of SQL Server 2000 or of SQL Server 7.0 that was installed after you installed SQL Server 2005 http://support.microsoft.com/default...b;EN-US;905618 You may want to test if above article fix the problem. When you have a named instance of SQL Server 2000 that is running side-by-side with an instance of SQL Server 2005 on the same computer, the SQL Server 2005 Browser service listens on UDP port 1434 for incoming requests for the named instance of SQL Server 2000. If the issue still occurs, it seems the instance was blocked by the firewall. Going forward, I suggest that you try the following steps to isolate the issue: 1. Click Start->ALL Programs->Microsoft SQL Server, run SQL 2000 Sever network utility, select SQL 2000 server name (servername\instancename). 2. Make sure TCPIP and Named Pipes protocol are enabled 3. Select TCPIP, and click Properties, and set the port of the instance to a fixed port such as 1500. 4. Restart SQL 2000 named instance. 5. Run "Client Network utility" on the server, on Alias type, add a alias such as test, select TCPIP, type the server computer name in Server name. 6. Check if you could connect to Alias on the local server. 7. If you have firewall enabled on your computer, please open the port. Please note, in Win2003 sp1, you could configure Windows firewall in the Control Panel. Please refer to the following article as I mentioned for details. INF: TCP Ports Needed for Communication to SQL Server Through a Firewall http://support.microsoft.com/kb/287932 8. Run "Client Network utility" on the client machine, and create Alias as described in setp 5. If you encounter any problem from this step, you may want to use "telnet <servername> 1500 to see if you could connect to the port you configure from client machine. If you encounter any error message, please let's know exact message. More related information 922131 You cannot remotely connect to a named instance of SQL Server 2000 by using the TCP/IP protocol http://support.microsoft.com/default...b;EN-US;922131 I look forward to your reply. Thanks. Best Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Partner Support ================================================== === This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ====