SQL Server 2005 SP2 (9.0.3068) installed on Windows Server 2008 Enterprise.
When I installed SQL Server I specified a "named instance" with the name
TEAMFOUNDATION.

This appears to be working OK; I have Team Foundation Server and SharePoint
3.0 installed on another Windows Server 2008 server and they can use this
instance of SQL Server without any problem.
I've done the steps from KB 914277 to enable Remote Connection using both
TCP/IP and Named Pipes.

Using the instructions in
http://msdn.microsoft.com/en-us/library/ms345483.aspx, executing the command
in the SQL Server Management Studio Database Engine Query window, I moved
the files for one of the databases (WSS_Search_TEAMFOUNDATION) from the
default location to a new disk. This appears to have been successful.

So, by all appearances, the SQL Server instance is up and running and
working OK.

Have you restarted the service after making the changes as per KB 914277?

"Bruce Sanderson" wrote in message
news:uQPVKH37IHA.1428@TK2MSFTNGP06.phx.gbl...

Hi Bruce,
I understand that you could not connect to your SQL Server 2005 instance from another
Windows Server 2008 server.
If I have misunderstood, please let me know.

To narrow down this issue, would you mind first answering me the following two questions?
1. Did this issue happen before you change the database files location?

2. Did you try the steps of "Enable the SQL Server Browser service" and "Create exceptions in
Windows Firewall" in the KB article, http://support.microsoft.com/kb/914277/en-us? If not,
please try it first.

3. Could you connect to your SQL Server 2005 instance from SQL Server Management Studio
on your remote client server?

Generally regarding the error message, there are several typical causes that documented in
this article, http://msdn.microsoft.com/en-us/library/ms190181.aspx. I recommend that you
refer to the section "Typical Causes of this Error" and check if the resolutions work for you.

Please feel free to let me know if you have any other questions or concerns. Have a nice day!

Some possibilities:
On Windows Server 2008 the firewall is on by default. Have you made an
exception for either the SQL Server exe or the SQL Server port? (And since
you are using a named instance, SQL Server may be using dynamic ports, so
SQL Server may not be listening on port 1433.)
Do you have a SQL Server login for your connection. Windows Server 2008
(like Vista) won't let you automatically use your Administrator group
membership.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"bass_player" mvps.org> wrote in message
news:eIhBTE67IHA.2348@TK2MSFTNGP06.phx.gbl...

Thanks for the follow up. The subject installation is a small experimental system I’m working on
partly to gain some knowledge and experience with Team Foundation and SQL Server.

Unfortunately, I have not had any time to devote to this in the last few days.

I’ll take a look at this over the weekend.

I’m issuing the sqlcmd command from an RDP session (logged on with and administrative user account)
of the server that is running SQL Server, NOT from another server. I will try logging on at the
console of that server, but I can’t see that making any difference.

As to your questions:

1.. Don’t know – never tried
2.. I believe so, but will verify
3.. Never tried – I use the SQL Server Management Studio only from an RDP session (logged on with
and administrative user account) of the server running SQL Server

--
Bruce Sanderson
http://members.shaw.ca/bsanders/
It's perfectly useless to know the right answer to the wrong question.

""Charles Wang [MSFT]"" online.microsoft.com> wrote in message
news:NW8xPSG8IHA.4912@TK2MSFTNGHUB02.phx.gbl...

Hi Bruce,
Thank you for your response and let me know the situation.

In addition to check SQL Browser Services and Windows Firewall as mentioned on the KB article, when
you have time I recommend that you also check the following conditions:
1. Check if your SQL Server instance allows remote connection.
On your SQL Server side, open Start->All Programs->Microsoft SQL Server 2005->Configuration Tools->
SQL Server 2005 Surface Area Configuration, click Surface Area Configuration for Services and
Connections, select your SQL Server instance, go to Database Engine->Remote Connections, ensure that
"Local and remote connections" and "Using both TCP/IP and named pipes" are checked. If they are not
checked, please enable them and restart your SQL Server service.

2. Check which TCP port your SQL Server instance is listening.
On your SQL Server side, open Start->All Programs->Microsoft SQL Server 2005->Configuration Tools->
SQL Server Configuration Manager, go to SQL Server 2005 Network Configuration->Protocols for SQL Server instance name>, double click TCP/IP, switch to the IP Address tab and you will find what the
TCP port is being listened by your SQL Server instance.

3. Check if your client request can reach to the TCP port.
On your client side, run "telnet " from command line to check if you can access
the TCP port on your remote server. If this is denied, it is most likely that your Windows Firewall block
the TCP port and I recommend that you add it the the Exception list.

Problem solved! Being new to SQL Server, I assumed that sqlcmd would
connect to the local SQL Server instance automatically, this turns out to be
not the case (I'm logged on at the computer that has the SQL Server instance
installed - I'm not trying to use sqlcmd remotely).

The command:

sqlcmd -S SQLSERVER\TEAMFOUNDATION

successfully connected to the database and I was then able to issue SQL
statements etc.

I have to launch the Command Prompt window elevated (Run as Administrator)
and key in upper case (as shown above) to get it to work.

No configuration changes were required. I did verify that Remote
Connections are enabled (item 1 from your note) and that the SQL Browser
service is configured to start automatically (SQL Server Configuration
Manager shows that all the SQL Server services are running). I've
configured the firewall sqlserver and sql browser. This is all documented
quite well in the Team Foundation Service installation documentation (see
http://go.microsoft.com/fwlink/?LinkId=79226).

Thank you for your posts and follow up.

Hi Bruce,
Thank you for your update.

I am sorry that my suggestions did not help you on this issue. Anyway I am very glad to hear that the
issue has been resolved by yourself. Yes, your SQL Server was installed as a named instance which name
is composed of two parts: server name and instance name. When you connect to a named instance, you
need to specify the two parts in the form of \.

If you have any other questions or concerns, please feel free to let me know. It is my pleasure to be of
assistance.