SQL2000 and 2005 problems on same machine

Steve,
have you gone onto the SQL Server and checked your Server Network Utility
and Client Network Utility manager settings?
http://msdn2.microsoft.com/en-us/lib...0(SQL.80).aspx
Perhaps you need to enable TCP/IP as an allowed protocol.

--
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Steve Gr" wrote in message
news:69B64722-3F0D-4E9D-AEC0-8975A8324E92@microsoft.com...
> Hi,
>
> I can't add a SQL2000 registration to Enterprise manager. I'm using the
> SQL
> New server wizard. I can't see the server I want in the list of available
> servers, so I type in in the box and click Add, eventually it tells me
> that
> the server does not exist or access is denied.
>
> The server I'm using EM on is W2000, the server with SQL2000 installed on
> is
> W2003. I've opened the relevant port on the W2k3 firewall. The W2003
> server
> also has SQL 2005 installed, this was installed before SQL2000.
>
> I also have problems making an ODBC connection to this SQL instance. I can
> create one if I use Windows authentication, but not if I use SQL user.
>
> Any help or pointers would be welcome, thanks.
>
> --
> Steve Gr

"Warren Brunk" wrote:

> Steve,
> have you gone onto the SQL Server and checked your Server Network Utility
> and Client Network Utility manager settings?
> http://msdn2.microsoft.com/en-us/lib...0(SQL.80).aspx
> Perhaps you need to enable TCP/IP as an allowed protocol.
>
Hi Warren,

I checked these out and they.re enabled for TCP/IP. I note that the server
is using port 1073, and the client is using the default 1433 doe that matter?
Should they be the same?
I note that there is an option to choose a port when you're setting up an
ODBC connection (which I have managed to do using Windows authentication),
but you can't choose a port when you're adding a new sql server registration
in enterprise manager.
Regards,
Steve

Steve Gr (MSDNNospam235@nospam.nospam) writes:
> I checked these out and they.re enabled for TCP/IP. I note that the
> server is using port 1073, and the client is using the default 1433 doe
> that matter? Should they be the same?

Yes.

> I note that there is an option to choose a port when you're setting up
> an ODBC connection (which I have managed to do using Windows
> authentication), but you can't choose a port when you're adding a new
> sql server registration in enterprise manager.

If the server is on a different port than 1073, it's supposedly a named
instance. In that case should be able to access the instance by
adding the instance name: SERVER\INSTANCE.

But you can also specify the port number when you connect by using this
format: SERVER,1073.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

"Erland Sommarskog" wrote:

> Steve Gr (MSDNNospam235@nospam.nospam) writes:
> > that matter? Should they be the same?
>
> Yes.

I changed it to 1073 but it made no difference to my problem.


> If the server is on a different port than 1073, it's supposedly a named
> instance. In that case should be able to access the instance by
> adding the instance name: SERVER\INSTANCE.

I still can't do that

>
> But you can also specify the port number when you connect by using this
> format: SERVER,1073.
>

Using that format has allowed me to add it to Enterprise manager. I still
feel as though something is wrong. Can anyone confirm if this is expected
behaviour when you install SQL 2000 after 2005?

Regards,
Steve

Steve Gr (MSDNNospam235@nospam.nospam) writes:
> Using that format has allowed me to add it to Enterprise manager. I still
> feel as though something is wrong. Can anyone confirm if this is expected
> behaviour when you install SQL 2000 after 2005?

It is the expected behaviour when you install a named instance. Since
you installed SQL 2005 first, I assume that this is the default instance
and SQL 2000 is a named instance.

It would be possible to first install SQL 2005 as a named instance, and
then install SQL 2000 as a default instance.

As for SERVER\INSTANCE not working, this may be due to that the SQL Browser
Service is not running, or that its port (UDP 1434, if I remember correctly)
is not open in the firewall.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

"Erland Sommarskog" wrote:

>
> As for SERVER\INSTANCE not working, this may be due to that the SQL Browser
> Service is not running, or that its port (UDP 1434, if I remember correctly)
> is not open in the firewall.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

That has solved the problem. Thanks. Looks like it was nothing to do with
SQL 2005 being on there as well.

Best Regards,

Steve