Cannot connect to Database Engine

Hi! I have a little problem and I need your help.

I have recently installed SQL Server 2005 Developer Edition. I did not install all the features, just the Database engine and Analysis Services. I also updated everything with SQL Server SP2.

So far, so good. But when I tried to connect to the Database Engine, I get a little window with the following message:

"Cannot connect to Valentin-PC (server name)."

"Login failed for user - User Name - ( Microsoft SQL Server, Error: 18456 )".

I have tried just about everything, but to no avail. What is strange is the fact that I can connect to the other server type that I have installed (Analysis Services). No connection problems there.

Can anyone help?

Mucho gracias!

Is the db instance local? If not, then you will need to use the Surface Area Configuration Tool to allow remote connections to the database engine. Remote connections are disabled by default.
Tim|||

I made the switch to allow for remote connections as well but still, the problem persists.

Anyway, and excuse my ignorance, how do I find out if the db instance is local or not?

Thanks!

|||

i think there is something wrong in the credential .... check these links

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

Madhu

|||

I also went through a nighmare when trying to connect to my instance of SQL 2005 Server. In a nutshell:

1. I downloaded the SQL 2005 Server Management Tools <- Highly recommended

2. I opened the "Server Configuration Manager" (located in the configuration tools folder in the SQL Server 2005 folder), and I enabled TCP/IP in all my network cards.

3. I specify the port 1433 as the one I want the server to listen to

4. I used the "Server Configuration Manager" to allow me to use both Windows and SQL authentication to log on

5. I told the Firewall to back off and let SQL listen to the port 1433

These five points allowed me to establish a connection from within my LAN. However, I did one last test in a Virtual Machine, and to make connection I had to go to the connection properties of my local area connection for my adapter, I went to the "Authentication Tab", and I unchecked all checkboxes... although I am very well aware that this is a serious security risk... but anyway, it was just a test in a Virtual Machine.

I hope it helps!!!!

Tarh Ik

PS: This posting has been posted "AS IS"

|||

I very much appreciate your help, Madhu. Just one question, if you don't mind.

How do I access the server error log?

I checked and looked around in the SQL Server folder but could not find it.

Thanks, anyway.

|||

Thanks for the input, Tarh lk. What is amazing is the fact that one has to go through the TCP/IP

in order to connect to a database installed on a one's own machine! It's like calling long distance

just to talk to someone in your own house!

Some of the settings you suggested were already there. I made the rest of them as well, but still no luck.

Thanks, anyway.

|||

I found the server error log. The message I'm getting is:

"Error Number: 18456."

"Severity: 14"

"State: 1"

"Line Number: 65536"

What does it mean? Can the connection problem be fixed?

Thank you for your time!

|||

Having a 'dash' in the server name makes it an invalid server name. Try putting square brackets around the server name.

[Valentin-PC]

|||

I followed your advice and now I'm getting a different message:

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005,

this error may be caused by the fact that under default settings, SQL Server does not allow remote

connections.(provider: Names Pipes Provider, error: 40 - Could not open a connection to SQL Server)

(Microsoft SQL Server, Error: 53)"

Now, just for the sake of it, I went to Surface Area Configuration and checked the settings for Connections.

Both the Database Engine and Analysis Services are set for local connections only.

Go figure!

Thanks, anyway!

|||

this is a common problem ... you need to enable sql server for remote connection..

Ref : http://support.microsoft.com/kb/914277

Madhu